Mercurial > hg > xemacs-beta

comparison man/xemacs-faq.texi @ 4509:dd12adb12b8f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Fix broken Xft FAQ.
author Stephen J. Turnbull <stephen@xemacs.org>
date Sat, 04 Oct 2008 13:57:55 +0900
parents a5f1da0eb001
children 4527fc976aa3
comparison
equal deleted inserted replaced
4507:83e35df20028 4509:dd12adb12b8f
6282 @end quotation 6282 @end quotation
6283 6283
6284 @node Q5.0.7, Q5.1.1, Q5.0.6, External Subsystems 6284 @node Q5.0.7, Q5.1.1, Q5.0.6, External Subsystems
6285 @unnumberedsubsec Q5.0.7: How can I use antialiased fonts under X11? 6285 @unnumberedsubsec Q5.0.7: How can I use antialiased fonts under X11?
6286 6286
6287 For this you need a recent beta version, and please consider the caveats 6287 The X11 version of XEmacs can use antialiased fonts via the Xft,
6288 that apply when using beta software from any source. Rebuild xemacs 6288 fontconfig, and freetype libraries. To configure this you need a recent
6289 using at least the following options to configure: 6289 beta version (at least 21.5.24); the more recent, the better. This is
6290 6290 beta software, the usual caveats apply. Rebuild xemacs using the
6291 @samp{./configure --enable-mule --with-xft=emacs,menubars} 6291 following configure options, plus any others you normally use:
6292 6292
6293 For further details on the XEmacs widgets that support XFT, see the 6293 @samp{--enable-mule --with-xft=emacs,menubars}
6294 output of @code{./configure --help}. You may find that you have to 6294
6295 install some lib[something]-dev packages to provide header files; see 6295 Xft @emph{may} work without Mule but the developers working on the Xft
6296 your packaging system's documentation. Depending on your platform, your 6296 code invariably build with Mule. The tab control also supports Xft, and
6297 packaging system will normally be something like RPM, @code{apt} or 6297 at some date the progress gauge will as well. If they are configured in
6298 DarwinPorts. 6298 to XEmacs, you may add @samp{tabs} and @samp{gauges} to the value of the
6299 @samp{--with-xft} option (with a comma separating each value from the
6300 previous ones). For further details on the XEmacs widgets that support
6301 XFT, see the output of @code{./configure --help}. If you use a package
6302 manager from your OS distribution, you may need to install development
6303 packages for @file{fontconfig} and @file{Xft}, and possibly for their
6304 prequisites.
6299 6305
6300 To specify a particular antialiased font, put something like the 6306 To specify a particular antialiased font, put something like the
6301 following lines in your @file{~/.Xdefaults} or @file{~.Xresources} 6307 following lines in your @file{~/.Xdefaults} or @file{~/.Xresources}:
6302 (using @code{#define} in @file{.Xresources} avoids boring hand
6303 substitution):
6304 6308
6305 @example 6309 @example
6306 #define MONO Mono 6310 XEmacs.default.attributeFont: monospace-12
6307 #define SANS Sans 6311 XEmacs.bold.attributeFont: monospace-12:style=Bold
6308 #define PTSIZEM 12 6312 XEmacs.italic.attributeFont: monospace-12:style=Oblique
6309 #define PTSIZES 11 6313 XEmacs.bold-italic.attributeFont: monospace-12:style=Bold Oblique
6310 XEmacs.default.attributeFont: MONO:size=PTSIZEM 6314 XEmacs.modeline.attributeFont: sans-serif-11
6311 XEmacs.bold.attributeFont: MONO:size=PTSIZEM:style=Bold 6315 XEmacs.menubar.xftFont: sans-serif-11
6312 XEmacs.italic.attributeFont: MONO:size=PTSIZEM:style=Oblique 6316 XEmacs*XftFont: sans-serif-11
6313 XEmacs.bold-italic.attributeFont: MONO:size=PTSIZEM:style=Bold Oblique
6314 XEmacs.modeline.attributeFont: SANS:size=PTSIZES
6315 XEmacs.menubar.font: SANS:size=PTSIZES
6316 XEmacs*xftFont: SANS:size=PTSIZES
6317 @end example 6317 @end example
6318 6318
6319 And run @code{xrdb -merge} before starting the new, XFT-enabled xemacs. 6319 @strong{Warning}: These resource naming conventions are just hacks to
6320 You can choose the available fonts from the list given by 6320 get the code running; you should expect them to change. (Sorry about
6321 @code{fc-list}; try @code{xfd -fa FONTNAME-SIZE} to preview a given font. 6321 that, but this @emph{is} beta software!)
6322
6323 Then run @code{xrdb -merge} before starting the new, XFT-enabled
6324 xemacs. You can choose the available fonts from the list given by
6325 @code{fc-list}; try @code{xfd -fa FONTNAME-SIZE} to preview a given
6326 font. Note that ``monospace'' and ``sans-serif'' are generic aliases
6327 defined by fontconfig which may correspond to any of many real fonts
6328 based on local configuration and availability of the aliased fonts,
6329 and so are likely to give good results in a well-set-up system.
6330
6331 Although Customize does not yet handle fontconfig fontspecs, you can
6332 pass them as strings directly to @samp{set-face-font} to set fonts from
6333 Lisp.
6322 6334
6323 @unnumberedsec 5.1: Microsoft Windows 6335 @unnumberedsec 5.1: Microsoft Windows
6324 6336
6325 @node Q5.1.1, Q5.1.2, Q5.0.7, External Subsystems 6337 @node Q5.1.1, Q5.1.2, Q5.0.7, External Subsystems
6326 @unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}? 6338 @unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?