On Wed, 07 Jan 2009 13:36:56 +1000, Anthony Thyssen wrote: > This is a good enhancment, however can you change it to be a command > line option instead. > > For example > imagick_type_gen -d /path/to/my/fonts > my_type.xml > > Will create a type.xml for a specific directory
hmm... I think the most important feature of my hack is *decoupling* of the generation of font list and font registration. To me that's the most important enhancement. For example, if to use -d, then how to add more directories? Moreover, given the command above what if I only want to register the ttf fonts under it, not pfb or afm ones? More options? what if I want to omit a specific sub directory under /path/to/my/fonts? even more options? Decoupling the font list generation and font registration will eliminate all the above problems and many more that I haven't listed. > rather than using locate. > this way it remains backward compatible with how it is currently > used. hmm... locate has it niche, as said, it is good to add all fonts within the system to ImageMagick once. if to use "-d /" and 'find' instead of locate to add fonts system wide, it would be more than 30 times slower. Again, my solution has a good balance: to add fonts system wide: slocate -ir '\.\(ttf\|pfb\|afm\)$' | imagick_type_gen To work with one or more specific directories: find /path/to/my/fonts /path2 ... | imagick_type_gen For more complicated cases, there is still the last resort -- the freedom of manually editing the font list. Please reconsider. Thanks -- Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/ _______________________________________________ Magick-users mailing list [email protected] http://studio.imagemagick.org/mailman/listinfo/magick-users
