Mailinglist Archive: opensuse (3031 mails)

[David Haller <opensuse@xxxxxxxxxx>]

Hello,

On Mon, 04 Feb 2008, auxsvr@xxxxxxxxx wrote:
> On Monday 04 February 2008, David Haller wrote:
> > Hello,
> >
> > On Sun, 03 Feb 2008, auxsvr@xxxxxxxxx wrote:
> > > Tex doesn't support unicode.
> >
> > Inputenc supports UTF-8 for quite a while now.
>
> It only supports a subset of UTF-8,

UTF-8 is an encoding of a character-set, not a character-set. And
LaTeX supports a huge part of unicode. The bigger problem is finding
fonts which contain the glyphs.

> as Tex wasn't designed to support 16 bit fonts. It's a design
> limitation.

TeX uses many different fonts anyway, most traditional fonts are only
7-bit.  This has no influence whatsoever on what glyphs LaTeX
supports. E.g. traditional TeX uses 7-bit encodings and 7-bit fonts
and supports many more glyphs (more than latin1 + at least 256 math
signs).

> This does work. Probably even spanish accents work, so this may help Carlos.
> However, this doesn't mean that unicode is supported, which can be verified
> easily by typing the €= (euro character) or characters of most other scripts
> in the world.

You need to use packages to support the characters. E.g:

====
\documentclass{scrartcl}
\usepackage{lmodern}
\usepackage{textcomp}
\usepackage[utf8]{inputenc}
\listfiles
\begin{document}
äöü߀óéñõ\end{document}
====

You need textcomp for \texteuro. You'll need CJK or something for
asian characters, etc.

If it doesn't work for you, you're missing something (in the log or a
package or ...).

BTW: I use a quite old TeX (teTeX 2.0.9 IIRC), with some updated
packages. And the above works for me.

-dnh

-- 
There are two major products that come out of Berkeley:
LSD and UNIX. We don't believe this to be a coincidence.
                                   -- Jeremy S. Anderson
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx