On Wed, Jun 03, 2009 at 12:13:54AM +0200, Pere Pujal i Carabantes wrote:
> In catalan we need the ç (ccedill) and some accented letters.
> Should I should put all of them here or a selected subset will be
I believe if you put all of the ones necessary for Catalan, that will
help fonts that FULLY support Catalan to bubble up to the top of the list.
Those that PARTIALLY support it would be lower on the list.
> Also, we should be able to type spanish (ntilde, exclamup...) and
> french (æ ae, oe) letters, as they are not so important for writing
> catalan, they have to go to uncommon punctuation below, right?
That sounds right. Albert?
Also, I'm waiting to hear from Albert as to whether providing weights
for some of these strings make sense. (e.g., more 'points' for supporting
common punctuation than for supporting uncommon ones... imagine, for example,
a font that supports Catalan characters (but not French or Spanish), and
one that supports Spanish and French (but is missing Catalan). I think
right now, they'd get the same score for those two tests. An unlikely
example, but still...)
> > > oO - Test whether uppercase and lowercase characters work
> > > (it's ok if it does not, but is scored lower).
> > >
> I am lost here, if we have yet checked for QX (uppercase) and qx
> (lowercase), what we are suposed to put here?
> Oh wait, I see below in your comment about Sweddish.
The "QX"/"qx" and "QY"/"qy" seem to be tested simultaneously. I don't
quite understand the logic, but code-wise, it works like this:
if (... ((charset_works(font, gettext("qx")) && // (qx and
charset_works(font, gettext("QX"))) // QX)
|| // or
(charset_works(font, gettext("qy")) && // (qy and
charset_works(font, gettext("QY"))) )) // QY)
So I guess this means, if all four strings are translated, then the font
had better support everything you had translated it to.
(charset_works() is our own function, written by Albert, that checks
whether every character in the string gets blitted. Unfortunately, in the
case of Tibetan, the font didn't include A-Z characters, it included
Tibetan glyphs at those spots in the font. :^( Bad standard.)
Otherwise, one or the other needs to work. Though I'm not sure if there's
really a difference between "only translate Line X ("qx"/"QX")", which we
instruct people to do now, and "only translate one line, Line X or Line Y".
(Again, this is the case where we need to filter out a font that does not
support our language at all, and we do not grok ASCII.)
*boggle* Confusing. :)
> Here have to go the spanish and french letters and symbols plus euro
> symbol plus some other uncommon punctuation, so this applies to
> 'letters, punctuation and symbols', not only punctuation, right?
> Also the same question as above, is enouth a subset of them?
Depends on if a subset is sufficient for typing in your locale. ;)
(And once again, we should decide whether weighing the score for this
lower than the following (below) is a good idea.)
> So in catalan I have to add "·" middot, "'" apostroph and "-" (minus?)
> as they are really needed.
Sure! Do it! :)
> 1Il| Should I add here "i¡" (lower aye and exclamup)?
(How, exactly, is this test done. Do we compare the blitted characters
somehow!? In other words, I _mostly_ understand why, but I'm unclear if
how we do the test makes sense... I haven't dissected 'charset_works()')
> I've seen some fonts that have the same gliph for both accented and not
> accented letters. Also, I've seen many fonts that have different gliphs
> for lowercase accented/not accented letters, but don't diferentiate
> capital accented letters from its corresponding capital not accented
> one, so maybe the Swedish choice is not so bad.
Albert, is it possible for us to even notice these problems, though?
(i.e., I don't think we compare "i" to "i acute", and see that they
look identical, and therefore score the font lower. Which leads me to
the previous question, what do we _do_ with "1Il|", other than check that
the characters exist in the font?)
Sent from my computer