Sven Schreiber wrote:
Jean-Pierre Chr�tien wrote:
Georg Baum <[EMAIL PROTECTED]> writes:
Does LyX support \oe and \OE natively? If yes, we should convert \oe to the
native format (an inset?), if not we should leave it alone.
I'm not aware about native support in 1.3.5 (otherwise I would use it).
So leave it as is.
(No need to respond if this is a totally stupid/unrelated question, I
will get the subtle hint... but here goes:)
Aren't all western characters (iso-8...whatever) supported by lyx?
It's not a stupid question.
The answer is: it depends.
If you use some locale encoding (e.g. iso-8859 a.k.a. latin1) then you'll
be able to input characters like � using your compose key (compose-ss) or a
dead key. The result is stored by LyX internally as a single character
(0xDF I believe) and will be shown on screen correctly.
Of course, if you change your locale encoding to, say ISO-8859-5, cyrillic,
then the (0xDF) character will be displayed on screen as something very
different to an es-zett. That is, your file is not portable. Different
people around the world will see different things.
One solution is to use a single encoding for all lyx documents. We are
proposing to use UTF-8 sometime soon. The es-zett is stored as two bytes in
the UTF-8 encoding and will be recognized as such everywhere.
Another solution is that used by LaTeX which is to define special,
portable, macros like \ss and \oe. If you use these macros in your LaTeX
document, then your Chinese colleague will be able to read what you wrote.
LyX has native support (meaning that \ss is rendered on screen as � rather
than as <ert>\ss</ert>) for some of these LaTeX macros but not all.
Does this answer your question?
Angus
