Hot answers tagged unicode
15
Another particularly well-done typeface is Nick Shinn's Scotch Modern and its sans-serif companion Figgins Sans. The serif comes in footnote, text, and display grade. It's a typeface rooted in the same period as Computer Modern (think Victorian-era UK, mid-1800s). [highly subjective and possibly controversial statement follows:] If Computer Modern were ...
10
Someone else will have to find a way to use 'TeX itself', which seems needlessly complicated, though admittedly not without interest. I prefer the philosophy of 'use the right tool for the job'. In this case, my advice is use pandoc, since this is what it was designed for: converting files from one markup to another. From exactly this input:
% ...
7
LaTeX2e introduced the notion of output font encoding and of “LaTeX Internal Character Representation” (LICR).
Depending on the current font encoding, escape codes, such as \'{e} for “é” or \k{a} for “ą” will either use a composed glyph or a “real” one.
The T1 font encoding contains glyphs for most European languages. It defines several combinations that ...
7
That is a bug in the font, the glyph for ɻ has an anchor point of type mark instead of base glyph, so the rendering engine treats it like a combining mark and places it over glyphs that have the same anchor but with base glyph type. This should be reported to the font developers.
The fact that LuaTeX does not place it above the preceding glyph is a bug in ...
6
The xcookybooky package makes wrong assumptions about fonts. But you're doing wrong too:
Don't use fontenc with XeLaTeX or LuaLaTeX (it can be used, but not in general cases)
Don't use the obsolete a4wide package. Use geometry if you want to modify the page parameters.
Don't load xltxtra and xunicode.
The fix is simple: use the default font and encoding ...
5
The following example introduces the switch \iflstcomment. It is enabled (\lstcommenttrue) in option commentstyle. Then the color for the numbers is only set, if \iflstcomment is not enabled. Macro \lstnumcolor hides the internals:
\documentclass[spanish, 11pt]{book}
\usepackage[utf8]{inputenc}
\usepackage[margin=2.5cm]{geometry}
...
5
Unicode points > 7 bit are encoded with several bytes in UTF-8. Package seqsplit does not know this, as it is written for long DNA/RNA/protein/… sequences. It is the wrong package for natural text. Languages have rules, where breakpoints are allowed in words (usually not after each letter) and they request the insertion of a hyphenation char.
Thus ...
5
The “LATIN LETTER SMALL ENG” U+0148 character “ŋ” is available only in T1 encoded fonts. Unfortunately not all fonts available in TeX distributions have it: don't try it with \usepackage{mathptmx}, for instance.
Add
\usepackage[T1]{fontenc}
to your preamble (and upgrade your TeX distribution to a full one).
You can also profit from direct Unicode input, ...
5
As to the “why” question, what is happening here is that under some circumstances the letter pair “ff” is replaced by “ff” LATIN SMALL LIGATURE FF U+FB00, which is understandable in a sense, but then things go wrong.
In cases 3 and 4, the character is presumably written correctly in the HTML document, but the font being used does not contain it, so the ...
4
For the down arrow the answer is \usepackage{textcomp}.
\documentclass[]{article}
\usepackage{amssymb,amsmath}
\usepackage{ifxetex,ifluatex}
\ifxetex
\usepackage{fontspec}
\defaultfontfeatures{Ligatures=TeX,Scale=MatchLowercase}
\else
\ifluatex
\usepackage{fontspec}
\defaultfontfeatures{Ligatures=TeX,Scale=MatchLowercase}
\else
...
4
Unhappily utf8.def does not show the numerical representation for the missing Unicode character. The missing character <char> is shown directly in macro \u8:<char>. The following example adds the numerical information in the error message:
\documentclass{article}
\usepackage[utf8]{inputenc}
\usepackage{stringenc}
\usepackage{pdfescape}
...
4
You mean Unicode characters rather than UTF-8 characters. Unicode code points are in the range hex 0-10FFFF and pdflatex fonts are restricted to hex 0-FF so you would need thousands of fonts to cover the full Unicode range and a TeX macro definition for each character (or range of characters that can be mapped as a block).
3
With the new greek-fontenc and updated greek-inputenc packages,
you are now able to use Greek Unicode characters in the LaTeX source
(and the utf8 "LaTeX encoding" option in LyX).
Together with \usepackage[pdfencoding=auto]{hyperref} his solves
the problem with PDF-strings.
Alternatively, Greek LICR macros (like \textalpha ... \textomega) can be used.
...
3
This is something like a hack. If a Unicode symbol definition has been loaded with encodings package such as textcomp or options to fontenc, with \UnicodeChar{abcd} you can access to it, or ? will be printed.
\documentclass[11pt,a4paper]{scrartcl}
\usepackage[english]{babel}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{eurosym}
...
2
Package pst-barcode needs a plain text string. UTF-8 is supported in 8-bit-TeX by active characters that contain code. The code can be anything, for example it chooses the character from the right position of the font that contains it.
That additional stuff that is needed, if the string is typeset by TeX disturbs
pst-barcode that only translates plain text ...
1
I don't have miktex, so don't know what means that error message about path, but for utf-8 output, you must run htlatex with:
htlatex mwe "xhtml, charset=utf-8" " -cunihtf -utf8"
result:
chars with àccéènts greek chars ασδφγη
1
For example (last item without changes)
\documentclass{article}
\usepackage{latexsym}
\begin{document}
\def\Item{\item[$\Box$]}
\begin{itemize}
\Item
A
\Item
B
\item
C
\end{itemize}
\end{document}
Only top voted, non community-wiki answers of a minimum length are eligible
