Re: CM-Super font package v0.2.0
i've put the new version of CM-Super package (two days ago) to ftp://ftp.vsu.ru/pub/tex/font-packs/cm-super/ you could try the mirror if connection to vsu.ru is slow: ftp://ftp.chg.ru/pub/TeX/RussianSupport/font-packs/cm-super/ Changes from previous version: * Changed license from Aladdin Free Public License (AFPL) to GNU General Public License (GNU GPL). That license would allow to be included in any (te)TeX distribution. Good. BTW. Since you used TeXtrace, and FontLab, I would like to point out about MF - Type1 conversion. There is another tool (although it has several restrictions) called mf2pt1 (on CTAN:support) allowing such kind conversion (resulting is more precise than tracing [although has overlaps] because has fewer nodes, and thus files shorter), and there is also a freeware font editor, called PfaEdit, at http://pfaedit.sourceforge.net, which has TWO interesting features: - 'Simplify': simplify the fonts reducing the number of unneeded nodes, make PFB file shorter. - 'Remove Overlap': remove overlaps in font paths. The second question is. Is there a table about choosing the UniqueID to be used for each of the Metafont fonts converted to PFB? If not how about to write one? Bye. Giuseppe.
Re: CM-Super font package v0.2.0
At 11.42 +0200 2001-09-24, Giuseppe GhibÚ wrote: The second question is. Is there a table about choosing the UniqueID to be used for each of the Metafont fonts converted to PFB? If not how about to write one? I don't think that's a kosher idea. UniqueIDs exist to help a PS printer cache the result of rendering a font. Since MF - PFB is not one-to-one, but in general one-to-many as some fonts have been converted several times, such a table would assign the same UniqueID to different PFBs. If you use the same UniqueID for a cheapo and a luxo conversion of the same font then you may find that the printer is using the cheapo conversion throughout, when that happens to be what got put in the cache. Furthermore the UniqueID is an optional entry in the font; what you may loose by not having it is merely some processing efficiency. Lars Hellström
Re: CM-Super font package v0.2.0
GG == Giuseppe Ghibò writes: GG BTW. Since you used TeXtrace, and FontLab, I would like to point GG out about MF - Type1 conversion. There is another tool (although GG it has several restrictions) called mf2pt1 (on CTAN:support) GG allowing such kind conversion (resulting is more precise than GG tracing [although has overlaps] because has fewer nodes, and thus GG files shorter), yes, i know about mf2pt1, and it could not convert arbitrary METAFONT fonts, because it uses METAPOST (which does not support some features of METAFONT). GG and there is also a freeware font editor, called PfaEdit, at GG http://pfaedit.sourceforge.net, which has TWO interesting GG features: GG - 'Simplify': simplify the fonts reducing the number of GG unneeded nodes, make PFB file shorter. GG - 'Remove Overlap': remove overlaps in font paths. i used FontLab to simplify (optimize), remove overlaps, and autohint the fonts. i'm not sure that PfaEdit will give better results than FontLab. The current fonts are already quite short, e.g. they are about the same size as commercial Type 1 EC fonts provided by Micropress, Inc. This comparison was made on fonts which contain only glyphs from EC fonts, because CM-Super fonts contain much more glyphs than fonts from Micropress. And there are possibilities to make the fonts even more short, which will be used in next versions: move definitions of glyphs with the same shape into subrs, and construct accented glyphs from non-accented and accents via subrs. GG The second question is. Is there a table about choosing the GG UniqueID to be used for each of the Metafont fonts converted to GG PFB? If not how about to write one? I'll add such a table. Best, v.
Re: CM-Super font package v0.2.0
yes, i know about mf2pt1, and it could not convert arbitrary METAFONT fonts, because it uses METAPOST (which does not support some features of METAFONT). of course it is not a total automatic tool (and in most case it is giving glyph totally messed up, if not converted at all), but it could be interesting to obtain more precise glyphs (or a set of them). On the other hand a big set of glyps replicated on various CM/EC, etc. fonts in the same way, as they are derived from Knuth ones. So the glyphs in Type1 should be always the same. Currently with t1asm/t1disasm it should be not much difficult to extract these glyphs (of course in a semi-automatic way) and combine them into arbitrary fonts to have a precise conversion for EC, etc. For instance see at the attached file: A.gif. Look at the A converted with TeXtrace. On the right, you'll see some distortion (the straight segment show this). On the other attached file you'll see the differencs in node numbers between a A converted with mf2pt1 (left) and yours with TeXtrace (right). i used FontLab to simplify (optimize), remove overlaps, and autohint the fonts. i'm not sure that PfaEdit will give better results than FontLab. Well, FontLab is commercial, while PFAEdit is free and it is getting better and better. Furthermore on font sfrm1000.pfb I achieved a +8-10kb shorter PFB file. Bye. Giuseppe A.gif mf2pt1-textrace.gif
Re: CM-Super font package v0.2.0
On Mon, 24 Sep 2001, Lars [iso-8859-1] Hellström wrote: At 11.42 +0200 2001-09-24, Giuseppe GhibÚ wrote: The second question is. Is there a table about choosing the UniqueID to be used for each of the Metafont fonts converted to PFB? If not how about to write one? I don't think that's a kosher idea. UniqueIDs exist to help a PS printer cache the result of rendering a font. Since MF - PFB is not one-to-one, but in general one-to-many as some fonts have been converted several times, such a table would assign the same UniqueID to different PFBs. If you use the same UniqueID for a cheapo and a luxo conversion of the same font then you may find that the printer is using the cheapo conversion throughout, when that happens to be what got put in the cache. Furthermore the UniqueID is an optional entry in the font; what you may loose by not having it is merely some processing efficiency. Well, I talked about UniqueID in general, not about SuperFont specifically. The idea is to have this UniqueID to avoid this, i.e. to avoid 27 kind of Type 1 conversion of the same fonts (of course not considering the commercial ones which are not freely downloadable). In other word to have (in the free fonts) only ONE official conversion to Type-1 of the same Knuth, EC, etc. MetaFont fonts. Up to not much time ago, the only free fonts available in Type 1 were the BlueSky set of CMR/AMS (which were not covering all the sets), and which were integrated on many TeX distributions, such as teTeX, by some font from the Bakoma free set, some fonts converted by TacoHoekwater (with MetaFog, if I remember right), and not much time ago the TX/PX fonts. Today with the availability of TeXtrace, mf2pt1, and PFAEdit, I think the number of free converted fonts availabile in Type1 format (which is a must for PDF files) is growing (for instance recently someone used TeXtrace for converting MusiXTeX fonts to Type1), so possible there should be a co-ordination to avoid overllaping and to do the same job twice. Bye. Giuseppe.
