Re: font compatability with PC installations of Word
From: Jeff Wiseman (wisemanja_at_earthlink.net)
Date: 02/11/05
- Next message: Beth Rosengard: "Re: Saving a Word 2001 doc in Word 2004"
- Previous message: Francis Hookam: "Re: Word paras in 2 cols"
- In reply to: John McGhie [MVP - Word and Word Macintosh]: "Re: font compatability with PC installations of Word"
- Next in thread: John McGhie [MVP - Word and Word Macintosh]: "Re: font compatability with PC installations of Word"
- Reply: John McGhie [MVP - Word and Word Macintosh]: "Re: font compatability with PC installations of Word"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 11 Feb 2005 21:52:52 GMT
John McGhie [MVP - Word and Word Macintosh] wrote:
> Hi Jeff:
>
> On 11/2/05 8:21 AM, in article
> nfQOd.5133$mG6.919@newsread1.news.pas.earthlink.net, "Jeff Wiseman"
> <wisemanja@earthlink.net> wrote:
<<stuff deleted>>
>>My past experience was primarily with PostScript printers which I
>>supposed reduce these types of problems a bit.
>
>
> Naaahhh.... They're worse :-) At least with an inkjet, you can rely on the
> fact that NO fonts are "resident" :-)
I guess I was thinking in terms of what the postscript code going
to the printer looks like. A line of text has all the text and
the starting coordinate so the line break will always be in the
same place regardless of the poscript printer used. However, I
now see the fallacy in that because the decision of how many
words and characters went on that line is a function of the
postscript driver that created it. I'm learning here.
>>1) Eliminate character changes when Microsoft fonts of the exact
>>same name but different versions are used.
>
> The older the font, the more trouble you're in. Mac fonts prior to OS X
> were largely non-Unicode. Very old PC fonts prior to Windows 95 were also
> non-Unicode.
I think I'm better off here as the installations I'm dealing with
are going to all be '98 and later (with few '98s)
> No font contains all 65,000 characters. But most of the Microsoft fonts
> contain the most common 576. Modern Apple fonts are the same: some of them
> do not contain such a wide range of characters. But within the Macintosh
> International character set, every character has the same character number.
>
> However, you have to be careful of Unicode characters in the "Private Use"
> area of the Unicode standard. The "Apple" symbol and the "Command" symbol
> are two. The Unicode value for those may produce a different character in a
> non-Apple font.
I've seen this. Using the character palatte or Font Book,
changing between fonts you can see those very characters jumping
around in position. My fear of the unknown was how many other
characters do this? I gather that in general, this doesn't happen.
> Ugh... I'm not sure on that one. I think "Arial" comes out of the same
> font foundry for both companies, but that the Mac version has about half the
> number of characters. Don't quote me on that.
I believe that this is true. That's why I'm trying to group my
fonts in order to isolate the mac ones from the ones provided by
MS. I made the mistake of hitting the "resolve duplicates" in the
Font Book utility when I was first getting used to this new
machine and OS (G5 iMac with OS 10.3.6). It proceeded to delete
all of the Mac versions of the Office font set since Office used
fonts that were all of newer versions. Since I wasn't initially
aware of how and where office installed its fonts, I didn't
realize I was going to have a scrambled mix in the Library/Font
areas.
>>What are the things that I CAN
>>control to minimize significant changes to a document when
>>someone receives it and displays it onver some other version of
>>Word on another platform?
>
>
> Your style definitions :-) Some important secrets:
>
> 1) No blank lines. None at all. You cannot control the pagination of a
> document that contains blank paragraphs.
>
> 2) No hard page breaks if you can possibly avoid them. Not because they're
> bad ion themselves, but because every time you change the document, you have
> to move them ALL. Use Keep With Next instead.
>
> 3) Use only "space after" on your body text. Don't use space before.
>
> 4) Use "space before" as well as space after on your headings.
>
> 5) Think carefully about where you use, and do not use, "Keep With Next".
> Basically, ON for headings and List styles, OFF for everything else.
>
> 6) Floating objects are very difficult to handle and error-prone. Try to
> avoid them as far as possible, because when they play up they really stuff
> your pagination.
>
> 7) Make a choice between Widow/Orphan Control versus Keep Lines Together
> for each style. Basically, I never use Widow/Orphan these days. Paper is
> not that expensive and readers hate chasing paragraphs across pages: it
> breaks their concentration and there's no need for it. Lawyers would have a
> different answer because of their very long paragraphs.
>
> 8) Set your margins correctly: allow for the binding margin, and don't
> allow anything to hang outside the page margins.
>
> 9) Resolve all of your Tracked Changes, then turn OFF Show/Hide to do your
> penultimate Proofing pass. Hidden and non-printing characters make a big
> difference.
>
> 10) The Print Preview view is editable: look up the Help to see how. Do
> your final proofing pass in Print Preview. When you do, be aware that Print
> Preview makes savage demands on your machine resources. Do very little
> editing in that view, stop as many other applications as you can before
> going into Print Preview, and Save very frequently: crashes are common due
> to the truly outrageous computing demands this view generates. The
> difference is that Print Preview reads the printer driver and draws every
> character individually, using the font outlines you are going to use to
> print with. The Print Preview display is within one pixel of perfect
> WYSIWYG. That requires sheer horsepower :-)
>
> 11) Make sure you have found and turned off "Allow A4/Letter resizing."
>
> 12) If you were silly enough to use "Shrink to fit" then you would be too
> silly to be asking these questions, so I am sure you're not going to do that
> :-)
>
> There you go: "Camera-Ready Publishing With Microsoft Word, Course 101"
Thanks for that great list. Many items I tend to do anyway since
I'm had some involvement in setting up document templates for
some older tools like Interleaf and Framemaker. Your comment on
orphan/widow handling is interesting. I guess I've been doing
that as a mix because a lot of the document I used in the past
actually had mixes of very long (i.e., mulitple page) paragraphs
or tables mixed with many very short ones in the same document.
The default was to set some larger orphin/widow values and then
for the very short, set them to lock the whole paragraph or table
together.
Is there a particular issue with the A4 letter resizing? I've
never allowed it since on at least 2 other tools Ive used, it's
always had problems. We were usually forced to simply reformat
into and out of the A4 size when necessary. Is resizing screwy on
Word too?
Again, thanks for all the input, I hope these things are also of
benefit to others.
- Jeff
- Next message: Beth Rosengard: "Re: Saving a Word 2001 doc in Word 2004"
- Previous message: Francis Hookam: "Re: Word paras in 2 cols"
- In reply to: John McGhie [MVP - Word and Word Macintosh]: "Re: font compatability with PC installations of Word"
- Next in thread: John McGhie [MVP - Word and Word Macintosh]: "Re: font compatability with PC installations of Word"
- Reply: John McGhie [MVP - Word and Word Macintosh]: "Re: font compatability with PC installations of Word"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
