# Tag Info

5

The problem is in luatex (possibly in luaotfload); if I ask the font corresponding to \liningmain from your code, I get "[EBGaramond12-Regular.otf]/ICU:script=latn;language=DFLT;+liga;mapping=tex-text;+lnum;+tnum;" with XeLaTeX and "[EBGaramond12-Regular.otf]:mode=node;script=latn;language=DFLT;+liga;+tlig;+trep;+lnum;+tnum;" with LuaLaTeX. So I ...

4

“EB Garamond” is an OpenType font, but “URW Garamond” available for TeX Live with the getnonfreefonts script (executable in Windows) is in Type1 format. With fontspec you can only use a True-/OpenType vresions of this font. You can download the whole URW fonts collection in Truetype format from your favorite source, cf. ...

11

For OpenType fonts, you simply take the name you use when loading the font, in your case Adobe Garamond Pro. You could then use the file mt-pad.cfg as your template, by copying it to mt-AdobeGaramondPro.cfg (note, no spaces), and changing/adding the protrusion values: \SetProtrusion [ name = AdobeGaramondPro ] { encoding = {EU1,EU2}, % EU1 = ...

5

First of all, note that you have some strange accented characters in your .bib file. For example é is the combination of a normal e (U+0065) plus a "Combining acute accent" character (U+0301), instead of the normal accented e é (U+00E9). Having said that, notice that the compilation returns first an "Overfull \hbox" warning caused by the word ...

4

The latest revision of xunicode-addon try to fix this bug (avaliable in ctex-kit or Google Driver currently). Please have a try. Update: The new version is available in TeX Live 2013.

1

You can also do the following: Go into Command mode in vim by hitting ESC, so what you enter appears in a special command-line at the bottom of the screen. Search: Enter / directly followed by what you want to search for and hit enter to search in forward direction. To search in backwards direction, use ? instead of /. To repeat the search in forward ...

1

Sometimes you might want to use an actual no-break space. So turning them into normal spaces altogether might not be the best idea. In that case Adityas solution is a good start. But I don’t like my indentation displayed as ^I. The following colours the no-break spaces in gvim: hi NoBreakSpace guibg=LightGoldenrod1 guifg=black syn match NoBreakSpace / / ...

0

I just want to add some words to Nils L's answer: I personally use NexusFont on windows 7, which can display the whole table of characters by categories (Latin1 Supplement, Cyrillic, Basic Greek, &c.) and offers a zoom on individual characters. That makes it easier to find what you want. Below is a screenshot of NexusFont in action:

0

Xetex Even though the question is about LuaLatex, here another XeTeX solution Based on this post: Generating a table of glyphs with XeTeX and some other research. It prints you all glyphs and you can access them with \XeTeXglyph \documentclass[landscape]{article} \usepackage{geometry} \usepackage{xltxtra} \usepackage{fontspec} \usepackage{xunicode} ...

1

LuaLaTeX can add virtual features to Open Type fonts. Since only glyphs are exchanged (not characters), find and copy should still work as expected in PDF viewers. I didn‘t test that, though. % !TEX TS-program = LuaLaTeX \begin{filecontents}{test.fea} languagesystem DFLT dflt; languagesystem latn dflt; feature test { sub g by uni0434.ital; } test; ...

2

Works for xelatex and pdflatex \documentclass{article} \usepackage{iftex} \ifXeTeX \usepackage[no-math]{fontspec} \usepackage[libertine]{newtxmath} \else \usepackage[T1]{fontenc} \usepackage[utf8]{inputenc} \fi \usepackage{libertine} \begin{document} $\mathbf{\Delta}$ \end{document}

0

It's important not to confuse math fonts and text fonts. Loading fontspec with the [no-math] option keeps the math font untouched, so math font packages should work as usual. Font packages written for PDFLaTeX may not work. However, before switching an existing document to XeLaTeX, proofreading is necessary. I found that there are some special cases that do ...

12

With XeTeX you can get glyph by name, but I don't think it's possible to map the name to the Unicode point, which wouldn't make sense anyway, because a code point can correspond to several glyphs. Here's how: if you know the name, say zero.slash, you can print the glyph with \XeTeXglyph\XeTeXglyphindex"zero.slash"<space> I got the list of glyph ...

Top 50 recent answers are included