Sophie

Sophie

distrib > Mageia > 5 > x86_64 > by-pkgid > 0da03bb1805d73f1aaf1c06fe3cffe2f > files > 243

fontforge-1.0-1.20120731.9.mga5.x86_64.rpm

<HTML>
<HEAD>
  <!-- Created with AOLpress/2.0 -->
  <!-- AP: Created on: 19-Feb-2004 -->
  <!-- AP: Last modified: 13-Oct-2004 -->
  <TITLE>Autotracing bitmaps in FontForge</TITLE>
  <LINK REL="icon" href="fftype16.png">
  <LINK REL="stylesheet" TYPE="text/css" HREF="FontForge.css">
</HEAD>
<BODY>
<DIV id="in">
<H1 ALIGN=Center>
  Autotracing bitmaps in FontForge
</H1>
<P>
FontForge does not have a native autotrace, but it will happily use the output
of two freely available programs which do autotracing. These are:
<UL>
  <LI>
    Peter Selinger's <A HREF="http://potrace.sf.net/">potrace</A>
  <LI>
    Martin Weber's <A HREF="http://sourceforge.net/projects/autotrace/">autotrace
    program</A><BR>
    <FONT COLOR="Red"><STRONG>CAVEAT: </STRONG></FONT>Autotrace 2.8 changed its
    argument conventions (around Dec 2001). New versions (after 15 Dec) of fontforge
    will not work with autotrace2.7, old versions of fontforge will not work
    with autotrace2.8. I see no way to make fontforge work with both or to detect
    the current version...<BR>
    <FONT COLOR="Red"><STRONG>CAVEAT2: </STRONG></FONT>I may not be loading the
    results of autotrace properly in all cases (I do in my test cases, of course).
    AutoTrace traces out both foreground and background regions, so I may sometimes
    leave behind a lump which represents a background area. Just delete it if
    it happens (and send me the image so I can fix things up).
</UL>
<P>
You must download at least one of these, (and possibly build it), and install
it somewhere along your PATH.
<P>
Having done that you must get an image into the background of the glyph(s)
you want to autotrace. There are several ways of doing this:
<DL>
  <DT>
    From a bitmap font
  <DD>
    If you want to autotrace a bitmap font then (from the FontView)
    <UL>
      <LI>
	(You will probably want to start out with a new font, but you might not)
      <LI>
	File-&gt;Import
      <LI>
	select the bitmap font type (bdf, FON, embedded in a ttf file, TeX bitmap
	(GF, PK), etc.)
      <LI>
	turn on the <CODE>[*] As Background </CODE>flag
      <LI>
	Select your font file
      <LI>
	This should place the bitmaps into the background of the glyphs in the font.
	Nothing will be visible in the font view, but if you open up an outline glyph
	view, you should see the bitmap version of the glyph as a grey background.
    </UL>
  <DT>
    From the clipboard
  <DD>
    If you have an application that supports sending image selections by mime
    type (kde does this), then you should be able to copy the image in that
    application and paste it into the appropriate glyph window in FontForge
  <DT>
    From an image file
  <DD>
    If you have a bitmap in an image (it works best if it IS a black and white
    bitmap image, rather than a color image)
    <UL>
      <LI>
	Open up an outline glyph view for the appropriate glyph
      <LI>
	Make the Background layer active (this is usually not necessary)
      <LI>
	File-&gt;Import
      <LI>
	select Format=Image (this will show you any image format that fontforge supports)
      <LI>
	Select your file
      <LI>
	The image should now be visible in the background of this glyph
    </UL>
  <DT>
    From multiple image files
  <DD>
    If you have many images, you can load them with one command, but you must
    name them appropriately. For example if your font contains unicode characters
    U+0041 (LATIN CAPITAL LETTER A) through U+0049 (LATIN CAPITAL LETTER J) then
    create files called "uni0041.png", "uni0042.png", ... "uni0049.png" containing
    the images for the appropriate characters, then (from the Font View)
    <UL>
      <LI>
	Select the requisite glyphs
      <LI>
	File-&gt;Import
      <LI>
	select Format=Image template
      <LI>
	select the first of your images, "uni0041.png"
      <LI>
	This should load all images that match that template ("uni*.png") into the
	appropriate glyph slot
    </UL>
</DL>
<P>
Once you have background images in your font (and have installed an autotrace
program)
<UL>
  <LI>
    Select all the glyphs you wish to autotrace
  <LI>
    Element-&gt;Autotrace
</UL>
<P>
This can take a while, so be patient.
<P>
<FONT COLOR="Red"><STRONG>Warning: </STRONG></FONT>Unless you are working
with a TeX bitmap font, you will most likely have an extremely low resolution
image. Autotrace programs work better the more resolution you give them.
<P>
If you hold down the shift key when you invoke AutoTrace from the menu then
you will be prompted for arguments to pass to it, if you do not hold down
the shift key FontForge will use the same arguments it used last time.
AutoTrace's arguments are described in "$ autotrace -help" or in the README
file that came with the program. Please do not specify input/output files
or formats. FontForge fills these in.
<P>
<P>
<P ALIGN=Center>
-- <A HREF="elementmenu.html#AutoTrace">Back</A> --
<A HREF="overview.html">TOC</A> --
</DIV>
</BODY></HTML>