Comments on: Fonts in LaTeX, Part One: XeLaTeX http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/ For People Who Like Type and Types Sun, 24 Jan 2010 22:31:27 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Using Unicode Character in LyX or LaTeX: XeTeX | 小石头工作室 . Stone Studio . http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/comment-page-1/#comment-44553 Using Unicode Character in LyX or LaTeX: XeTeX | 小石头工作室 . Stone Studio . Sun, 24 Jan 2010 22:31:27 +0000 http://existentialtype.net/?p=251#comment-44553 [...] http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/ [...] [...] http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/ [...]

]]> By: Swift Arrow http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/comment-page-1/#comment-31282 Swift Arrow Fri, 17 Apr 2009 14:46:06 +0000 http://existentialtype.net/?p=251#comment-31282 @John, I find Scribus to be very good. Just converted my student's association to it from publisher. And it's quite like indesign. @John,
I find Scribus to be very good. Just converted my student’s association to it from publisher. And it’s quite like indesign.

]]> By: Swift Arrow http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/comment-page-1/#comment-31281 Swift Arrow Fri, 17 Apr 2009 14:43:45 +0000 http://existentialtype.net/?p=251#comment-31281 Where's part two of this article? Where’s part two of this article?

]]> By: washburn http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/comment-page-1/#comment-30787 washburn Wed, 08 Apr 2009 09:04:44 +0000 http://existentialtype.net/?p=251#comment-30787 @John: I think part of the issue with Gnome Character Map is that the underlying font engine it uses tries to be smart about substituting glyphs from other fonts if the font you have requested does not include the glyph. I expect your problems could be resolved, but I don't really have enough information to go on. In any event, TeX's strength is typesetting mathematics and its macro capabilities. Given that you are interested in typesetting linguistics, InDesign may indeed be the better choice for your needs. @John: I think part of the issue with Gnome Character Map is that the underlying font engine it uses tries to be smart about substituting glyphs from other fonts if the font you have requested does not include the glyph.

I expect your problems could be resolved, but I don’t really have enough information to go on. In any event, TeX’s strength is typesetting mathematics and its macro capabilities. Given that you are interested in typesetting linguistics, InDesign may indeed be the better choice for your needs.

]]> By: John Jason Jordan http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/comment-page-1/#comment-30719 John Jason Jordan Tue, 07 Apr 2009 00:52:19 +0000 http://existentialtype.net/?p=251#comment-30719 I should have added that I did figure out how to enter IPA directly in LyX. And I also figured out about UTF-8. However, it is still messing up on the double breve (0x0361). This glyph is available in Junicode only in the regular font. However, what I am getting from LyX/XeTeX is a single short mark that covers just one letter, and it appears for all the fonts, not just regular. Somewhere a glyph from a different font is being substituted. But I am not going to pursue it further. TeX/LaTeX/LyX/XeTeX are not good solutions for my work. I need much more design freedom. InDesign works much better for me, although I dislike intensely the corporate bs. I need to see what it looks like as I work. Thanks again for the response. I should have added that I did figure out how to enter IPA directly in LyX. And I also figured out about UTF-8. However, it is still messing up on the double breve (0×0361). This glyph is available in Junicode only in the regular font. However, what I am getting from LyX/XeTeX is a single short mark that covers just one letter, and it appears for all the fonts, not just regular. Somewhere a glyph from a different font is being substituted.

But I am not going to pursue it further. TeX/LaTeX/LyX/XeTeX are not good solutions for my work. I need much more design freedom. InDesign works much better for me, although I dislike intensely the corporate bs. I need to see what it looks like as I work.

Thanks again for the response.

]]> By: John Jason Jordan http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/comment-page-1/#comment-30717 John Jason Jordan Tue, 07 Apr 2009 00:40:09 +0000 http://existentialtype.net/?p=251#comment-30717 Thanks for the response. Since my first post above I have made progress. That is, I have discovered the main source of the problem. I have been using the Junicode face (on Sourceforge) for years for linguistics work. I guess in all that time I never used anything but the regular font. I was trying to set the title of a book in Lyx, and I wanted it bold. There were IPA characters in the title and they were dropping out. Today it dawned on me to verify that the glyphs actually existed in the fonts. I opened each of the four fonts in Fontforge and, guess what? Most of the IPA and combining diacriticals glyphs were missing in the bold and bold-italic fonts. All this time I was relying on Gnome Character Map. It shows the characters as present in all the fonts. But what Character Map is actually doing is taking the regular version of the font (since all you can select is the family name). When the user clicks on the italic button it slants it, and when the user clicks on the bold button it makes it fatter. After discovering the truth with Fontforge I observed that the a in the regular-italic and bold-italic was really just a slanted regular a, not the script a that it is really supposed to be. So Gnome Character Map is a shameless liar. Thanks for the response. Since my first post above I have made progress. That is, I have discovered the main source of the problem.

