Georg Baum wrote:
I don't think either that there would be a performance problem. What might
be a problem is that an inset knows more about its content (and, more
importantly, about the context) and could do a better conversion than an
external converter could do. For example, I am 100% sure that ucs4
characters exist that need to be translated to different LaTeX macros in
math mode and in text mode. In LyX we always know whether we are in text or
math mode. An external script would need to parse LaTeX, and if you think
that that is easy have a look at tex2lyx (which btw is far from perfect).
Perfect is the enemy of good. Why cares about those unicode characters?
We can hack those somehow if they are important.
In summary and IMHO: let's keep the core C++ LyX simple and only support
utf8.
With my proposal the core would be simple and not even know about utf8, only
ucs4, except for the cases like the example above.
IMO we do not need to answer now the question whether the conversion will be
external or not if we follow my proposal. I really would like to know what
others think.
Tell me a little more about your proposal. What are the pros and cons
compared to UTF-8 + external conversion? So far, I've got:
Pro:
- LyX can do smart conversions depending on context (not important to me)
Con:
- More complicated code
Which to me means that UTF-8 + external conversion wins.
Regards,
Asger
