Browsing Korean translation

Response to Lavender (186, 157, 255) color selected

Response to Purple (128, 0, 128) color selected

Response to Pink (255, 165, 211) color selected

Response to Brown (128, 80, 0) color selected

Response to Tan (226, 189, 166) color selected

Response to Beige (247, 228, 219) color selected

First, the blacklist. We list font families that can crash Tux Paint
via bugs in the SDL_ttf library. We also test fonts to be sure that
they have both uppercase and lowercase letters. Note that we do not
test for "Aa", because it is OK if uppercase and lowercase are the
same (but not nice -- such fonts get a low score later).

Most locales leave the blacklist strings alone: "QX" and "qx"
(it is less destructive to use the scoring strings instead)

Locales that absolutely require all fonts to have some
extra characters should use "QX..." and "qx...", where "..."
are some characters you absolutely require in all fonts.

Locales with absolutely NO use for ASCII may use "..." and "...",
where "..." are some characters you absolutely require in
all fonts. This would be the case for a locale in which it is
impossible for a user to type ASCII letters.

Most translators should use scoring instead.

TODO: weight specification
Now we score fonts to ensure that the best ones will be placed at
the top of the list. The user will see them first. This sorting is
especially important for users who have scroll buttons disabled.
Translators should do whatever is needed to put crummy fonts last.
distinct uppercase and lowercase (e.g., 'o' vs. 'O')

common punctuation (e.g., '?', '!', '.', ',', etc.)