I have been using the Junicode face (on Sourceforge) for years for linguistics work. I guess in all that time I never used anything but the regular font. I was trying to set the title of a book in Lyx, and I wanted it bold. There were IPA characters in the title and they were dropping out.

Today it dawned on me to verify that the glyphs actually existed in the fonts. I opened each of the four fonts in Fontforge and, guess what? Most of the IPA and combining diacriticals glyphs were missing in the bold and bold-italic fonts.

All this time I was relying on Gnome Character Map. It shows the characters as present in all the fonts. But what Character Map is actually doing is taking the regular version of the font (since all you can select is the family name). When the user clicks on the italic button it slants it, and when the user clicks on the bold button it makes it fatter. After discovering the truth with Fontforge I observed that the a in the regular-italic and bold-italic was really just a slanted regular a, not the script a that it is really supposed to be.

So Gnome Character Map is a shameless liar.

]]> By: washburn http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/comment-page-1/#comment-30705 washburn Mon, 06 Apr 2009 19:32:12 +0000 http://existentialtype.net/?p=251#comment-30705 @John: I've never really used Lyx, so I am not sure how much useful advice I can provide. I would first check whether it is indeed saving files in UTF8 format, as by default XeTeX expects that the input uses a UTF8 encoding of the text. Based upon my interpretation of http://wiki.lyx.org/Mac/XeTeX, Lyx does not save in UTF8 by default, so I am going to guess that is the most probable cause. If that isn't the problem, I would recommend opening your document in another Unicode aware editor or viewer (I can't really suggest one without knowing what platform you are using) and check whether IPA symbols in the document look correct. Then I would try running XeTeX manually and see what happens. @John: I’ve never really used Lyx, so I am not sure how much useful advice I can provide. I would first check whether it is indeed saving files in UTF8 format, as by default XeTeX expects that the input uses a UTF8 encoding of the text. Based upon my interpretation of http://wiki.lyx.org/Mac/XeTeX, Lyx does not save in UTF8 by default, so I am going to guess that is the most probable cause.

If that isn’t the problem, I would recommend opening your document in another Unicode aware editor or viewer (I can’t really suggest one without knowing what platform you are using) and check whether IPA symbols in the document look correct. Then I would try running XeTeX manually and see what happens.

]]> By: John Jason Jordan http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/comment-page-1/#comment-30681 John Jason Jordan Mon, 06 Apr 2009 05:39:25 +0000 http://existentialtype.net/?p=251#comment-30681 Thanks a lot for this how-to. I finally got Lyx using my Junicode font. However, there is problem. The main reason I need my Junicode font is for linguistics work, that is, I need all 150 or so of the IPA characters that the Junicode font has. The problem is that all text comes out in Junicode *except* the IPA characters. For some reason it is using some weird font. And the weird font is not taking attributes like bold or italic. I think I need a way to enter the IPA characters by Unicode code point instead of from the Insert > Special Character menu. Thanks a lot for this how-to. I finally got Lyx using my Junicode font. However, there is problem. The main reason I need my Junicode font is for linguistics work, that is, I need all 150 or so of the IPA characters that the Junicode font has. The problem is that all text comes out in Junicode *except* the IPA characters. For some reason it is using some weird font. And the weird font is not taking attributes like bold or italic.

I think I need a way to enter the IPA characters by Unicode code point instead of from the Insert > Special Character menu.

]]> By: washburn http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/comment-page-1/#comment-29494 washburn Mon, 09 Mar 2009 12:24:07 +0000 http://existentialtype.net/?p=251#comment-29494 @plgx: No, the problem seems to be that if I write <pre>abcd ... </pre> the first character gets eaten. If I just put in a newline <pre> abcd ... </pre> It seems okay. @plgx: No, the problem seems to be that if I write

<pre>abcd
…
</pre>

the first character gets eaten. If I just put in a newline

<pre>
abcd
…
</pre>

It seems okay.

]]> By: plgx http://existentialtype.net/2008/07/12/fonts-in-latex-part-one-xelatex/comment-page-1/#comment-29321 plgx Thu, 05 Mar 2009 19:26:38 +0000 http://existentialtype.net/?p=251#comment-29321 Maybe \\ Maybe \\

]]>