Fontforge: Feature request for some support for the 'meta' table (for example: dlng tag)

[xmha97]

Hi,
Please go to Windows 10 font manager

How I can change the "Designed language" tag?

[JoesCat]

FontForge is put together and maintained by volunteers.
If nobody has volunteered to help translate to that language, then the default will be English.

These are the current language translations so far (with percentage translation so far).
https://crowdin.com/project/fontforge

Would you, and others be interested in helping with translation?

[frank-trampe]

@JoesCat, I think he wants to know where the font stores the value that Windows 10 displays as "Designed language".

@xmha97, I don't know the answer to this. It could be an actual value, or it could be inferred from the codepoints covered. I would suggest dumping the file to XML with TTX (a free Python tool) and searching the text of the XML for "Arabic". If it is in a particular field, we have our answer. If it is not, it might take a little more work.

@adrientetar, do you have any thoughts on this?

[dscorbett]

Does the font include a 'dlng' tag (“Design languages”) in a 'meta' table? If so, this issue is a feature request for some support for the 'meta' table. FontForge currently ignores it.

[xmha97]

The meta table was added to the OpenType spec in version 1.8 in September 2016, it was previously in the Apple TrueType specification.
The meta table information can probably be added, for example under the key openTypeMeta, as a dict with keys restricted to the registered tags appl, bild, dlng, and slng or private tags in all uppercase ASCII letters (however the Apple TrueType spec says the first letter must be a capital letter), values can be either <string> or <data> elements. The values for appl and bild must be <data>, the values of dlng and slng must be <string> elements, all others should be allowed to be either.
It would be particularly useful to be able to define the dlng “Design languages” and slng “Supported languages” metadata in UFO.