# Tag Info

6

Well, Private Use Areas are part of Unicode, they just have no predefined meaning. So you can use them like any other character, e.g. by simply typing it (if you have an appropriate input method) or using the character code either as \char"F3A0F or ^^^^^f3a0f. If I run your example here, I get a PDF with the symbol both with LuaTeX and XeTeX.

4

You can abuse the infrastructure of ucs; here's a set of tricks that read the files you need in the ucs distribution, but under utf8 which is compatible with biblatex. \documentclass[]{article} \usepackage[T1]{fontenc} \usepackage[utf8]{inputenc} \input{binhex} \makeatletter \def\uc@dclc#1#2#3{% \ifnum\pdfstrcmp{#2}{mathletters}=\z@ ...

4

As you input the file you could try to simply declare the BOM: \documentclass[]{book} \usepackage[utf8]{inputenc} \DeclareUnicodeCharacter{FEFF}{} \begin{document} \input{test-with-bom} \end{document}

3

It is a known bug of CJKutf8 package. I reported the issue to Werner Lemberg months ago and the problem has been fixed: Git commit of LaTeX-CJK. You can download the develop version of CJKutf8.sty from the git host before the new release of CJK bundle. Or you can use this patch code after \usepackage{CJKutf8}: \makeatletter \endlinechar\m@ne ...

3

It's - 9 as 99 as ” - 6 as 66 as “ Well, the font here isn't quite showing it, on wikipedia, better ones can be found:

3

The problem is due to how amsart uppercases the title. You solve it by adding \usepackage{textcase} that will use the safer \MakeTextUppercase command. \documentclass[a4paper]{amsart} \usepackage[utf8]{inputenc} \usepackage[english,greek]{babel} \usepackage{textcase} \begin{document} \title{τυχαιος τιτλος} \maketitle \end{document} It won't work with ...

2

You may get this error also if you use different language for bibtex. In that case project.bbl may contain characters in different encoding (e.g latin2). What you need to do is swap encoding when rendering bibliography to latin2 and switch back to utf8 after. \inputencoding{latin2} \bibliography{mybib} \inputencoding{utf8} Hope this helps.

1

The main issue is whether the font used for typesetting has the needed characters in it. The example below works on a linux system. Using Microsoft's truetype fonts also works using \setmonofont{Courier New}, instead. \documentclass{article} \usepackage{fontspec} \setmonofont{FreeMono} \begin{document} \begin{verbatim} . ├── Maildir/ └── scripts/ ...

1

This is not an answer, but a comment can't contain an MWE and pictures It would be helpful if you did some more work in diagnosing where the problem occurs. Simplifying your example and compiling the code with XeLaTeX gives no issues for me. \documentclass{article} \usepackage{fontspec} \setmainfont{CMU Serif} \begin{document} \section{Свои проекты и ...

Only top voted, non community-wiki answers of a minimum length are eligible