[AppStream] Local font names in fonts metadata

Changwoo Ryu cwryu at debian.org
Fri Jun 29 04:12:07 UTC 2018


Hello,

On reading AppStream specification "Fonts" section,

> You should add one or more children of type <font/> to make the
> font's full-names known. The full-name should be the same as
> given in the font file for the English language. If no
> full-name is set, a space-separated combination of the font's
> family and style is used instead. The font must have a family
> defined to be included.

It clearly states <font/> should be "full-names for the English
language". But some fonts have local names and people usually specify
those fonts using the local names. I think non-English names should be
also added.

For example, Korean fonts usually have multiple English and Korean
names. Korean web pages often specify their CSS font-family in Korean
font name. And if I write an ODF document specifying a Korean font in
Korean locale, then the document has the Korean version of font family
name, not English one.

In addition, I think "fullname" should not be preferred to "family".

> $ fc-query  /usr/share/fonts/truetype/nanum/NanumGothicBold.ttf
> Pattern has 23 elts (size 32)
>     family: "나눔고딕"(s) "NanumGothic"(s)
>     familylang: "ko"(s) "en"(s)
>     style: "Bold"(s)
>     stylelang: "ko"(s)
>     fullname: "NanumGothicBold"(s)
>     fullnamelang: "en"(s)

Like the above, some fonts only have English "fullname" but multiple
"family" names including local one.


Opinions?


Changwoo Ryu


More information about the AppStream mailing list