From: mpsuzuki@hiroshima-u.ac.jp
Date: Tue Feb 26 2008 - 09:05:08 CST
Dear Sir,
Nice to hear the samples were something useful for you.
Indeed, fontforge is appropriate and easy tool to change
the values. In fact, I used fontforge for preliminary
test - afterwards, I used binary editor to make minimum
modified samples.
On Tue, 26 Feb 2008 05:51:49 -0600
vunzndi@vfemail.net wrote:
>Quoting mpsuzuki@hiroshima-u.ac.jp:
>> vs17-ucr.ttf:
>> All bits in UnicodeRange in OS/2 are set,
>> vs17-cpr.ttf:
>> All bits in CodePageRange in OS/2 are set,
>> vs17-ucr+cpr.ttf:
>> All bits in UnicodeRange and CodePageRange in OS/2 are set.
>
>The results provisionally seem to be rather application depednent
>
>Some quick test results
>
>on Linux (debian)
>
>abiword - works with any font including my original
>
>on windows
>
>abiword - works with any font including my original
>word - works with either vs17-cpr.ttf or vs17-ucr+cpr.ttf
>wordpad - various partial results, eg displays vs17-cpr.ttf in
>pre-existant documents but won't select.
At present I don't have abiword in my hand - most Linux
applications let fontconfig library to manage the font
files, and fontconfig checks the character coverage by
cmap/loca/glyf, so the UnicodeRange and CodePageRange
in OS/2 have no effects, I guess. fontconfig-2.2 didn't
check the complex text layout feature support, but
fontconfig-2.4 checks GSUB, GPOS and Silf tables to
pass appropriate fonts to the text layout libraries.
We can find that Apple reserved a few flags in head table
to indicate the requirement of complex text layout feature.
Please check head.flags bit 7,8,9,10 and head.fontDirectionHint in
http://developer.apple.com/textfonts/TTRefMan/RM06/Chap6head.html
OpenType specification does not carry over these flags.
However, yet I've not investigated how Mac OS font
framework check these values.
Regards,
mpsuzuki
This archive was generated by hypermail 2.1.5 : Tue Feb 26 2008 - 09:08:03 CST