>>>>> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:

Georg> lib/unicodesymbols contains a list of ucs4 code points and
Georg> LaTeX commands. This list is used to output characters that
Georg> cannot be encoded in the current encoding and replaces the
Georg> hardcoded stuff for euro & co in
Georg> Paragraph::Pimpl::simpleTeXSpecialChars. It is also used for
Georg> the characters that were handled by InsetLaTeXAccent formerly,
Georg> although I only added those code points manually that the
Georg> attached test file uses. Later we can complete this list using
Georg> similar existing databases like that of plastex. The nice thing
Georg> of this list is that we do not need to care anymore which
Georg> encoding has which characters - we are using iconv to get that
Georg> information (see below).

Question: is the equivalent of \'{e} '+e or directly é (in the
internal representation)? I do not understand the stuff about
surrogate characters in the patch.

Second point: rather than putting in explicit preamble snippets I
think we should go for feature (i.e. put "textcomp" there, and handle
it in LaTeXFeatures).

Is it really necessary to look at the outerfont to know the encoding?
Can environment nesting really change the encoding? 

Georg> In order to properly output accents on spaces I had to remove
Georg> an (IMO ugly) hack that tries to do clever things with spaces
Georg> and font changes (see
Georg> http://bugzilla.lyx.org/show_bug.cgi?id=1428). I am not sure
Georg> whether this is a file format change, but IMO we should not try
Georg> to be clever here and simply output what the user entered. If I
Georg> don't want \textbf{xxx }, then I should not mark the space as
Georg> bold face.

This is OK.

Another question: what is the status of kmap files with this patch?

All in all, I like the patch (but I have not tried it).

JMarc

Reply via email to