[SLE] Use of :unscaled in font paths
`Steve's Linux' (not sure who the human is) posted this example of a FontPath setting for XF86Config a while ago: Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "unix/:7101" FontPath "/usr/X11R6/lib/X11/fonts/misc" FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1" FontPath "/usr/X11R6/lib/X11/fonts/URW" FontPath "/usr/X11R6/lib/X11/fonts/Speedo" FontPath "/usr/X11R6/lib/X11/fonts/75dpi" FontPath "/usr/X11R6/lib/X11/fonts/100dpi" However, the example in the XWindow Howto looks a little different: FontPath "/usr/X11R6/lib/X11/fonts/misc" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1" FontPath "/usr/X11R6/lib/X11/fonts/Speedo" Some of the difference may just be a matter of taste, but there's one substantive difference: the `/' before `:unscaled' that appears in the Howto but not in Steve's version. Does anyone know if the slash really belongs there or not? And if not, how X distinguishes between scaled and unscaled fonts when it's looking for a font with a particular name or description? Neither the Howto nor the XF86Config(5) man page is enlightening on this point. Is there a better place to look for information? Paul Abrahams Paul Abrahams -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"Paul W. Abrahams" wrote:
FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
Some of the difference may just be a matter of taste, but there's one substantive difference: the `/' before `:unscaled' that appears in the Howto but not in Steve's version.
Does anyone know if the slash really belongs there or not? And if not, how X distinguishes between scaled and unscaled fonts when it's looking for a font with a particular name or description?
The / shouldn't make any difference. Just type both from a cmd line. You end up at the same spot. I think X searches each dir in order. So first it checks whatever is the first line. Does it find something it likes? If so it stops and uses that. If not it continues. Repeats the process. IMHO one of the simplest fixes for fonts under X is to put the 100dpi stuff ahead of the 75dpi stuff. Things will normally improve quite a bit. On to the issue of Netscape and bad fonts I was forced yesterday to take a look at the ESPN site under windows with IE. Guess what? It's screwed up under IE also! Nick -- -------------------------------------------------- Nick Zentena "Microsoft has unjustifiably jeopardized the stability and security of the operating system." U.S. District Judge Thomas Penfield Jackson Nov 5/1999 -------------------------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Nick Zentena wrote:
"Paul W. Abrahams" wrote:
FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
Some of the difference may just be a matter of taste, but there's one substantive difference: the `/' before `:unscaled' that appears in the Howto but not in Steve's version.
Does anyone know if the slash really belongs there or not? And if not, how X distinguishes between scaled and unscaled fonts when it's looking for a font with a particular name or description?
The / shouldn't make any difference. Just type both from a cmd line.
Are you saying that a/:b and a:b are equivalent if typed from a command line?
You end up at the same spot. I think X searches each dir in order. So first it checks whatever is the first line. Does it find something it likes? If so it stops and uses that. If not it continues.
The question is how X determines if a particular directory contains ``something it likes''. While looking in a particular directory, does X have a way of distinguishing between scaled and unscaled fonts? If it does, what's the criterion?
IMHO one of the simplest fixes for fonts under X is to put the 100dpi stuff ahead of the 75dpi stuff. Things will normally improve quite a bit.
That was my experience also. I'd be interested in knowing why that's the case, though. Paul -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"Paul W. Abrahams" wrote:
Nick Zentena wrote:
"Paul W. Abrahams" wrote:
FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
Some of the difference may just be a matter of taste, but there's one substantive difference: the `/' before `:unscaled' that appears in the Howto but not in Steve's version.
Does anyone know if the slash really belongs there or not? And if not, how X distinguishes between scaled and unscaled fonts when it's looking for a font with a particular name or description?
The / shouldn't make any difference. Just type both from a cmd line.
Are you saying that a/:b and a:b are equivalent if typed from a command line?
I was thinking along Nicks line when I read this first this morning: /foo/bar equals /foo/bar/, were in the latter case a "/" is added that's not nessesarry, but both means the same. One part is a path, the other a statement or parameter separated ba a colon (/foo/bar:xyz). Nothing wrong.... Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Juergen Braukmann wrote:
/foo/bar equals /foo/bar/, were in the latter case a "/" is added that's not nessesarry, but both means the same. One part is a path, the other a statement or parameter separated ba a colon (/foo/bar:xyz). Nothing wrong....
It's possible to read /foo/bar/:xyz as the :xyz entry in the /foo/bar/ directory, since :xyz is a valid, if peculiar, filename (and one that doesn't work in all contexts, either). But I see now how to parse /foo/bar/:xyz. Thanks. Paul -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"Paul W. Abrahams" wrote:
Are you saying that a/:b and a:b are equivalent if typed from a command line?
Actually I was saying that something like /etc is equal to /etc/ The trailing / is not an issue. Your example looks good though.
The question is how X determines if a particular directory contains ``something it likes''. While looking in a particular directory, does X have a way of distinguishing between scaled and unscaled fonts? If it does, what's the criterion?
Doesn't scaled/unscale relate to if X is allowed to scale? That was my understanding. My understanding was that it looks at the first line in your XF86Config file. If a font with a matching name is found it's used. If not it goes to the next line. By placing unscaled first you are telling it that it should keep going if it doesn't find a font that can be shown unscaled. So it keeps going to the next line. The lines without unscaled are a catch all I guess. If it can't find a better choice it will scale.
IMHO one of the simplest fixes for fonts under X is to put the 100dpi stuff ahead of the 75dpi stuff. Things will normally improve quite a bit.
That was my experience also. I'd be interested in knowing why that's the case, though.
More dpi is better then less. The same thing with laser printer or anything else that prints by dots. 100dpi should be using smaller dots and allowing a better image. I think the first macs were 72dpi. Sounds worse then 75 but those were 9" screens. Nick -- -------------------------------------------------- Nick Zentena "Microsoft has unjustifiably jeopardized the stability and security of the operating system." U.S. District Judge Thomas Penfield Jackson Nov 5/1999 -------------------------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Nick Zentena wrote:
Doesn't scaled/unscale relate to if X is allowed to scale? That was my understanding. My understanding was that it looks at the first line in your XF86Config file. If a font with a matching name is found it's used. If not it goes to the next line. By placing unscaled first you are telling it that it should keep going if it doesn't find a font that can be shown unscaled.
Ah, that's the question! How does X determine if a particular font can be shown unscaled? Also, do you know the roles of the fonts.dir and fonts.scaled files (if they have a role) in the search? And more generally, where can I go to read about all of this? Thanks. Paul -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"Paul W. Abrahams" wrote:
Ah, that's the question! How does X determine if a particular font can be shown unscaled?
I'm guessing [but that's okay isn't it-)] that the font file includes one or more actual font sizes. Be it bitmapped or something different. So if for example you ask for 12pt fancyfont#123 it looks at the file and if it's there then it doesn't need to be scaled. If the font file lacks the info then it must be scaled. A font that can be shown unscaled must already exist ready to be shown. Scaling if for all the other point sizes.
Also, do you know the roles of the fonts.dir and fonts.scaled files (if they have a role) in the search?
No idea.
And more generally, where can I go to read about all of this?
There must be a general X book out there. My first choice would likely be something from O'Reilly. I can't vouch for any of these books but having read various other O'Reilly books they would be my first choice. X Window System Administrator's Guide Paperback | 372 Pages | ISBN 0937175838 Series: Definitive Guides To The X Window System Published in 1992 by O'reilly And Associates X Window System User's Guide, Motif Edition: Volume 3m by Valerie Quercia , Tim O'Reilly Paperback | 956 Pages | ISBN 1565920155 Series: Definitive Guides To The X Window System Published in 1993 by O'reilly And Associates Orients the new user to Window system concepts and provides detailed tutorials for many client programs, including the xterm terminal emulator and window managers. This popular manual is available in two editions, one for users of the MIT software, one for users of Motif. Revised for X11 Release 5 and Motif 1.2 http://www.oreilly.com/ Nick -- -------------------------------------------------- Nick Zentena "Microsoft has unjustifiably jeopardized the stability and security of the operating system." U.S. District Judge Thomas Penfield Jackson Nov 5/1999 -------------------------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
abrahams＠mbs.valinet.com -
juergen.braukmann＠ruhr-west.de -
zentena＠hophead.dyndns.org