[XeTeX] adding some diacritics to a font

Wilfred van Rooijen wvanrooijen at yahoo.com
Wed Jan 7 00:50:19 CET 2009


But isn't the essential trick of xe(la)tex that you *don't need* any font weirdness as long as you have a font available with the correct glyphs. So I'd humbly suggest to (re-)evaluate the font you've chosen. Is it really necessary to use Garamond, or can you find a suitable alternative that does have the correct glyphs available?

Another option could be to switch the font temporarily to another OTF font for words with diacritics. It would depend on the situation. It would be very weird to have one sentence in a different font in a paragraph for instance. 

If you find a good solution, please let us know.

Cheers,
Wilfred 




--- On Tue, 1/6/09, Peter Dyballa <Peter_Dyballa at Web.DE> wrote:

> From: Peter Dyballa <Peter_Dyballa at Web.DE>
> Subject: Re: [XeTeX] adding some diacritics to a font
> To: "Unicode-based TeX for Mac OS X and other platforms" <xetex at tug.org>
> Date: Tuesday, January 6, 2009, 6:20 PM
> Am 06.01.2009 um 23:14 schrieb François Patte:
> 
> > I want to use Garamong Pro otf fonts in a document
> where I need some
> > diacritics which are not included in this font:
> under/over-dot  
> > chars (ṇ
> > ṅ ḷ )
> >
> > If I put:
> >
> > \setmainfont[Mapping=tex-text]{Garamond Premier
> Pro}
> >
> > These glyphs do not appear. If I add:
> >
> > \usepackage[garamond]{mathdesign}
> 
> Mathdesign is a very complex package that uses it's own
> font  
> encodings. And T1 + TS1 for text!
> 
> >
> > I can get these glyphs through ordinary latex command
> (\d n), but the
> > whole document uses these mathdesign fonts....
> 
> The latter is no command, it's used in a declarative
> style. \d{n} is  
> a command. Or \.{n}.
> 
> 
> In short: I'd use for maths mathdesign and for text
> I'd use a regular  
> fontspec font. And this font can be your Garamond Premier
> Pro! And in  
> case you don't see any character with a dot below:
> remove  
> xunicode.sty from the packages you use! Xunicode.sty
> translates  
> typical LaTeX constructs like \d{n} to their real
> Unicode value. And  
> if the font does not have a glyph at this position, then
> you'll see  
> an OPEN BOX character, I think. Without xunicode.sty
> XeLaTeX will  
> work like LaTeX and construct the final character from two
> (or more),  
> and this construct will be unsearchable. And without
> xunicode.sty  
> other things will fail, presumingly ... So it would be nice
> if one  
> could switch off xunicode.sty for certain constructs!
> 
> --
> Greetings
> 
>    Pete
> 
> There is no national science just as there is no national  
> multiplication table; what is national is no longer
> science.
> 				– Anton Checov
> 
> 
> 
> _______________________________________________
> XeTeX mailing list
> postmaster at tug.org
> http://tug.org/mailman/listinfo/xetex


      


More information about the XeTeX mailing list