On 2014-09-03 17:25, Stefan Solbrig wrote:
2014-09-03 22:46 GMT+02:00 Lorna Evans <lorna_ev...@sil.org>:
It came from the Nikosh.ttf file. I have Microsoft Font Properties Extension installed and with that installed I can right click on a .ttf and select "Properties" and it gives me a whole range of tabs full of info that were not available without the extension. I don't know how you would find this
info on other Operating Systems.

Maybe fontforge?

Yes, fontforge can do this.
Open the font file with fontforge,
then select "Elements"->"Font info".

thanks, I see that now, but how do you find the embeddability info that xdvipdfmx is seeing? I guess it's coded as a single bit, but is there a way to read it in FontForge?

(As a quick hack, if you don't want to install fontforge,
the License is usually also contained as an utf-8 string. So just
doing a dump e.g. with:
   hexdump -C path/to/font/file  | less
or using a hex capable edtior:
   vim -b  path/to/font/file
will make it easy to find the license (usually at the beginning if the
 font file.
It might also be stored as an utf-16 string, which makes it a bit
harder to read.

The license is encoded both as UTF-8 and as UTF-16; at a guess, the latter is what Lorna reported in the Windows app (and what I also see in FontForge) as looking like a "Chinese" license!

   Mike Maxwell


--------------------------------------------------
Subscriptions, Archive, and List information, etc.:
 http://tug.org/mailman/listinfo/xetex

Reply via email to