Now you need to be a little cautious criticizing latex's default - the macros default to sensible values appreciated by professional typesetters. It's easy to typeset your document in other fonts (\usepackage{palatino} or times, avantgar, etc), but it should be remembered that the package setting sets the entire family of associated shapes and weights. Thus your document may contain italic, slant, sc, bold and so on, and using a font package sets the whole range for those shapes and the correct wieghtings automatically. It's really in your best interest to follow the default family shapes that a package gives you, rather than doing a 'Word97' approach and deciding your own. In my experience, you can tell Word documents a mile off. They *always* look awful, usually for two reasons: i) the user tries to blend different fonts in their documents for headings etc (aargh!), ii) Word97's very poor typesetting abilities - virtually any word document will contain 'rivers' (white space running vertically between lines), in addtion to non-existant proper hyphenation. As for T3 fonts, I read last night in the documentation for Fontinst are rare and poorly supported. So I'm pretty sure your using type 1 fonts anyhow by default. That's certainly what mine is set up to do. Try the \usepackage command above after doing locate .mf to find the directory where the sty files are kept. You can be sure that the mf families are super high quality fonts, they scale correctly unlike truetype, and just insert those with a *.sty into the package and everything else should be automatic. I'll wish you good luck, and as you said you were relatively new to latex, welcome to world of properly typeset documents! Most folk, after they finish their first latex document and get it printed, never want to return to the output of Word again. :-) k. On Wednesday, October 18, 2000 6:28 PM, Corvin Russell [SMTP:corvinr@sympatico.ca] wrote:

You can't be more mystified than I am! In the end I decided to use unbolded SC, because no matter how I fiddled and twiddled, I could not make it work. The t1cmr.fd is somewhat differently done than ot1cmr.fd, but not knowing the arcana I decided to take the aesthetic hit for convenience. I figured it would involve meta* to do it.

PS Why on Earth does latex default to bx for headings?

C

On Wed, Oct 18, 2000 at 12:14:38PM +0100, Kester Clegg wrote:

...

I am mystified as to why that should happen - but the output of latex mentions something about not finding the font:

LaTeX Font Warning: Font shape `OT1/cmr/bx/sc' undefined (Font) using `OT1/cmr/bx/n' instead on input line 101.

hence if the font shape does not exist or is not defined, it has to

make a

...

substitution. I imagine your type 3 fonts do have bold weighting for sc and so it can generate them. I remember at one point messing about with \definefont commands and having to check the weightings / shape of new definitions. Presumably the T1 encoding is able to use type 3 as well? I think the only solution if you're determined on using a particular font is generate your own bold sc using metapost (or maybe it's metafont?), and from the `Latex Graphics Companion' I gather that it is not an operation for the faint-hearted! k.

-- Corvin Russell

-- 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/faq

-- 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/faq