Re: unicode failure with inputenc package
- From: rf10@xxxxxxxxxxxx (Robin Fairbairns)
- Date: 3 Jun 2008 20:17:31 GMT
r <inpost@xxxxxxxxx> writes:
Upon further thought, with the instruction to use utf8 and the
inputenc package, why does latex accept my tex files being created in
utf8 text encoded text editor, yet fail to accept a utf8 character
within those very same utf8 encoded text files?
because.
the utf8 code in inputenc is extremely tricky, and it relies on each
character having a separate definition.
because this is a space hog, it doesn't even try to set up characters
it doesn't believe you can typeset (you tell it what you can typeset
via your fontenc declarations).
all of this is a mess, which derives from tex only being able to deal
with fonts with at most 256 glyphs in them.
otoh, xetex, which people have suggested you use, uses opentype fonts
which can, in principle, contain a glyph for every registered unicode
code point. you don't need a macro to access that -- just the unicode
character.
--
Robin Fairbairns, Cambridge
.
- Follow-Ups:
- Re: unicode failure with inputenc package
- From: Frank Mittelbach
- Re: unicode failure with inputenc package
- References:
- unicode failure with inputenc package
- From: r
- Re: unicode failure with inputenc package
- From: Joseph Wright
- Re: unicode failure with inputenc package
- From: r
- Re: unicode failure with inputenc package
- From: Robin Fairbairns
- Re: unicode failure with inputenc package
- From: r
- Re: unicode failure with inputenc package
- From: Joseph Wright
- Re: unicode failure with inputenc package
- From: r
- unicode failure with inputenc package
- Prev by Date: Re: unicode failure with inputenc package
- Next by Date: Re: comparing savebox contents
- Previous by thread: Re: unicode failure with inputenc package
- Next by thread: Re: unicode failure with inputenc package
- Index(es):
Relevant Pages
|