Take the 2-minute tour ×
TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.

I have bought OTF Adobe Garamond Pro and successfully converted it to use with LaTeX (using otfinst.py). It works well including ligatures, old-style numerals, small caps, etc., but the problem is again with Latin characters, specifically ď, ľ and ť (\v{d}, \v{l}, \v{t}). Normally, the caron changes its shape so it looks like a comma rather than a wedge, but in this case, it is not working.

I have spent a considerable amount of time by researching the possibilities, yet came to no acceptable conclusion.

Could you please suggest how to fine-tune it while preserving proper kerning?

Improper placement of carons.

Fig. 1: The problematic characters.


Edit (20. July 2011):

Thanks to Ulrike's answer, I have realised that I forgot to change the encoding and the encoding file. After editing the script and another run, it works perfectly and I can finally typeset my documents using Garamond typeface. I shall accept the answer as it led me to the solution.

Proper placement of carons.

Fig. 2: Victory! :-)

share|improve this question
    
Note that XeTeX and LuaTeX can use OTF fonts natively. Note also that EB Garamond is an excellent open-source Garamond font :-) –  ℝaphink Jul 21 '11 at 9:36
    
I think that caron over t is misplaced, it should be placed lower. also, it is very similar to apostrophe, better is to have distinct shape, like in EB Garamond. –  michal.h21 Jul 21 '11 at 10:37
    
@michal.h21 As far as I know, the original typeface did not include the letter ť, so there should not be an exact example to follow. This is how Adobe decided to make it and I think that it is very reasonable as the proportions and placement are the same as in case of ď and ľ. –  Harold Cavendish Jul 21 '11 at 10:46
    
@Raphink Thank you for the suggestions, I am aware of the potential of XeTeX and LuaTeX, but I have to use LaTeX for various reasons. EB Garamond appears to be still in development, hence its usage could cause problems later. –  Harold Cavendish Jul 21 '11 at 10:49
1  
@Harrold: XeTeX and LuaTeX are LaTeX (see xelatex and lualatex). They're "just" alternative LaTeX compilers to PDFTeX, but the language is strictly the same and 99% of the CTAN packages will work just the same. In EB Garamond, it's mostly the Italic that's currently in development (and almost finished, I'm using it in a book) and the bold face is not done yet. The rest is ready (including small caps) and of really good quality. –  ℝaphink Jul 21 '11 at 11:07
show 4 more comments

1 Answer

up vote 5 down vote accepted

Well in T1-encoding \v{d} etc are real chars. So if you don't get them either your font doesn't have the glyphs or something did go wrong with the reencoding.

\documentclass{article}
\usepackage[T1]{fontenc}
%switch here to your font:

\begin{document}

\v{d}, \v{l}, \v{t}

\char164, \char169, \char180
\end{document}
share|improve this answer
    
I have just realised that I did not change the LY1 encoding... D'oh! :-) I am going to convert it again, the original font does have the glyphs. –  Harold Cavendish Jul 20 '11 at 18:24
    
Thank you very much indeed! –  Harold Cavendish Jul 20 '11 at 20:34
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.