Somehow the converter has to recognize the input encoding of the LaTeX
file. Up to now it does this by checking the
\usepackage[...]{inputenc}
command.
AFAIK there is no
\usepackage[utf8]{inputenc}
option (correct me if I'm wrong), so
-> we need to know which packages YOU use to support UTF-8 input.
Please reply here (in the newsgroup) or to wh_ng(at)gmx(dot)de.
Regards, Wilfried
\usepackage[utf8x]{inputenc}
Greetz
Adrian
>> -> we need to know which packages YOU use to support UTF-8 input.
>>
>> Please reply here (in the newsgroup) or to wh_ng(at)gmx(dot)de.
>>
>> Regards, Wilfried
>
> \usepackage[utf8x]{inputenc}
>
> Greetz
> Adrian
I prefer:
\usepackage{ucs}
\usepackage[utf8,utf8x]{inputenc}
for Win 2k, XP and MikTex 2.5 and greater. [utf8,utf8x] for file
changing in Linux (K)Ubuntu and the Win-World.
Greetings
Jörn
> Adrian Nievergelt schrieb:
> > Wilfried Hennings wrote:
> >>
> >> -> we need to know which packages YOU use to support UTF-8 input.
> >
> > \usepackage[utf8x]{inputenc}
> >
>
> I prefer:
> \usepackage{ucs}
> \usepackage[utf8,utf8x]{inputenc}
>
> for Win 2k, XP and MikTex 2.5 and greater. [utf8,utf8x] for file
> changing in Linux (K)Ubuntu and the Win-World.
Thank you, with these packages nearly all characters which are defined
in the standard MS Windows fonts are also output by LaTeX.
If you are interested in my test file, you can get it from
(The test file doesn't yet include Hebrew and Arab letters because Word
behaves strange as soon as I start entering these letters, and I hadn't
yet time to figure out what is wrong.)
Have a nice weekend!
to be precise,
\usepackage[utf8]{inputenc} % for input that can be represented in
% standard-latex-encoded fonts -- t1,
% t2*, etc
\usepackage{ucs}
\usepackage[utf8x]{inputenc} % for input using other fonts for
% output, notably lgr, but lots of
% others too
for wilfried's purposes i would think that simply recognising utf8 and
utf8x options for inputenc would be enough.
--
Robin Fairbairns, Cambridge
rf...@cl.cam.ac.uk (Robin Fairbairns) writes:
> to be precise,
>
> \usepackage[utf8]{inputenc} % for input that can be represented in
> % standard-latex-encoded fonts -- t1,
> % t2*, etc
> \usepackage{ucs}
> \usepackage[utf8x]{inputenc} % for input using other fonts for
> % output, notably lgr, but lots of
> % others too
What if that is not enough, and some very exotic chars are needed? Is it
time to use Omega and Lambda?
--
Juhapekka "naula" Tolvanen * http colon slash slash iki dot fi slash juhtolv
"S teki. S teki. S teki. S wo kakusei. S teki. S teki. S teki. S wo umekome.
S teki. S teki. S teki. M wo setsudan. S teki. S teki. Puratonikku wo
hajimemashou." Dir en grey
forget tex or omega (or even aleph), switch to xetex or wait for a
fully working luatex. that way, the restriction is what's in the
font, rather than what's dealt with by way of macros. (aiui...)
--
Robin Fairbairns, Cambridge