From: Paul-Kenji C. <pkc@F1-Photo.com> - 2008-08-27 02:54:13
|
Hello, I have recently been trying to convert some of our old Japanese mac fonts (sadly not available in ttf/otf) and so far have no managed to convert them to anything usable. The fonts of course come in traditional ffil style, with ressource forks. The easy part was getting them as dfonts. Using fondu produces .ttf files(which dont look like ttfs to me) that wont open in anything but mac os itself(cid type 0?) These CID Type 0 font files(which I have also obtained by creating a pdf including the font and then using a tool to extract the pdf fonts as fontforge's pdf opening feature did not work properly) do not seem to behave well at all with fontforge, sometimes segfaulting, other times importing only a few glyphs in the wrong place.(The only exception being only producing the ascii subset of the font when generating a pdf containing it and then extracting the resulting font from the pdf) I have put up one of the smaller ones at: http://91.121.88.169/Various/FontForge/ (dfont file, and the ttf generated by fondu) Thanks in advance for any answer, PK Cahier |
From: George W. <gw...@si...> - 2008-08-27 23:46:25
Attachments:
cid.patch
|
On Tue, 2008-08-26 at 19:51, Paul-Kenji Cahier wrote: > I have recently been trying to convert some of our old Japanese mac fonts > (sadly not available in ttf/otf) and so far have no managed to convert > them to anything usable. These files appear to be in the old (undocumented as far as I know) Apple CID-sfnt format. Which is basically an sfnt wrapper (ttf and otf files are also sfnts) around a 'CID ' table which contains a CID font -- and some garbage (at least it's garbage to me because I can't understand it). (fondu calls it a ttf file because fondu thinks all 'sfnt's are either truetype or opentype; it doesn't know about all the other odd formats Apple came up with.) In theory fontforge can read these. However a lot of old Apple CID-sfnts contain CID fonts which do not comply with Adobe's CID-font description (oh, they are valid PostScript, and if the PostScript is executed it will produce a valid CID font. Consider the pfb file for a moment. There are many ways using valid PostScript to create a type1 font. One of those ways was chosen as the standard representation and became the pf[ab] file format. A full PostScript interpreter can handle any representation, but something like Adobe Type Manager can only read the standard pfb format. In this case the fix (to fontforge) turns out to be simple, but I make no promises about others of these fonts. |
From: Anshuman P. <pa...@um...> - 2008-08-28 00:12:51
|
I am having some trouble exporting glyphs of a TrueType font as bitmaps through scripting. I am able to use the Export() function to produce EPS files containing glyph images: Open("font.ttf") SelectAll() Export("%e_%f.eps") But, when I modify the above lines as Open("font.ttf") SelectAll() Export("%e_%f.bmp",72) in order to generate bitmap files, fontforge says that "No bitmap font matches the specified size". When I add BitmapsAvail([72]) after the Open() line, fontforge creates the expected files, but without the glyph image. Is there something I am overlooking? Regards, Anshuman |
From: George W. <gw...@si...> - 2008-08-28 00:41:47
|
On Wed, 2008-08-27 at 17:12, Anshuman Pandey wrote: > I am having some trouble exporting glyphs of a TrueType font as bitmaps > through scripting. > But, when I modify the above lines as > Open("font.ttf") > SelectAll() > Export("%e_%f.bmp",72) > in order to generate bitmap files, fontforge says that "No bitmap font > matches the specified size". > When I add BitmapsAvail([72]) after the Open() line, fontforge creates the > expected files, but without the glyph image. That is what you need to do. It works for me (the files have glyph images). There were problems with creating bitmaps from scripts recently. I hope the problem will be fixed if you upgrade to the current release. -- except don't do it right now. I've fixed another crash in the current release and need to post a new one. (cvs sources are up-to-date, otherwise wait until the file release system has a 20080828 build in it which will be sometime tomorrow given my slow internet connection). |
From: Anshuman P. <pa...@um...> - 2008-08-28 00:51:20
|
Hi George, I just installed release 20080824 and the BitmapsAvail() function works properly. I re-ran my script and the .bmp files were no longer being produced as empty. I did read in the release notes that the function was erroneously exporting backgrounds. Thanks for the quick response and for fixing the bug. Regards, Anshu On Wed, 27 Aug 2008, George Williams wrote: > On Wed, 2008-08-27 at 17:12, Anshuman Pandey wrote: >> I am having some trouble exporting glyphs of a TrueType font as bitmaps >> through scripting. >> But, when I modify the above lines as >> Open("font.ttf") >> SelectAll() >> Export("%e_%f.bmp",72) >> in order to generate bitmap files, fontforge says that "No bitmap font >> matches the specified size". >> When I add BitmapsAvail([72]) after the Open() line, fontforge creates the >> expected files, but without the glyph image. > That is what you need to do. > > It works for me (the files have glyph images). > > There were problems with creating bitmaps from scripts recently. I hope > the problem will be fixed if you upgrade to the current release. > -- except don't do it right now. I've fixed another crash in the > current release and need to post a new one. (cvs sources are up-to-date, > otherwise wait until the file release system has a 20080828 build in it > which will be sometime tomorrow given my slow internet connection). > > > > |
From: <mps...@hi...> - 2008-08-29 05:51:49
|
Hi, I'm a maintainer of Mac-specific functionalities in FreeType2. At present, FreeType2 could not read the dfont data you provided, although FreeType2 can find sfnt resource in it. So I want to fix it, if it's not special case. Could you tell me how you created it? # taking a glance on the contents, there would be a # few unexpected conditions for FreeType2. # 1) the header of sfnt resource is "typ1". It differs # from the candidates FreeType2 expects: 0x00010000, # "true", "OTTO", etc. # 2) the sfnt resource has no "maxp" table. Regards, mpsuzuki On Wed, 27 Aug 2008 04:51:02 +0200 Paul-Kenji Cahier <pkc@F1-Photo.com> wrote: >Hello, > >I have recently been trying to convert some of our old Japanese mac fonts >(sadly not available in ttf/otf) and so far have no managed to convert >them to anything usable. > >The fonts of course come in traditional ffil style, with ressource forks. >The easy part was getting them as dfonts. >Using fondu produces .ttf files(which dont look like ttfs to me) that wont open in anything >but mac os itself(cid type 0?) >These CID Type 0 font files(which I have also obtained by creating a pdf including the font >and then using a tool to extract the pdf fonts as fontforge's pdf opening feature did not >work properly) do not seem to behave well at all with fontforge, sometimes segfaulting, >other times importing only a few glyphs in the wrong place.(The only exception >being only producing the ascii subset of the font when generating a pdf containing it >and then extracting the resulting font from the pdf) > >I have put up one of the smaller ones at: http://91.121.88.169/Various/FontForge/ >(dfont file, and the ttf generated by fondu) > >Thanks in advance for any answer, > >PK Cahier > > >------------------------------------------------------------------------- >This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >Build the coolest Linux based applications with Moblin SDK & win great prizes >Grand prize is a trip for two to an Open Source event anywhere in the world >http://moblin-contest.org/redirect.php?banner_id=100&url=/ >_______________________________________________ >Fontforge-users mailing list >Fon...@li... >https://lists.sourceforge.net/lists/listinfo/fontforge-users |