[Pkg-fonts-devel] Bug#714436: Bug#714436: Only three Hangul glyphs in it

Changwoo Ryu cwryu at debian.org
Sat May 10 13:06:34 UTC 2014


2014-05-10 21:29 GMT+09:00 Jonas Smedegaard <dr at jones.dk>:
> Hi Changwoo (or is that your family name? I aimed for "first" name),

Hello,

Mostly shorter one is the Korean family name and the other is give
name. Yes, Changwoo is my given name.

>> IMO simple solution is just to copy&paste Hangul glyphs from another
>> DroidSansFallback file to DroidSansFallbackFull.ttf. Simple
>> python-fontforge script can do the job. It will modify font file but I
>> think it's better than increasing package size and messing with
>> fontconfig configs. Opinions?
>
> Best is, I believe, to try collaborate upstream on such improvements, as
> else we will effectively create a fork of the font which is generally
> bad for the FLOSS eco system.
>
> If you find it more comfortable to work only with Debian on this, then
> perhaps you could try put together the script that you envision and
> share it as a patch to this bugreport, and others can then pass that
> upstream for their consideration.

In my years of Debian development, I have almost always worked with
upstream and I think you are right in general.

But in this specific case, working with upstream won't work. These
Hangul glyphs have been removed with clear reason; because they are
replaced by NanumGothic font in Android. What could AOSP do on this?
We can't expect them to restore the Hangul glyphs or to begin
maintaining general font file for non-Android use.

My idea is to copy Hangul glyphs from DroidSansFallback.ttf to
installed DroidSansFallbackFull.ttf during package building. It's not
about modifying the font data directly.



More information about the Pkg-fonts-devel mailing list