Re: Keynote und fehlende Schriften

Noses schrieb am 2006-09-08 in <news:45015e9f@xxxxxxxxxxxx>
ArialMS ist ein Paradebeispiel - auf dem Mac brauchs Du das nur, damit
unter Windows erstellte Dokumente auf dem Mac genauso krank aussehen wie
unter Windwos.

Na, wenn Du mal nicht ziemlich daneben liegst, weil das auf die Arial eben
nicht zutrifft, wohl aber auf Times(NewRoman) und Courier. Zur Arial und
der kreativen Umbenamsung in "ArialMS" siehe hier:

Regarding Microsoft's "bug-fix" release of Arial and Times fonts (see
previous item), we received an email from a software engineer at GCC
Technologies that goes into more detail on this matter, especially as it
related to a problem printing smart (or "curly") quotes to their
printers. It explains exactly why the problem occurs and offers a
critical view of Microsoft's solution:

I figured out what's going on with the curly quotes, etc., and why the
problem occurs with Arial and Times New Roman. The problem is not the
result of bugs in the printer versions of these fonts. Rather, it is due
to a mix-up between Microsoft's TrueType fonts and the LaserWriter
driver on how characters are mapped, which differs between the Mac and
the printer. The workaround is to download and install new versions of
Arial and Times New Roman from Microsoft's Typography web site.

Here's the longer explanation: Each Mac font has a couple of "font
class" bits which give the LaserWriter driver some info on how the
font's encoding vector (which maps ASCII codes to glyphs, or character
shapes) may need to be modified when the job is generated. Most Mac
fonts (from Apple and Adobe) say "re-encode me with the usual
MacEncoding vector". Mac fonts from Microsoft seem to say, "just use
whatever encoding vector I already have."

For more technical details on this, see Apple Technote 1140.

When most Mac fonts are used, the LaserWriter driver re-encodes them to
match the MacEncoding used by the Mac on screen. This is not the case
with the Microsoft fonts. However, the encoding that these fonts already
have is the MacEncoding, so when the font is downloaded as part of the
job, there is no need to re-encode it.

The problem occurs when the font is not downloaded, as with Arial and
Times New Roman on a printer that has the PS3 font set, which includes
them. Now, the Mac font says "use my existing encoding", so LaserWriter
does so. However, because it doesn't download the fonts, the job
actually references the versions which are built into the printer.
Unfortunately, these do not already have the MacEncoding. Instead, like
all other text fonts, they have the Adobe StandardEncoding. So, the
wrong glyphs get printed.

Fortunately, there is the work-around of the new Microsoft Mac fonts.
Did Microsoft take this opportunity to follow Apple's two-year-old
recommendations on how to indicate the presence of the Euro character?
No. Did Microsoft work around our problem by setting the "font class"
bits differently, so that when the font isn't downloaded, it would be
re-encoded? No. In typical Microsoft fashion, they chose another path.
The reason the LaserWriter driver doesn't download the fonts is that it
sees that either the printer or the PPD reports the font names "ArialMT"
and "TimesNewRomanPSMT" (and their variants), and these match the
PostScript font names embedded in the Microsoft Mac fonts. Well,
Microsoft changed the embedded PS names in the new versions to "ArialMS"
and "TimesNewRoman", etc.

With these installed, LaserWriter will not see a match, so it will
download these Mac fonts every time, thus avoiding the problem. Never
mind that this defeats the purpose of including the font in the printer
in the first place. Oh, well.

Hat also mehr mit EUR-Zeichen, Mac- vs. "Adobe Standard" Encoding und MacOS
9 bzw. dessen LaserWriter Treiber 8 zu tun als Dir lieb sein dürfte ;-)

(BTW: Und für genau das Problem gab es einen viel billigeren Workaround als
die Installation anders benamster Schriften. Im LaserWriter 8.7.x-Dialog
konnte man irgendwo einstellen, daß das Encoding des Fonts Vorrang vor
falschen Annahmen seitens Druckertreiber hatte. Damit waren jene Probleme
ebenfalls aus der Welt zu schaffen)

Irgendwie schon traurig, daß Microsoft, als eine Firma, die sehr viel
Kompetenz und Renommee im Bereich Computer-Typografie ansammeln konnte, dann
bei den Mac-Schriften *regelmäßig* so einen Mist baut(e).

Aber was das insgesamt mit dem Problem einer Apple-Anwendung zu tun hat, die
"einfach mal so" irgendwelche Schriften einbettet und dann durch idiotische
Fehlermeldungen glänzt, verstehe ich nicht so recht. Das ist doch ein
Problem mit dem Programm und keines mit den Schriften?

Oder stellt sich das so dar, daß Microsoft mit irgendeinem Office-Update
neue Versionen seiner Mac-Arial ausgeliefert hat, die dann bereits im System
befindlichen Arial-Font-Dateien überschrieben haben aber jetzt als interner
Schriftnamen *nicht mehr* "ArialMS" sondern eben nur noch "Arial" tragen?

Gruss,

Thomas
.

Relevant Pages

  • Re: Advice please on Styles for cross-platform?
    ... NOT a reason to "Just buy Microsoft Office", ... PDF on the Mac. ... the reason to use EMF is to keep your rotated text. ... But your comments on fonts, and what to expect from the MS ones vs others ...
    (microsoft.public.mac.office.word)
  • Re: 2004 Microsoft Word for Mac versus 11.03 Word for PC
    ... One last question - I didn't think there was an 11.03 - but when my Mac ... Microsoft provides fonts ... with Microsoft Office on the Mac that are carefully designed to match the ... unlikely to welcome or be able to use JPG or TIFF. ...
    (microsoft.public.mac.office.word)
  • Re: 2004 Microsoft Word for Mac versus 11.03 Word for PC
    ... One last question - I didn't think there was an 11.03 - but when my Mac ... Microsoft provides fonts ... with Microsoft Office on the Mac that are carefully designed to match the ... unlikely to welcome or be able to use JPG or TIFF. ...
    (microsoft.public.mac.office.word)
  • Re: 2004 Microsoft Word for Mac versus 11.03 Word for PC
    ... Microsoft provides fonts ... with Microsoft Office on the Mac that are carefully designed to match the ... unlikely to welcome or be able to use JPG or TIFF. ... Microsoft Word on the Mac matches that on the PC closely enough to enable ...
    (microsoft.public.mac.office.word)
  • Re: Word 2008 - does it do right-to-left text
    ... the same thing for Mac Office, they could expect to improve Office sales by ... "Take Windows Office 2007, remove the products that are too hard, remove the ... If Apple RTL support is now sufficiently complete that Microsoft can ...
    (microsoft.public.mac.office.word)