diff options
author | Kaleb Keithley <kaleb@freedesktop.org> | 2003-11-25 19:28:33 +0000 |
---|---|---|
committer | Kaleb Keithley <kaleb@freedesktop.org> | 2003-11-25 19:28:33 +0000 |
commit | b1ee756a2b3769dedbcc7abbb94f560195bca4c7 (patch) | |
tree | c221a1be79be6ecd4e1e3d5586fa4eb683528726 /sgml | |
parent | b050d760f72956e04705abb6bbe69fb5e7a6a8c3 (diff) |
XFree86 4.3.99.16 Bring the tree up to date for the Cygwin folksxf86-4_3_99_16
Diffstat (limited to 'sgml')
-rw-r--r-- | sgml/LICENSE.sgml | 116 | ||||
-rw-r--r-- | sgml/README.sgml | 4 | ||||
-rw-r--r-- | sgml/RELNOTES.sgml | 63 | ||||
-rw-r--r-- | sgml/XKB-Config.sgml | 6 | ||||
-rw-r--r-- | sgml/add.sh | 4 | ||||
-rw-r--r-- | sgml/fonts.sgml | 162 | ||||
-rw-r--r-- | sgml/index.post | 11 | ||||
-rw-r--r-- | sgml/index.pre | 4 | ||||
-rw-r--r-- | sgml/mdefs.pre | 8 |
9 files changed, 289 insertions, 89 deletions
diff --git a/sgml/LICENSE.sgml b/sgml/LICENSE.sgml index d928d7c..0bb09db 100644 --- a/sgml/LICENSE.sgml +++ b/sgml/LICENSE.sgml @@ -8,7 +8,7 @@ <date>February 2003</date> <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/LICENSE.sgml,v 1.12 2003/02/24 03:41:16 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/LICENSE.sgml,v 1.16 2003/10/26 12:17:17 herrb Exp $ </ident> <sect>XFree86 License @@ -177,6 +177,120 @@ are met: OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +<sect2>The NetBSD Foundation, Inc. +<p> +Copyright (c) 2003 The NetBSD Foundation, Inc. +All rights reserved. + +This code is derived from software contributed to The NetBSD Foundation +by Ben Collver <collver1@attbi.com> + + Redistribution and use in source and binary forms, with or without + modification, are permitted provided that the following conditions + are met: +<enum> +<item> Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. +<item> Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. +<item> All advertising materials mentioning features or use of this software + must display the following acknowledgement: + This product includes software developed by the NetBSD + Foundation, Inc. and its contributors. +<item> Neither the name of The NetBSD Foundation nor the names of its + contributors may be used to endorse or promote products derived + from this software without specific prior written permission. +</enum> + + THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS + ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED + TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR + PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS + BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR + CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF + SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS + INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN + CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) + ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE + POSSIBILITY OF SUCH DAMAGE. + +<sect2>Theodore Ts'o. +<p> +Copyright Theodore Ts'o, 1994, 1995, 1996, 1997, 1998, 1999. All +rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: +<enum> +<item>Redistributions of source code must retain the above copyright + notice, and the entire permission notice in its entirety, + including the disclaimer of warranties. +<item>Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. +<item>he name of the author may not be used to endorse or promote + products derived from this software without specific prior + written permission. +</enum> + +THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED +WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF +WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE +LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR +CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT +OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR +BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF +LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE +USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH +DAMAGE. + +<sect2>Theo de Raadt and Damien Miller +<p> +Copyright (c) 1995,1999 Theo de Raadt. All rights reserved. +Copyright (c) 2001-2002 Damien Miller. All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: +<enum> +<item> Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. +<item> Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. +</enum> + +THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR +IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES +OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. +IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, +INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, +DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY +THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT +(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF +THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. + +<sect2>Todd C. Miller +<p> +Copyright (c) 1998 Todd C. Miller <Todd.Miller@courtesan.com> + +Permission to use, copy, modify, and distribute this software for any +purpose with or without fee is hereby granted, provided that the above +copyright notice and this permission notice appear in all copies. + +THE SOFTWARE IS PROVIDED "AS IS" AND TODD C. MILLER DISCLAIMS ALL +WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES +OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL TODD C. MILLER BE LIABLE +FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES +WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION +OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN +CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. + <sect1>NVIDIA Corp <p> Copyright (c) 1996 NVIDIA, Corp. All rights reserved. diff --git a/sgml/README.sgml b/sgml/README.sgml index eb115af..b121882 100644 --- a/sgml/README.sgml +++ b/sgml/README.sgml @@ -16,7 +16,7 @@ <date>26 February 2003 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml,v 3.134 2003/02/27 01:19:32 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml,v 3.135 2003/10/18 13:30:27 dawes Exp $ </ident> <abstract> @@ -63,8 +63,10 @@ software. If you find problems with this snapshot, you are encouraged to report your findings to the public XFree86 mailing list: <email>XFree86@XFree86.org</email>. +<![ %relcandidate [ XFree86 &relvers; is a feature-complete snapshot of XFree86 &nextfullrelvers;. +]]> ]]> <p> diff --git a/sgml/RELNOTES.sgml b/sgml/RELNOTES.sgml index 4fb915d..dc6e6cf 100644 --- a/sgml/RELNOTES.sgml +++ b/sgml/RELNOTES.sgml @@ -6,10 +6,10 @@ <title>Release Notes for XFree86™ &relvers; <author>The XFree86 Project, Inc -<date>26 February 2003 +<date>21 November 2003 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml,v 1.81 2003/02/27 00:45:05 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/RELNOTES.sgml,v 1.83 2003/11/21 05:44:11 dawes Exp $ </ident> <abstract> @@ -41,32 +41,47 @@ in 3.3.x. Our <htmlurl name="Driver Status document" url="Status.html"> summarizes how the hardware driver support compares between &legacyvers; and &relvers;. Please check there first before downloading &relvers;. -The 4.0.1 release introduced a new graphical configuration tool, -"<tt>xf86cfg</tt>", and a text mode interface was added to it for the -4.0.2 release. It is the preferred configuration tool provided by with -XFree86. The trusty old text-based tool "<tt>xf86config</tt>" can also -be used for generating X server config files. In addition to these -tools, the XFree86 server has some built in capabilities for generating -a base config file. This works well for most hardware, and in most -cases is the easiest way to get an initial config file. To try it out, -just run (as root): +XFree86 4.4 introduces an automatic configuration mechanism for the +XFree86 server. This makes it possible to start XFree86 in a usable +way without first creating a configuration file. The initial automatic +configuration support is currently targetted towards Linux and FreeBSD. +Automatic configuration will be supported on other platforms in future +releases. If you're running Linux or FreeBSD, try it out if you don't +already have a working <tt>XF86Config</tt> file. If you want to customise +things afterwards, you can cut and paste the automatically generated +configuration from the <tt>/var/log/XFree86.0.log</tt> file into an +<tt>XF86Config</tt> file and make your customisations there. Runtime +and dynamic configuration is planned for future releases. + +If you don't have any luck with automatic configuration, or you are using +a platform that it isn't currently supported on, try one of the older +methods for getting started. + +XFree86 comes with a graphical configuration tool called "<tt>xf86cfg</tt>". +It also has a text mode interface. It can be used to create an iniital +configuration file, and to customise existing configurations. + +Next in the order of configuration preferences is to make use of the +XFree86 server's ability to create a starting configuration file. To +do this, just run (as root): <tscreen><verb> XFree86 -configure </verb></tscreen> -Each of these configuration options will give you a reasonable starting -point for a suitable configuration file. We've put some effort into -documenting the &relvers; config file format, and you can find that -information in the <htmlurl name="XF86Config manual page" -url="XF86Config.5.html">. Check there and the driver-specific manual -pages and the related documentation for further information. References -to this driver-specific information can be found in the <ref id="drivertables" -name="tables below">. +and follow the instructions. -We have plans to make the configuration file optional in a future release. -The XFree86 server is close to being able to automatically determine -a complete base configuration for most popular hardware configurations. +Finally, the trusty old text-based tool "<tt>xf86config</tt>" can also +be used for generating X server config files. + +At least one of these configuration options will give you a reasonable +starting point for a suitable configuration file. With the automatic +mechanism you might even find that you don't need one! If you do need +to customise the configuration file, you can find it fully documented +in the <htmlurl name="XF86Config manual page" url="XF86Config.5.html">. +Also check the driver-specific manual pages and the related documentation +for further information. References to this driver-specific information +can be found in the <ref id="drivertables" name="tables below">. Before you go to download and install the binary distributions for this release, please have a quick read through the <htmlurl @@ -96,6 +111,8 @@ don't have enough space to cover them all here. <sect>Summary of new features in &fullrelvers;. +<sect1>NEEDS TO BE UPDATED + <sect1>Video Driver Enhancements <p> @@ -248,7 +265,7 @@ don't have enough space to cover them all here. <item> Various Cygwin support updates, including an experimental rootless X server for Cygwin/XFree86. -<item> AMD x86-64 support (primarily for Linux so far) has been added. +<item> AMD AMD64 support (primarily for Linux so far) has been added. <item> Support added for OpenBSD/sparc64. diff --git a/sgml/XKB-Config.sgml b/sgml/XKB-Config.sgml index 564fe03..c1b352b 100644 --- a/sgml/XKB-Config.sgml +++ b/sgml/XKB-Config.sgml @@ -6,7 +6,7 @@ <date>25 November 2002 <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/XKB-Config.sgml,v 1.2 2003/02/25 19:31:02 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/XKB-Config.sgml,v 1.4 2003/09/21 01:55:03 dawes Exp $ </ident> <abstract> @@ -27,7 +27,7 @@ need to touch any of xkb configuration files. <sect>Selecting XKB Configuration <p> The easiest and the most natural way how to specify a keyboard mapping is -tu use <tt>rules</tt> component. As its name suggests it describes a number of general +to use <tt>rules</tt> component. As its name suggests it describes a number of general rules how to combine all bits and pieces into a valid and useful keyboard mapping. All you need to do is to select a suitable rules file and then to feed it with a few parameters that will adjust the keyboard behaviour to @@ -105,7 +105,7 @@ EndSection Of course, this can be also done at runtime using utility setxkbmap. Shell command loading the same keyboard mapping would look like: <tscreen><verb> -setxkmap -rules xfree86 -model logicordless -layout "us,cz,de" \ +setxkbmap -rules xfree86 -model logicordless -layout "us,cz,de" \ -option "grp:alt_shift_toggle" </verb></tscreen> diff --git a/sgml/add.sh b/sgml/add.sh index f3d1671..86bc7e8 100644 --- a/sgml/add.sh +++ b/sgml/add.sh @@ -1,11 +1,11 @@ #!/bin/sh # -# $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/add.sh,v 1.1 1999/08/23 09:06:04 dawes Exp $ +# $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/add.sh,v 1.3 2003/10/19 00:58:11 dawes Exp $ # name=`basename $1 .sgml` sgmlfmt -f index $name.sgml | \ sed -e 's,<title>,<item><htmlurl name=",' \ - -e 's,</title>," url="'$name.html'">,' \ + -e 's,</title>," url="'$name.html'"> <htmlurl name="[PDF]" url="'../PDF/$name.pdf'">,' \ -e 's,<author>,<!-- ,' \ -e 's,</author>, -->,' \ -e 's,<date>,<!-- ,' \ diff --git a/sgml/fonts.sgml b/sgml/fonts.sgml index 1feab53..ff4ab93 100644 --- a/sgml/fonts.sgml +++ b/sgml/fonts.sgml @@ -6,10 +6,10 @@ <title>Fonts in XFree86 <author>Juliusz Chroboczek, <email/jch@xfree86.org/ -<date>17 January 2003</date> +<date>17 November 2003</date> <ident> -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/fonts.sgml,v 1.20 2003/01/20 03:43:07 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/fonts.sgml,v 1.22 2003/11/19 01:44:58 dawes Exp $ </ident> <toc> @@ -1016,9 +1016,9 @@ name to a font name. A `<tt/fonts.alias/' file might look as follows: <sect1>Additional notes about scalable core fonts -<p>The FreeType backend (module `<tt/freetype/', formerly known -as <it/xfsft/) is able to deal with both TrueType and Type 1 -fonts. This puts it in conflict with the X-TT and Type 1 +<p>The FreeType (libfreetype-xtt2) backend (module `<tt/freetype/', +formerly known as <it/xfsft/) is able to deal with both TrueType and +Type 1 fonts. This puts it in conflict with the X-TT and Type 1 backends respectively. If both the FreeType and the Type 1 backends are loaded, the @@ -1026,73 +1026,125 @@ FreeType backend will be used for Type 1 fonts. If both the FreeType and X-TT backends are loaded, X-TT will be used for TrueType fonts. -<sect2>Delayed glyph rasterisation +<sect2>About the <it/FreeType/ backend + +<p>The <it/FreeType/ (libfreetype-xtt2) backend (formerly <it/xfsft/) +is a backend based on version 2 of the FreeType library (see <url +url="http://www.freetype.org/" name="the FreeType web site">) and has +the X-TT functionalities for CJKV support provided by the After X-TT +Project (see <url url="http://x-tt.sourceforge.jp/" name="the After X-TT +Project web site">). The <it/FreeType/ module has support for the +``fontenc'' style of internationalisation (see <ref id="sec:fontenc" +name="The fontenc layer">). This backend supports TrueType font files +(`<tt/*.ttf/'), OpenType font files (`<tt/*.otf/'), TrueType Collections +(`<tt/*.ttc/'), OpenType Collections (`<tt/*.otc/') and Type 1 font +files (`<tt/*.pfa/' and `<tt/*.pfb/'). -<p>Both FreeType and X-TT delay glyph rasterisation up to the time at -which a glyph is first used. For this reason, they only provide an -approximate value for the ``average width'' font property. +In order to access the faces in a TrueType Collection file, the face +number must be specified in the fonts.dir file before the filename, +within a pair of colons, or by setting the 'fn' TTCap option. For example, -Both backends also support an optimisation for character-cell fonts -(fonts with all glyph metrics equal, or terminal fonts). A font with -an XLFD specifying a character-cell spacing `<tt/c/', as in <tscreen><verb> --misc-mincho-medium-r-normal--0-0-0-0-c-0-jisx0208.1990-0 +:1:mincho.ttc -misc-pmincho-medium-r-normal--0-0-0-0-p-0-jisx0208.1990-0 </verb></tscreen> -will not rasterise glyphs at metrics computation time, but instead -trust the font really to be a character-cell font. You are -encouraged to make use of this optimisation when useful, but be warned -that not all monospaced fonts are character-cell fonts. -<sect2>About the <it/FreeType/ backend +refers to face 1 in the `<tt/mincho.ttc/' TrueType Collection file. -<p>The <it/FreeType/ backend (formerly <it/xfsft/) is a backend based -on version 2 of the FreeType library (see <url -url="http://www.freetype.org/" name="the FreeType web site">) and has -support for the ``fontenc'' style of internationalisation (see -<ref id="sec:fontenc" name="The fontenc layer">). This backend -supports TrueType font files (`<tt/*.ttf/'), OpenType font files -(`<tt/*.otf/'), TrueType Collections (`<tt/*.ttc/'), OpenType -Collections (`<tt/*.otc/') and Type 1 font files (`<tt/*.pfa/' and -`<tt/*.pfb/'). +The new <it/FreeType/ backend supports the extended +`<tt/fonts.dir/' syntax introduced by X-TrueType with a number +of options, collectively known as `TTCap'. A `TTCap' entry follows the +general syntax + +<tscreen><verb> +option=value: +</verb></tscreen> + +and should be specified before the filename. The new <it/FreeType/ +almost perfectly supports TTCap options that are compatible with X-TT +1.4. The Automatic Italic (`<tt/ai/'), Double Strike (`<tt/ds/') and +Bounding box Width (`<tt/bw/') options are indispensable in CJKV. +For example, -In order to access the faces in a TrueType Collection file, the face -number must be specified in the fonts.dir file before the filename -within colons. For example, <tscreen><verb> -:2:mincho.ttc -misc-mincho-medium-r-normal--0-0-0-0-c-0-jisx0208.1990-0 +mincho.ttc -misc-mincho-medium-r-normal--0-0-0-0-c-0-jisx0208.1990-0 +ds=y:mincho.ttc -misc-mincho-bold-r-normal--0-0-0-0-c-0-jisx0208.1990-0 +ai=0.2:mincho.ttc -misc-mincho-medium-i-normal--0-0-0-0-c-0-jisx0208.1990-0 +ds=y:ai=0.2:mincho.ttc -misc-mincho-bold-i-normal--0-0-0-0-c-0-jisx0208.1990-0 +bw=0.5:mincho.ttc -misc-mincho-medium-r-normal--0-0-0-0-c-0-jisx0201.1976-0 +bw=0.5:ds=y:mincho.ttc -misc-mincho-bold-r-normal--0-0-0-0-c-0-jisx0201.1976-0 +bw=0.5:ai=0.2:mincho.ttc -misc-mincho-medium-i-normal--0-0-0-0-c-0-jisx0201.1976-0 +bw=0.5:ds=y:ai=0.2:mincho.ttc -misc-mincho-bold-i-normal--0-0-0-0-c-0-jisx0201.1976-0 </verb></tscreen> -refers to face 2 in the `<tt/mincho.ttc/' TrueType Collection file. -The <it/FreeType/ backend uses the <it/fontenc/ layer in order to -support recoding of fonts; this was described in <ref -id="sec:fontenc" name="The fontenc layer"> and especially <ref -id="sec:fontenc-freetype" name="FreeType-specific notes about -fontenc"> earlier in this document. +setup the complete combination of jisx0208 and jisx0201 using mincho.ttc +only. More information on the TTCap syntax is found on <url +url="http://x-tt.sourceforge.jp/" name="the After X-TT Project page">. + +The <it/FreeType/ backend uses the <it/fontenc/ layer in order to support +recoding of fonts; this was described in <ref id="sec:fontenc" name="The +fontenc layer"> and especially <ref id="sec:fontenc-freetype" +name="FreeType-specific notes about fontenc"> earlier in this document. <sect2>About the <it/X-TrueType/ TrueType backend <label id="sec:X-TT"> -<p>The `X-TrueType' backend is a backend based on version 1 of the -FreeType library. X-TrueType doesn't use the `fontenc' layer for -managing font encodings, but instead uses its own database of -encodings. +The `X-TrueType' backend is a backend based on version 1 of the FreeType +library. X-TrueType doesn't use the `fontenc' layer for managing font +encodings, but instead uses its own database of encodings. + +Since the functionalities for CJKV support introduced by X-TT have been +merged into the new <it/FreeType/ backend, the X-TT backend will be +removed from XFree86's tree near the future. Therefore, the use of +<it/FreeType/ backend is preferred over the X-TT backend. + +General information on X-TrueType may be found at <url +url="http://x-tt.sourceforge.jp/" name="the After X-TT Project page">. + +<sect2>Delayed glyph rasterisation + +<p>When loading a large character set, the old <it/FreeType/ delayed +glyph rasterisation until the time at which the glyph was first used. +The new FreeType (libfreetype-xtt2) has an improved `very lazy' metric +calculation method to speed up the process when loading TrueType or +OpenType fonts. Although the <it/X-TT/ module also has this method, +the "<tt/vl=y/" TTCap option must be set if you want to use it. This +is the default method for <it/FreeType/ when it loads multi-byte fonts. +Even if you use a unicode font which has tens of thousands of glyphs, +this delay will not be worrisome as long as you use the new <it/FreeType/ +backend -- its `very lazy' method is super-fast. + +The maximum error of bitmap position using `very lazy' method is 1 pixel, +and is the same as that of a character-cell spacing. When the X-TT +backend is used with the `<tt/vl=y/' option, a chipped bitmap is displayed +with certain fonts. However, the new FreeType backend has minimal problem +with this, since it corrects left- and right-side bearings using +`italicAngle' in the TrueType/OpenType post table, and does automatic +correction of bitmap positions when rasterisation so that chipped bitmaps +are not displayed. Nevertheless if you don't want to use the `very lazy' +method when using multi-bytes fonts, set `<tt/vl=n/' in the TTCap option to +disable it: + +<tscreen><verb> +vl=n:luxirr.ttf -b&h-Luxi Serif-medium-r-normal--0-0-0-0-p-0-iso10646-1 +</verb></tscreen> + +Of course, both backends also support an optimisation for character-cell +fonts (fonts with all glyph metrics equal, or terminal fonts). A font +with an XLFD specifying a character-cell spacing `<tt/c/', as in -X-TrueType extends the `<tt/fonts.dir/' syntax with a number of options, -collectively known as `TTCap'. A `TTCap' entry follows the general -syntax <tscreen><verb> -:option=value: +-misc-mincho-medium-r-normal--0-0-0-0-c-0-jisx0208.1990-0 </verb></tscreen> -and should be specified before the filename. -The most useful TTCap option is used to specify the face number to use -with TTCs; this is the `<tt/fn/' TTCap option. For example, face 2 of -font file `<tt/mincho.ttc/' is specified using: +or + <tscreen><verb> -:fn=2:mincho.ttc -misc-mincho-medium-r-normal--0-0-0-0-c-0-jisx0208.1990-0 +fs=c:mincho.ttc -misc-mincho-medium-r-normal--0-0-0-0-p-0-jisx0208.1990-0 </verb></tscreen> -More information on the TTCap syntax, and on X-TrueType in general, -may be found on <url url="http://x-tt.dsl.gr.jp/" name="the X-TrueType -home page">. + +will not compute the metric for each glyph, but instead +trust the font to be a character-cell font. You are +encouraged to make use of this optimisation when useful, but be warned +that not all monospaced fonts are character-cell fonts. <sect>Appendix: background and terminology <label id="sec:background"> <sect1>Characters and glyphs @@ -1247,8 +1299,8 @@ ancestor of <tt/mkfontscale/. might or might not contain related scribbles and development versions of software. -The documentation of <it/X-TrueType/ is available from -<url url="http://x-tt.dsl.gr.jp/" name="the X-TrueType home page">. +The documentation of <it/X-TrueType/ is available from <url +url="http://x-tt.sourceforge.jp/" name="the After X-TT Project page">. A number of East-Asian CIDFonts are available from <url name="O'Reilly's FTP site" diff --git a/sgml/index.post b/sgml/index.post index 17e6c2f..360a5e0 100644 --- a/sgml/index.post +++ b/sgml/index.post @@ -14,9 +14,18 @@ Manual pages: <p> ]]> +<![ %specdocs; [ +<p> +Other: +<itemize> +<item><htmlurl name="Specification and Related Documents" url="specindex.html"> +</itemize> +<p> +]]> + </article> <!-- -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/index.post,v 1.2 2000/03/21 19:57:10 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/index.post,v 1.3 2003/03/19 01:49:28 dawes Exp $ --> diff --git a/sgml/index.pre b/sgml/index.pre index 35b97ac..dff4c73 100644 --- a/sgml/index.pre +++ b/sgml/index.pre @@ -8,10 +8,10 @@ <!-- Title information --> <title>Documentation for XFree86™ version &relvers; <author>The XFree86 Project, Inc -<date>27 February 2003 +<date>18 October 2003 <!-- -$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/index.pre,v 1.19 2003/02/24 03:41:25 dawes Exp $ +$XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/index.pre,v 1.20 2003/10/19 00:58:39 dawes Exp $ --> <p> diff --git a/sgml/mdefs.pre b/sgml/mdefs.pre index ecf6540..2c6993b 100644 --- a/sgml/mdefs.pre +++ b/sgml/mdefs.pre @@ -1,4 +1,4 @@ -<!-- $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/mdefs.cpp,v 1.1 2000/03/21 19:57:11 dawes Exp $ --> +<!-- $XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/mdefs.cpp,v 1.2 2003/03/19 01:49:28 dawes Exp $ --> <!-- entity definitions for man pages --> @@ -8,6 +8,12 @@ <!ENTITY % manpages 'IGNORE'> #endif +#ifdef HTML_SPECS +<!ENTITY % specdocs 'INCLUDE'> +#else +<!ENTITY % specdocs 'IGNORE'> +#endif + <!ENTITY drvsuffix CDATA __drivermansuffix__ > <!ENTITY filesuffix CDATA __filemansuffix__ > <!ENTITY miscsuffix CDATA __miscmansuffix__ > |