I have a similar problem:<br><br>I've come to appreciate the use of small caps fonts in the documents I type. Furthermore, some of the documents I create are in Turkish. Even though it is rather easy to find open type fonts with Turkish support, I've come to realize that the support does not necessarily cover the small caps glyphs. More specifically, the capital I with dot above ( İ ), character most often does not exist in the small caps version---though there are exceptions. Not having access to that glyph pretty much renders small caps usage unavailable in Turkish and that bothers me.<br>
<br>Anyhow, I was thinking of creating the required glyph as a combination of two glyphs (the small caps I and the over dot) and putting that information in the open type font through the <i>Font Forge</i> software. Perhaps there is an easier way of essentially doing the same thing using XeTeX, though I don't know how. I would not want to mark the characters as something like \smallcapsdot{I}, but rather, directly type them in unicode, so that---for instance---whenever \textsc{İ} is invoked, the correct glyph is displayed. <br>
<br>I will look into the xunicode.sty file as suggested below. Do you have any other reccomendations?<br><br>Ekin<br><br>
<br><br><br><div class="gmail_quote">On Tue, Jan 6, 2009 at 3:50 PM, Wilfred van Rooijen <span dir="ltr"><<a href="mailto:wvanrooijen@yahoo.com" target="_blank">wvanrooijen@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
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?<br>
<br>
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.<br>
<br>
If you find a good solution, please let us know.<br>
<br>
Cheers,<br>
Wilfred<br>
<br>
<br>
<br>
<br>
--- On Tue, 1/6/09, Peter Dyballa <Peter_Dyballa@Web.DE> wrote:<br>
<br>
> From: Peter Dyballa <Peter_Dyballa@Web.DE><br>
> Subject: Re: [XeTeX] adding some diacritics to a font<br>
> To: "Unicode-based TeX for Mac OS X and other platforms" <<a href="mailto:xetex@tug.org" target="_blank">xetex@tug.org</a>><br>
> Date: Tuesday, January 6, 2009, 6:20 PM<br>
<div><div></div><div>> Am 06.01.2009 um 23:14 schrieb François Patte:<br>
><br>
> > I want to use Garamong Pro otf fonts in a document<br>
> where I need some<br>
> > diacritics which are not included in this font:<br>
> under/over-dot<br>
> > chars (ṇ<br>
> > ṅ ḷ )<br>
> ><br>
> > If I put:<br>
> ><br>
> > \setmainfont[Mapping=tex-text]{Garamond Premier<br>
> Pro}<br>
> ><br>
> > These glyphs do not appear. If I add:<br>
> ><br>
> > \usepackage[garamond]{mathdesign}<br>
><br>
> Mathdesign is a very complex package that uses it's own<br>
> font<br>
> encodings. And T1 + TS1 for text!<br>
><br>
> ><br>
> > I can get these glyphs through ordinary latex command<br>
> (\d n), but the<br>
> > whole document uses these mathdesign fonts....<br>
><br>
> The latter is no command, it's used in a declarative<br>
> style. \d{n} is<br>
> a command. Or \.{n}.<br>
><br>
><br>
> In short: I'd use for maths mathdesign and for text<br>
> I'd use a regular<br>
> fontspec font. And this font can be your Garamond Premier<br>
> Pro! And in<br>
> case you don't see any character with a dot below:<br>
> remove<br>
> xunicode.sty from the packages you use! Xunicode.sty<br>
> translates<br>
> typical LaTeX constructs like \d{n} to their real<br>
> Unicode value. And<br>
> if the font does not have a glyph at this position, then<br>
> you'll see<br>
> an OPEN BOX character, I think. Without xunicode.sty<br>
> XeLaTeX will<br>
> work like LaTeX and construct the final character from two<br>
> (or more),<br>
> and this construct will be unsearchable. And without<br>
> xunicode.sty<br>
> other things will fail, presumingly ... So it would be nice<br>
> if one<br>
> could switch off xunicode.sty for certain constructs!<br>
><br>
> --<br>
> Greetings<br>
><br>
> Pete<br>
><br>
> There is no national science just as there is no national<br>
> multiplication table; what is national is no longer<br>
> science.<br>
> – Anton Checov<br>
><br>
><br>
><br>
> _______________________________________________<br>
> XeTeX mailing list<br>
> <a href="mailto:postmaster@tug.org" target="_blank">postmaster@tug.org</a><br>
> <a href="http://tug.org/mailman/listinfo/xetex" target="_blank">http://tug.org/mailman/listinfo/xetex</a><br>
<br>
<br>
<br>
_______________________________________________<br>
XeTeX mailing list<br>
<a href="mailto:postmaster@tug.org" target="_blank">postmaster@tug.org</a><br>
<a href="http://tug.org/mailman/listinfo/xetex" target="_blank">http://tug.org/mailman/listinfo/xetex</a><br>
</div></div></blockquote></div><br>