Hi,
Akira TAGOH wrote:
Using lang-test pattern for scan doesn't work as expected because it
only happens when creating caches.
That also struck me as odd -- the rules for DroidSansJapanese.ttf,
right? I suppose one could use edits instead, to add or replace 'lang'
properties as needed for the later match, or use target="pattern" rules
for that face.
In this case, I'm not sure if this is even necessary though, because I
just dropped DroidSansJapanese.ttf in my font folder and it seemed that
it didn't advertise any of the 'zh*' locales anyway.
Behdad Esfahbod wrote:
In the same recipe with match="scan", I *think* you can add multiple families
and remove the original one, instead of replacing it.
Yes it is possible to append or replace multiple family names at scan
time, so that "Droid Sans Japanese" becomes "Droid Serif,Droid Sans"
which matches both, i. e.
<match target="scan">
<test name="family"><string>Droid Sans Japanese</string></test>
<edit name="family" mode="assign">
<string>Droid Sans</string>
<string>Droid Serif</string>
</edit>
</match>
will make the following possible:
sun2:~)fc-list Droid\ Serif file family
/export/pub/fonts/Droid/DroidSerif-Regular.ttf: Droid Serif
/export/pub/fonts/Droid/DroidSansJapanese.ttf: Droid Sans,Droid Serif
sun2:~)fc-list Droid\ Sans file family
/export/pub/fonts/Droid/DroidSans.ttf: Droid Sans
/export/pub/fonts/Droid/DroidSansJapanese.ttf: Droid Sans,Droid Serif
sun2:~)fc-list Droid\ Serif:lang=ja file family
/export/pub/fonts/Droid/DroidSansJapanese.ttf: Droid Sans,Droid Serif
sun2:~)fc-list Droid\ Sans:lang=ja file family
/export/pub/fonts/Droid/DroidSansJapanese.ttf: Droid Sans,Droid Serif
Although I think mode="append" is smarter here, because it's an easy way
of retaining compatibility with all places that directly refer to the
locale-specific name and expect it to be enumerable with FcFontList.
As a side note, I do wonder why it might be useful to generate all these
exact same family names at scan time. Shouldn't target="pattern"/alias
rules be able to do the same, like 'sans' and 'serif' already map to all
the different fonts for the different languages?
OK I understand that enumeration with FcFontList (for drop-down boxes
and such) will then list the locale-specific variants, but -- without
any particular experience with this font -- I think that's what
applications expect anyway -- or isn't it?
Raimund
On Thu, Jul 26, 2012 at 12:17 AM, Nicolas Mailhot
<nicolas.mailhot@xxxxxxxxxxx> wrote:
Le Mer 25 juillet 2012 14:55, Behdad Esfahbod a écrit :
On 07/16/2012 02:00 AM, Nicolas Mailhot wrote:
So make kufi a separate family and keep the old droid sans arabic for
sans? Or is it also horrible in some way?
I'd say yes.
Ok then I'll take it the changes in
http://pkgs.fedoraproject.org/gitweb/?p=google-droid-fonts.git;a=tree
are ok for production use.
Need to find some brave arabic users to test your other suggestion
--
Nicolas Mailhot
_______________________________________________
Fontconfig mailing list
Fontconfig@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/fontconfig
--
Worringer Str 31 Duesseldorf 40211 Germany +49-179-2981632 icq 16845346
_______________________________________________
Fontconfig mailing list
Fontconfig@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/fontconfig
