I recently noticed that Font Book seems to have changed its database with respect to what it considers necessary for each language to show up as supported. For example, some of my fonts that were flagged as supporting Dutch and Turkish in older versions of Font Book (or Mac OS) are not showing these two any more.
Is there a way to access the language database in Font Book? Does anyone know which database they use? Although I wouldn’t consider Font Book the only authoritative source on this, it would be good to know which characters I need to include to make Font Book show a certain language as supported.
0
Comments
Still trying to figure out what the letter pairs mean, e.g. Dutch requires:
a á ä b c d e é ë f g h i í ï ij j k l m n o ó ö p q r s t u ú ü v w x y z
a á ä b c d e é ë f g h i í ï ij j k l m n o ó ö p q r s t u ú ü v w x y z
Possibly a compatibility decomposition of the ij digraph character (U+0133)?
John, I also thought of a decomposition but there are other pairs such as ch and dd for Welsh, which aren’t decompositions, I assume?
So, this puzzle is still not quite solved.
The list of locales is pretty similar, however the content is slightly different in some cases, which probably means it from an older version or has been processed in some way.
For exemple CLDR’s nl.xml contains:
and in LanguageAlphabets.plist there is:
What editor do you use?
I’m mainly using Glyphs, btw.
I didn’t mean to start a discussion on the question which characters are necessary for Dutch or any other specific language. I am sure there would be a lot to discuss on this topic.
As I said above, I wouldn’t consider Font Book the only authoritative source on this but it would be good to know which characters I need to include to make Font Book show a certain language as supported.
I am always trying to have my own opinion on which characters make sense to include but in the case of FontBook language support, it may be easier to just follow along and provide the specified characters so as not to confuser users who, unlike us, might rely entirely on the information given by Font Book.
I'm not absolutely sure how the information in curly brackets should be interpreted at all. My underständing is {íj\u0301} means the iacute-jacute ligature which is not encoded in unicode. In this case CLDR list the components needed to build this character. But simply adding the combining acute is not enough to fully support the dutch iacute-jacute ligature case.
On the other hand, if I add the combining acute to the list of required characters for dutch, the Charset Checker (which uses the same database) will mark dutch as unsupported for a whole bunch of existing fonts, what I don't want either.
It is a dilemma...
And as a side note: Not everything that Apple has done in the past in regard of unicode was 100% correct ;-)
Eigi