On Fri, Oct 18, 2019 at 10:03 AM Terry Brown wrote:
"Vanilla" LaTeX systems tend to use `pdflatex` to process things, and don't
> understand unicode inputs without extra fiddling. If you use XeTeX
> (`xelatex`), it assumes unicode by default and makes things simpler - in a
> lot of cases it can
"Vanilla" LaTeX systems tend to use `pdflatex` to process things, and don't
understand unicode inputs without extra fiddling. If you use XeTeX
(`xelatex`), it assumes unicode by default and makes things simpler - in a
lot of cases it can be a drop in replacement. I think TeXLive supports
either,
On Fri, Oct 18, 2019 at 7:50 AM Rob wrote:
> I re-read the error message in the LaTeX processor and perhaps I should
> clarify.
>
> Keyboard character used is undefined in inputencoding`utf8'.
>
> Reviewing the documentation for that package (inputenc) suggests the error
> is because there is no
I re-read the error message in the LaTeX processor and perhaps I should
clarify.
Keyboard character used is undefined in inputencoding`utf8'.
Reviewing the documentation for that package (inputenc) suggests the error
is because there is no corresponding glyph to map to output. So, it's
On Thu, Oct 17, 2019 at 9:21 PM Rob wrote:
My LaTeX processor choked on 2 instances of an unknown UTF8 character.
> Probably came into Leo when I copied from somewhere else (perhaps an MS
> Word document).
>
I'm not sure there is such a thing as an "unknown" UTF8 character.
Leo is quite
My LaTeX processor choked on 2 instances of an unknown UTF8 character.
Probably came into Leo when I copied from somewhere else (perhaps an MS
Word document). Anyway, there was no visual clue in Leo where the offending
characters were. By process of elimination I found the offending node and
