<HTML>
<HEAD>
<!-- Created with AOLpress/2.0 -->
<!-- AP: Created on: 2-Sep-2002 -->
<!-- AP: Last modified: 14-Nov-2008 -->
<TITLE>Preferences Dialog</TITLE>
<LINK REL="icon" href="fftype16.png">
<LINK REL="stylesheet" TYPE="text/css" HREF="FontForge.css">
</HEAD>
<BODY>
<DIV id="in">
<H1 ALIGN=Center>
Preferences Dialog
</H1>
<UL>
<LI>
<IMG SRC="prefs-generic.png" WIDTH="502" HEIGHT="360" ALIGN="Right"><A HREF="prefs.html#ResourceFile">Generic</A>
<LI>
<A HREF="prefs.html#NewCharset">New Font</A>
<LI>
<A HREF="prefs.html#PreferCJKEncoding">Open Font</A>
<LI>
<A HREF="prefs.html#GlyphAutoGoto">Navigation</A>
<LI>
<A HREF="prefs.html#ItalicConstrained">Editing</A>
<UL>
<LI>
<A HREF="prefs.html#AutoWidthSync">Synchronize</A>
<LI>
<A HREF="prefs.html#ClearInstrsBigChanges">TT</A>
<LI>
<A HREF="prefs.html#AccentOffsetPercent">Accents</A>
<LI>
<A HREF="prefs.html#PreferPotrace">Apps</A>
</UL>
<LI>
<A HREF="prefs.html#FoundryName">Font Info</A>
<LI>
<A HREF="prefs.html#AskBDFResolution">Generate</A>
<UL>
<LI>
<A HREF="prefs.html#Hints">PS Hints</A>
<LI>
<A HREF="prefs.html#Instrs">TT Instrs</A>
<LI>
<A HREF="prefs.html#UseNewIndicScripts">OpenType</A>
</UL>
<LI>
<A HREF="prefs.html#scripts">Script Menu</A>
<LI>
Mac
<UL>
<LI>
<A HREF="prefs.html#Mac">Features</A>
<LI>
<A HREF="prefs.html#Mapping">Mapping to OpenType</A>
</UL>
<P>
<BR CLEAR=ALL>
</UL>
<P>
<IMG SRC="prefs-generic.png" WIDTH="502" HEIGHT="360" ALIGN="Right">
<DL>
<DT>
<A NAME="ResourceFile">ResourceFile</A>
<DD>
FontForge will read <A HREF="xres.html">X Resources</A> from a property on
the screen. But sometimes this isn't enough. You set this preference item
to specify a file from which these resources should be read (those on the
screen will also be read and will supersede those in the file).
<DT>
<A NAME="HelpDir">HelpDir</A>
<DD>
FontForge will search this directory for help files when the user presses
[F1].
<DT>
<A NAME="OtherSubrsFile">OtherSubrsFile</A>
<DD>
Allows you to redefine the OtherSubrs routines used in type1 fonts. The file
format is described at the scripting command
<A HREF="scripting-alpha.html#ReadOtherSubrsFile">ReadOtherSubrsFile</A>.
<DT>
<A NAME="FreeTypeInFontView">FreeTypeInFontView</A>
<DD>
Normally FontForge will use the freetype library to generate glyphs for display
in the fontview. This is a bit slower, but creates better images than using
FontForge's built-in rasterizer. This preference item allows you to control
whether to use freetype or FontForge's own rasterizer.
<DT>
SplashScreen
<DD>
Controls whether a splash screen is displayed on start up.
<DT>
UseCairoDrawing
<DD>
FontForge can use its own drawing routines, or rely on Cairo library in the
<A HREF="charview.html">outline glyph view</A>. Using Cairo is slower, but
gives smooth curves, and subpixel display precision. New setting applies
only to windows created afterwards.
<DT>
UsePangoDrawing
<DD>
Controls whether FontForge uses its own interface text drawing routines,
or relies on Pango library. Using Pango slows down older machines, but gives
antialiased text, exotic Unicode support, and complex script support. New
setting applies only to windows created afterwards.<BR Clear=all>
</DL>
<P>
<IMG SRC="prefs-newfont.png" WIDTH="502" HEIGHT="360" ALIGN="Right">
<DL>
<DT>
<A NAME="NewCharset">NewCharset</A>
<DD>
The default encoding used to create new fonts. Normally this is ISO 8859-1.
<DT>
<A NAME="NewEmSize">NewEmSize</A>
<DD>
Specifies the default number of em-units in the em-square. For PostScript
fonts this should be 1000, for truetype fonts it should be a power of two
(often 512, 1024 or 2048 will be used).
<DT>
<A NAME="NewFontsQuadratic">NewFontsQuadratic</A>
<DD>
Splines in fonts may be either in quadratic or cubic format. TrueType fonts
use quadratic splines while PostScript (and OpenType) fonts use cubic splines.
When FontForge generates a font it will convert from whatever format is used
internally to whatever format is required for the font, so there will be
no problem if this is set incorrectly, but setting it correctly for your
font means you get a clearer idea of what the outlines will look like.
<DT>
<A NAME="LoadedFontsAsNew">LoadedFontsAsNew</A>
<DD>
When FontForge reads in a font it will generally keep the splines in the
format they used in the font (that is quadratic for truetype fonts and cubic
for postscript). If you set this flag then all loaded fonts will have the
same file format as that specified by NewFontsQuadratic above.<BR Clear=all>
<DT>
</DL>
<P>
<IMG SRC="prefs-openfont.png" WIDTH="502" HEIGHT="360" ALIGN="Right">
<DL>
<DT>
<A NAME="PreferCJKEncoding">PreferCJKEncoding</A>
<DD>
This controls the loading of truetype and opentype fonts. If a font contains
both an unicode encoding subtable and a cjk subtable, then this item allows
you to pick which one FontForge will choose to decode.
<DT>
AskUserForCMap
<DD>
When loading an sfnt (truetype, opentype font file), ask the user which cmap
encoding s/he would like to use.
<DT>
<A NAME="PreserveTables">PreserveTables</A>
<DD>
A string containing a list of 4 letter table tags separated by commas. When
loading an SFNT (ttf/otf) file, any table in the font with one of these tags
will be preserved without interpretation. (Note: If FontForge thinks it
understands the table it will parse it rather than preserving it).
<DT>
SeekCharacter
<DD>
A unicode character (or a hex name for a unicode character, so either "A"
or "U+0041"), fontforge will attempt to scroll the display to this character
when it opens a font.
<DT>
CompactOnOpen
<DD>
Whether fontforge should make a font compact when it opens one (does not
apply to openning an sfd file which already knows whether it should be compact
or not).<BR CLEAR=ALL>
</DL>
<P>
<IMG SRC="prefs-navigation.png" WIDTH="502" HEIGHT="360" ALIGN="Right">
<DL>
<DT>
<A NAME="GlyphAutoGoto">GlyphAutoGoto</A>
<DD>
In the glyph window this controls how ff behaves when the user types a normal
character. If this is On then when a normal character is typed the glyph
window will shift to display that character, if Off typed characters will
be ignored.
<DT>
OpenCharsInNewWindow
<DD>
Double clicking on a glyph in a <A HREF="fontview.html">font view</A> can
either always create a new <A HREF="charview.html">glyph view</A>, or reuse
an already opened one.<BR Clear=all>
</DL>
<P>
<IMG SRC="prefs-editing.png" WIDTH="502" HEIGHT="390" ALIGN="Right">
<DL>
<DT>
<A NAME="ItalicConstrained">ItalicConstrained</A>
<DD>
Whether constrained motion in the glyph view should allow motion parallel
to the italic angle as well as horizontal and vertical.
<DT>
<A NAME="ArrowMoveSize">ArrowMoveSize</A>
<DD>
The number of em-units an arrow key will move a selected point in the glyph
view.
<DT>
<A NAME="ArrowAccelFactor">ArrowAccelFactor</A>
<DD>
When holding down the Alt (Meta) key, the arrow keys will move faster. This
preference item says how much faster.
<DT>
<A NAME="SnapDistance">SnapDistance</A>
<DD>
The maximum distance at which pointer motion in the glyph view will be snapped
to an interesting object (ie. a point, baseline, width line, etc.). This
is measured in pixels.
<DT>
SnapToInt
<DD>
When positioning points and control points, the mouse will move to the nearest
integral value. This is useful in editing TrueType (or PostScript if you
wish to save space in the font file).
<DT>
<A NAME="JoinSnap">JoinSnap</A>
<DD>
The maximum distance between the endpoints of two splines before they will
join with the Edit->Join command. This is measured in pixels in the char
view and em-units elsewhere.
<DT>
<A NAME="StopAtJoin">StopAtJoin</A>
<DD>
When dragging points in the outline view, if the end point of one open contour
is moved onto the end point of another open contour then those two contours
will join. If you leave this Off then further motion will continue to move
the points, if you set this to On then FontForge will stop noticing mouse
movements (it pretends that you released the mouse button). This is useful
if you hand jitters a little on the mouse.
<DT>
<A NAME="CopyMetaData">CopyMetaData</A>
<DD>
Controls the behavior of Edit->Copy from the fontview. Normally Copy does
not copy a glyph's metadata (name, encoding, etc.) but if this is set then
it will.
<DT>
<A NAME="UndoDepth">UndoDepth</A>
<DD>
Controls the maximum number of Undoes that may be retained in a glyph. (In
some rare occasions an Undo will be stored even if this depth is 0)
<DT>
<A NAME="UpdateFlex">UpdateFlex</A>
<DD>
Figure out what points will be part of flex hints after every change to a
glyph. Points which are at the center of a flex hint will have a green halo
drawn around them. The criteria for flex hints are given on pages 72-73 of
Adobe's
<A HREF="http://partners.adobe.com/asn/developer/PDFS/TN/T1_SPEC.PDF">T1_Spec.pdf</A>.
This setting can be used to show you when those criteria are not met.
<DT>
<A NAME="UpdateFlex">AutoKernDialog</A>
<DD>
Controls whether FontForge opens an <A HREF="lookups.html#Pair">auto kern
dialog</A> for each new kerning subtable.<BR Clear=all>
</DL>
<P>
<IMG SRC="prefs-sync.png" ALIGN="Right" WIDTH="502" HEIGHT="360">
<DL>
<DT>
<A NAME="AutoWidthSync">AutoWidthSync</A>
<DD>
Whether you want the widths of accented glyphs to track the width of the
base glyph (so if you modify the width of A then the width of À will
automagically change, if À is built as a reference to A and a reference
to grave)
<DT>
<A NAME="AutoLBearingSync">AutoLBearingSync</A>
<DD>
Whether you want left side bearings of accented glyphs to track the left
side bearing of base glyphs (so if you shift A left, then the accent in À
will also be shifted left)<BR CLEAR=ALL>
</DL>
<P>
<IMG SRC="prefs-tt.png" WIDTH="502" HEIGHT="360" ALIGN="Right">
<DL>
<DT>
<A NAME="ClearInstrsBigChanges">Clear Instructions on Big Changes</A>
<DD>
TrueType instructions refer to points by number. So if you do any editing
that adds, removes or otherwise changes the point numbers then the instructions
will be applied to a different set of points.
<P>
Sometimes the results are amusing, but almost always they are ugly and wrong.
<P>
This is very different from having out of date PostScript Hints. There the
hints are probably just useless (as opposed to being actively bad, as here).
<P>
FontForge will normally delete all instructions to prevent this happening.
However, if you are prepared to fix up the instructions after a set of changes
you may prefer to have the instructions left. Be careful though!
<DT>
CopyTTFInstrs
<DD>
When copying and pasting in the font view, copy and paste instructions as
well as the glyph outlines.
<FONT COLOR="Red"><STRONG>WARNING</STRONG></FONT>: If you copy a glyph from
one font to another its instructions will probably not work (it will make
assumptions about the control table and subroutines which do not hold in
the new font).<BR CLEAR=ALL>
</DL>
<P>
<IMG SRC="prefs-accent.png" ALIGN="Right" WIDTH="502" HEIGHT="360">
<DL>
<DT>
<A NAME="AccentOffsetPercent">AccentOffsetPercent</A>
<DD>
The amount of space (as a percentage of the em-square) that should be placed
between an accent and the glyph below it by the Build Accented Character
command.
<DT>
<A NAME="AccentCenterLowest">AccentCenterLowest</A>
<DD>
Whether accents should be positioned over letters based on the center of
the accent, or on the center of the bottom of the accent.
<DT>
<A NAME="CharCenterHighest">CharCenterHighest</A>
<DD>
Whether accents should be positioned over letters based on the center of
of the letter, or on the center of the top of the letter.
<DT>
PreferSpacingAccents
<DD>
Whether to prefer spacing accents (Unicode 02C0-02FF) or combining accents
(0300-036F) when building accented glyphs.<BR CLEAR=ALL>
</DL>
<P>
<IMG SRC="prefs-apps.png" WIDTH="502" HEIGHT="390" ALIGN="Right">
<DL>
<DT>
<A NAME="PreferPotrace">PreferPotrace</A>
<DD>
If you system has both potrace and autotrace installed this allows you to
specify which you'd prefer FontForge to use for autotracing.
<DT>
<A NAME="AutotraceArgs">AutotraceArgs</A>
<DD>
This allows you to specify any arguments you want passed to the autotrace
program. Don't try to pass something that will change the input or output
format or set input or output files.
<DT>
<A NAME="AutotraceAsk">AutotraceAsk</A>
<DD>
If this is set then each time autotrace is invoked it will ask you for arguments.
<DT>
<A NAME="MfArgs">MfArgs</A>
<DD>
This is the command passed to the mf (MetaFont) program which controls conversion
of .mf files into bitmaps.
<DT>
<A NAME="MfClearBg">MfClearBg</A>
<DD>
Loading a .mf font is a multi step process, first a bitmap font is generated,
it is loaded into the background, then autotrace is invoked to trace around
the backgrounds. These background bitmaps can take up a lot of space and
you may not want them after they have been autotraced. Selecting this entry
will remove those bitmaps from the font after they have been used.
<DT>
<A NAME="MfShowErr">MfShowErr</A>
<DD>
The mf program generates a fair amount of verbiage even when it is working
correctly. And if it is working correctly you don't want to see those words.
So normally FontForge suppresses messages from mf. But if something goes
wrong you do want to see mf's output and setting this will allow you to do
so.<BR Clear=all>
</DL>
<P>
<IMG SRC="prefs-font.png" WIDTH="502" HEIGHT="360" ALIGN="Right">
<DL>
<DT>
<A NAME="FoundryName">Foundry Name</A>
<DD>
Used in generating bdf files (part of the X Windows font naming convention).
<DT>
<A NAME="TTFFoundry">TTF Foundry</A>
<DD>
Similar to the above except that it is used inside ttf files (the achVendID
field of the OS/2 table) and is limited to 4 characters.
<DT>
<A NAME="NewFontNameList">NewFontNameList</A>
<DD>
Specifies the namelist that will be attached to any new font. This list will
be used to name any glyphs created in that font. See the section on
<A HREF="encodingmenu.html#namelist">namelists</A> for more information.
<DT>
RecognizePUANames
<DD>
Originally Adobe used the PUA (public use area of unicode) to contain glyphs
for small caps, lower case numerals, etc. They have since changed their minds
and no longer recommend this usage. FontForge normally recognizes names like
"a.sc" as being mapped to the appropriate slot in Adobe's old view of the
PUA. If you don't like this behavior turn this item off and "a.sc" will not
have a unicode encoding.
<DT>
UnicodeGlyphNames
<DD>
Glyph names are supposed to be composed of ASCII letters and numbers (and
a few other characters). At least they are when they are stored in a font.
But when you are building a font and if you are not an English speaker, it
might be useful to have a wider range of letters available for glyph names.
You should never export these names when you generate a font (Use the Force
Glyph Names to field of the generate dialog).
<!--
<DT>
<A NAME="XUID-Base">XUID-Base</A>
<DD>
The base
"<A HREF="http://partners.adobe.com/asn/tech/type/xuid.jsp">XUID</A>". Should
uniquely identify the user's organization. If present then every new font
will be given an XUID generated by appending a random number to the end of
this string (which should consist of a set of numbers separated by spaces).
Whenever a postscript font is generated then this last number will be incremented
by 1.
<P>
I have registered with Adobe and they have assigned FontForge (actually PfaEdit)
an extended unique id base of [1021]. When you first start FontForge, FontForge
will itself append a couple of random numbers to this to give you your own
extended unique id. And individual fonts will get a fourth number added to
that.
<P>
If you want you may
<A HREF="http://partners.adobe.com/asn/tech/type/xuidregister.jsp">register
directly with Adobe</A> for your own XUID base.
<P>
See also Adobe's comments on
<A HREF="http://partners.adobe.com/asn/tech/type/uniqueid.jsp">UniqueID</A>s.
-->
<DT>
AddCharToNameList
<DD>
Some character names are barely understandable or unintuitive. While editing
opentype lookups having long lists of such names, confusion is easy. A character
itself may be appended to the name to make things easier. <BR Clear=ALL>
</DL>
<P>
<IMG SRC="prefs-generate.png" WIDTH="502" HEIGHT="360" ALIGN="Right">
<DL>
<DT>
<A NAME="AskBDFResolution">AskBDFResolution</A>
<DD>
Normally FontForge will guess at what screen resolution you intend based
on the pixel size of the font (ie. 17 pixel fonts are usually 100dpi (12pt)
and 12 pixel fonts are usually 75dpi), but sometimes you will have more esoteric
desires. Setting this will give you more control, but you have to click through
another dlg.
<DT>
<A NAME="AutoHint">AutoHint</A>
<DD>
Whether glyphs should be automagically hinted before a font is generated
or rasterized.<BR Clear=ALL>
</DL>
<P>
<IMG SRC="prefs-pshints.png" WIDTH="502" HEIGHT="360" ALIGN="Right">
<DL>
<DT>
StandardSlopeError
<DD>
The maximum slope difference that still allows two elements to be considered
as parallel. Enlarging this value makes autohinter more tolerable to small
deviations from straight lines when detecting stem hints.
<DT>
SerifSlopeError
<DD>
Serifs and other small features usually have to be allowed to deviate from
parallellness more than stem edges.
</DL>
<P>
I am testing a few hinting options there are three radio button sets which
add the following hints:
<TABLE BORDER CELLPADDING="2" WIDTH=500>
<CAPTION>
PS <A NAME="Hints">Hints</A>
</CAPTION>
<TR>
<TD><P ALIGN=Center>
<IMG SRC="hintboundingbox.png" WIDTH="119" HEIGHT="107"></TD>
<TD><P ALIGN=Center>
<IMG SRC="hintdiagonalinter.png" WIDTH="87" HEIGHT="72"></TD>
<TD><P ALIGN=Center>
<IMG SRC="hintdiagonalends.png" WIDTH="82" HEIGHT="166"></TD>
</TR>
<TR VALIGN="Top">
<TD>HintBoundingBoxes<BR>
Add hints around the bounding boxes of some glyphs. Adobe seems to do this.</TD>
<TD>HintDiagonalInter<BR>
Add hints at the intersections of diagonal stems</TD>
<TD>HintDiagonalEnds<BR>
Add hints at the ends of diagonal stems.</TD>
</TR>
</TABLE>
<P>
More importantly there is also the
<A NAME="DetectDiagonalStems">DetectDiagonalStems</A> option. Make sure this
is turned on if you intend to have FontForge
<A HREF="hintsmenu.html#AutoInstr">generate truetype instructions
automatically</A>. <BR CLEAR=ALL>
<P>
<IMG SRC="prefs-ttinstrs.png" WIDTH="502" HEIGHT="360" ALIGN="Right">
<A NAME="Instrs" HREF="hintsmenu.html#AutoInstr">Truetype autoinstructor</A>
bases its output on postscript hints, but it has also its own options:
<DL>
<DT>
InstructDiagonalStems
<DD>
Generate instructions for diagonal stem hints. For this option to be useful,
<A HREF="#DetectDiagonalStems">DetectDiagonalStems</A> must be enabled first.
Enabling this will lessen apparent weight inconsistencies, perceived at some
sizes whenever horizontal and vertical stems are controlled, but diagonals
are not.
<DT>
InstructSerifs
<DD>
Try to detect serifs and other elements protruding from base stems and generate
instructions for them: try to control distances between serifs' tips and
their base stems.
<DT>
InstructBallTerminals
<DD>
Generate instructions for ball terminals. They need different handling than
other kinds of serifs.
<DT>
InterpolateStrongPoints
<DD>
Instructing stems is sometimes not enough. This option makes FontForge to
interpolate some important points (sharp corners, inflections, curve extremes),
not affected by other instructions, between stem edges. Both parallel and
perpendicular extremes are controlled. Agressive optimization is employed,
to still leave as many points as possible to IUP, but manual review is
nevertheless greatly adviced.
<DT>
CounterControl
<DD>
Make sure similar or equal counters remain the same in gridfitted outlines.
This was inspired by, but works somewhat independently from,
<A HREF="charinfo.html#CounterMasks">PS Counter Hints</A>. Enabling this
option means that proper shapes are more important than proper scaling of
advance widths.
</DL>
<P>
<BR CLEAR=ALL>
<P>
<IMG SRC="prefs-opentype.png" WIDTH="502" HEIGHT="360" ALIGN="Right">
<DL>
<DT>
<A NAME="UseNewIndicScripts">UseNewIndicScripts</A>
<DD>
MS has changed the way it handles indic scripts and has created a parallel
set of script tags for the new method. Set this flag if you want to create
a font using the new Indic system.
<!--
<DT>
AddDFLTScript
<DD>
Someone from Adobe recommended that almost all features should be active
in the DFLT script. So setting this flag will mean the ff will output most
features in the OpenType sub-table for the DFLT script.
--> <BR Clear=ALL>
</DL>
<P>
<IMG SRC="prefs-script.png" WIDTH="502" HEIGHT="485" ALIGN="Right"><A NAME="scripts">This
section </A>of the dialog allows you to define built in scripts that will
show up in the <A HREF="filemenu.html#ScriptMenu">script menu</A>. Each entry
has two things associated with it, the menu name and a script file. The menu
name will be the name of this entry inside the script menu, and the
<A HREF="scripting.html">script file</A> will be the filename of the file
to be invoked. The "..." button allows you to browse for script files, which
I think have extension .pe (but which can have whatever extension you prefer
if you don't like my conventions).<BR Clear=All>
<P>
<IMG SRC="prefs-macfeat.png" WIDTH="502" HEIGHT="485" ALIGN="Right">The
<A NAME="Mac">Mac</A> Features dialog allows you to define a set of default
names (in many languages) for mac features and settings. These names are
placed in the 'name' table whenever a feature/setting is used in a generated
'morx' table. (Thus if you have some common ligatures in your font, then
the "ligature" feature names, and the "common ligature" setting names will
be added to the 'name' table).
<P>
You may also use this dialog to establish which setting(s) should be on by
default in a given feature and whether the feature only allows one setting
to be on at a time (the settings are mutually exclusive). All of this data
may be overridden by the similar dialog in the
<A HREF="fontinfo.html#Mac-Features">Element->Font Info </A>dialog.
<P>
<IMG SRC="macfeature.png" WIDTH="258" HEIGHT="369" ALT="Mac Feature dialog"
ALIGN="Left">To edit an existing feature double click on that feature in
the list (at right) this will bring up the dialog on the left. Each feature
must be assigned a unique number. You should indicate whether it has mutually
exclusive features or not. You should provide names for the feature in various
languages, and you should provide settings for the feature.
<P>
To add a new name press the [New] button under the name list and you will
be prompted for a language and a name.
<P>
To add a new setting press the [New] button under the setting list. The setting
dialog contains the numeric value of this setting (Apple has decreed that
if the feature is not mutually exclusive, all settings must be even numbers),
whether this setting is on by default, and then a list of names for the setting
in as many languages as you like.<BR CLEAR=ALL>
<IMG SRC="MacFeatName.png" ALIGN="Right" WIDTH="263" HEIGHT="125"><IMG SRC="macFeatureSetting.png"
WIDTH="263" HEIGHT="216" ALIGN="Left"><BR CLEAR=ALL>
<P>
<IMG SRC="prefs-macmap.png" WIDTH="502" HEIGHT="485" ALIGN="Right">The Mac
<A NAME="Mapping">Mapping</A> dialog allows you to define a mapping between
OTF <CODE>GSUB</CODE> feature tags and Apple's
<A HREF="http://developer.apple.com/fonts/TTRefMan/RM06/Chap6morx.html"><CODE>mort/morx
</CODE></A>Feature/Setting codes.
<P>
<A HREF="http://developer.apple.com/fonts/Registry/index.html">Apple's published
list </A>of features and settings appears out of date (in that some features
used by current fonts are not found in it).
<P>
A four letter OTF feature tag may correspond to a mac feature/setting
combination. If you wish to create a new mapping you must first insure that
the mac feature setting you desire is present in the feature list (above),
and then you may add the mappings.
<P>
<IMG SRC="MacMapping.png" WIDTH="337" HEIGHT="198" ALIGN="Left">You must
specify a mac feature (which must already be defined), a mac setting code
and a 4 character opentype tag.<BR CLEAR=ALL>
<H2>
Other ways of configuring
</H2>
<P>
A number of things that might be controlled from a preference window are
controlled by
<UL>
<LI>
<A HREF="xres.html">X Resources</A>
<LI>
<A HREF="cliargs.html#Environment">Environment Variables</A>
</UL>
<P ALIGN=Center>
-- <A HREF="filemenu.html">Prev</A> -- <A HREF="overview.html">TOC</A> --
<A HREF="filemenu.html">Next</A> --
<P>
</DIV>
</BODY></HTML>
distrib
>
Mageia
>
5
>
i586
>
media
>
core-release
>
by-pkgid
>
6b465285c9860724a695461ac61807f4
>
files
>
628
