Article View: adobe.postscript.programming
Article #1169Re: sfnt array in Type 42 font dict..
From: Nawnit
Date: Fri, 07 Mar 2003 13:15
Date: Fri, 07 Mar 2003 13:15
16 lines
1613 bytes
1613 bytes
Anandi, Thanks for your help. Can you give me idea how can I do without Tables. .? If I am using the TTF tables here What I understod from your reply that I should read all the tables contains in hexadecimal values bytes and make the string object of max size of 65535 and include in sfnt array as per the Tech guide. I have some more doubts on this .. 1) As per my knowledge the table contains many information on predefined offsets. Do I have to send all the data from the tables..? 2) Do I need to keep any order in putting in sfnt array from the different Tables ? Like cmap table data should be before glyph table..? It would be great if you elaborate these point for me. I feel there are lots of table present in the windows TTF files ( its around 20~22 tables). Can I skeep some table data in sfnt array filling..? Once again thanks for your help. Regards, -Nawnit
Technical Details
Message-ID:
<1de82c18.1@WebX.la2eafNXanI>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-04!sn-xit-03!sn-xit-01!sn-xit-08!supernews.com!newsfeed.news2me.com!fu-berlin.de!newsfeed01.sul.t-online.de!t-online.de!WebXReferences:
<1de82c18.-1@WebX.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10c61a,ce0d834eeff1bdb1 X-Google-Attributes: gid10c61a,public X-Google-ArrivalTime: 2003-03-07 05:37:50 PST From: Nawnit <nawnit.kumar@wipro.com> Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-04!sn-xit-03!sn-xit-01!sn-xit-08!supernews.com!newsfeed.news2me.com!fu-berlin.de!newsfeed01.sul.t-online.de!t-online.de!WebX Newsgroups: adobe.postscript.programming Subject: Re: sfnt array in Type 42 font dict.. Message-ID: <1de82c18.1@WebX.la2eafNXanI> Date: Fri, 7 Mar 2003 05:15:52 -0800 References: <1de82c18.-1@WebX.la2eafNXanI> Lines: 22 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit