Le 23 oct. 2010 à 11:27, Peter Dyballa a écrit : > > Am 23.10.2010 um 10:53 schrieb André Bellaïche: > >> 1. Is it possible to replace unicode by applemac encoding? What are the >> commands in this case? > > If you want to continue typing in applemac input encoding you better stay > with the much more developed pdfTeX. All packages work with pdfTeX, and > additionally you gain micro-typography. And: you can also continue to use > PostScript fonts.
I can convert my files to utf-8 using TextEdit or iconv. I only wanted to know. > >> >> 2. If the main roman font is Frutiger® 55 Roman (Linotype Original names), I >> doubt that the system will find out that if the italic, bold and bold italic >> counterparts are Frutiger® 56 Italic, Frutiger® 65 Bold, Frutiger® 66 Bold >> Italic. >> >> The same font is sold by Adobe under the name Frutiger Std™ Roman, and Adobe >> says that other names of the font are: >> >> Postscript File Name: FrutigerLTStd-Roman >> MAC Menu Name: Frutiger LT Std 55 Roman >> Windows/PC Menu Name: Frutiger LT Std 55 Roman > > The PostScript or Family name is the one by which XeTeX knows a font. Yes, but it does not seem that the Postscript name is the one you type in the command \setromanfont. > > Beware of PostScript fonts! They don't come with the data that XeTeX or > LuaTeX need for typesetting. (OpenType and TrueType fonts are recommended.) A > PostScript font is for XeTeX or LuaTeX as useful as a French car without gas > for its owner or user. Thanks. I didn't know. As all these fonts are available in either format, I'll buy the OpenType one. > > -- > Greetings > > Pete === -Q > ==<__/% >> > _____________(_)_...@_____________________________ > > > > > -------------------------------------------------- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex -------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
