# Tag Info

0

I will give what I learned by trial and error. This is pertaining to Windows platform. ( I used the material given found here at the XeLaTeX wiki.) The trick is to use the fonts available in the system's font directory. (Windows7 provides Latha font for Tamil) and compile your source file with xelatex, not pdflatex! (For this in Windows platform, ...

4

Like Harish I would suggest to use utf8 instead of ucs/utf8x, but if for some reason you really need utf8x you must prerender the offending unicode character: \documentclass[a4paper]{report} \usepackage[T1]{fontenc} \usepackage[utf8x]{inputenc} \PrerenderUnicode{ø} \begin{document} \tableofcontents \chapter{ø} \end{document}

1

Use \usepackage[utf8]{inputenc} instead of utf8x \documentclass[a4paper]{report} \usepackage[utf8]{inputenc} \begin{document} \tableofcontents \chapter{ø} \end{document}

3

xunicode sets up for these commands also some OT1 defaults, but the main point are accents commands. E.g. \DeclareEncodedCompositeCharacter{\UTFencname}{\M}{0322}{0322} % (Combining retroflex hook below) You can naturally redefine the command if you don't use it, but there is a tradition to use "one-char-commands" for accent commands and so I would never ...

3

Unicode's advantages As I see it, there are many advantages to using a Unicode font with XeLaTeX/LuaLaTeX, some of which are mentioned in answers to the above questions and in other places, notably Alan Munn's answers to How to use phonetic IPA characters in LaTeX and Preparing a text for conversion to LaTeX: How to convert "ejective stops" in ...

3

Yes, LaTeX will parse the left and right quotation marks correctly if you tell it to parse the input with UTF-8 encoding. \documentclass{article} \usepackage[utf8]{inputenc} \begin{document} ‘Hello’ \end{document}

0

There are a few packages now available: coloremoji.sty Twitter Emoji For Everyone DoraTeX coloremoji

1

If this is what you expect to see in your LaTeX / XeTeX output … then you may just have to change the name of the font, which may be outdated in the example you got. I modified your example like this (with comments removed): \documentclass{article} \usepackage{fontspec} \setmainfont[Script=Devanagari]{Lohit-Devanagari} % Hindi -> Devanagari ...

5

In the past a use case for ucs was when Greek input was needed; since TeX Live 2013 the situation has changed and full support for Greek input (monotonic and polytonic) is available with \usepackage[utf8]{inputenc} provided the greek or polutonikogreek is passed to babel. Note that the package ucs and the utf8x options to inputenc are not compatible with ...

1

I gave an answer above yesterday. Through a new research of Polyglossia Package, I find out a new solution to Tibetan line-breaks. In fact, Polyglossia is supporting Tibetan now and I was totally misled by Tom who commented on this question. This is my example. \documentclass{article} \usepackage{fontspec} \usepackage{polyglossia} \usepackage{eledmac} ...

4

add \XeTeXlinebreaklocale "bo" after \begin{document} \documentclass{article} \usepackage{fontspec} \setmainfont{Microsoft Himalaya} \usepackage{microtype} \begin{document} \XeTeXlinebreaklocale "bo" །།འདིར་སྨྲས་པ། \begin{quotation} གལ་ཏེ་འདི་དག་ཀུན་སྟོང་ན། །འབྱུང་བ་མེད་ཅིང་འཇིག་པ་མེད།།གང་ཞིག་སྤང་དང་འགོག་པ་ལས། །མྱ་ངན་འདའ་བར་འགྱུར་བར་འདོད། \end{quotation} ...

2

The reason why the behavior differs when LuaTeX or XeTeX is used, is explained here. The XeTeX uses xdvipdfmx and this converter sets the UTF8 to UCS2 conversion automatically. On the other hand, when we are using direct pdfTeX primitives (like in LuaTeX) then the UTF8 to UCS2 conversion must be done at macro level. And the hyperref package does this when ...

0

I think I got it: just use a \endofdump to indicate the end of the precompiled format slightly before \begin{document}; and then insert the \AtBeginDvi{\input{zhwinfonts}} line after it. The preamble thus becomes: \RequirePackage{filecontents} % %% NOTE: filecontents cannot be active when -ini runs; must be commented! % %% NOTE: cannot use just {{文章}}, ...

6

It's probably better to use ^^^^043a which produces a character token, rather than use \char"043A which is a non expandable primitive accessing a font position. The character token is usable in more contexts (such as writing to tables of contents) and generally has less restrictions than \char. the ^^^^ notation (and \char"043A) will work in luatex or ...

Top 50 recent answers are included