Am Dienstag, 16. Januar 2007 11:29 schrieb Jacek M. Holeczek: > In principle, the "fall through" in the patch should take place only when > LaTeX does it, too ... but I don't know how to test for "T1" (nor which > additional conditions should trigger this behavior and thus be tested). > However, according to: > http://en.wikipedia.org/wiki/Caron > http://de.wikipedia.org/wiki/Caron > these four special characters (d,l,L,t) are ONLY used with caron in Czech > and Slovak languages, and ALWAYS with the "special caron" form.
That is interesting, we finally found somebody who knows what this "special caron" is. This is really amazing: No LyX developer knew that this was indeed working, and that people used it. The same is true for the "default" encoding: First we thought it was useless, no we know that the opposite is true. We are going to get rid of InsetLaTeXAccent for 1.5.0, because it is not needed anymore since we support unicode. When importing old documents with lyx2lyx we are going to convert the normal caron to the unicode character 0x030c. Can you please tell us what we should do with the special caron? Convert to 0x030c too, or to something else? > Thus, I believe one can safely put this "unconditional fall through" ... > unless you know any other languages for which is should not be done ... > which I have not found (working hard on this issue) ... > (Last, but not least, please note that, this patch influences ONLY the LyX > window display, the generated LaTeX/ps/eps files will ALWAYS be fine, > regardless if this patch is in or out.) I think this part could go really in, since it is no risk and it seems to be very important for Jacek. > Please commit this patch. This is a bug fix. A serious one for me. On a > couple of occasions, I have already reported that, the current LyX > produces INCORRECT LaTeX code when it finds a character, in the ".kmap" > file, which it cannot display by itself. This patch is a fix to this > problem. A working one ... I believe it does not influence anything else. Can you give an example please? E.g. character typed in, resulting stuff in the .lyx file and resulting .tex output. > And how about "combined" cases? > For the moment, I have made this patch as simple as possible ... fixing > only the nasty bug with "keyboard enter" ... I have no idea how these kmap files work, but can they really contain LaTeX code? I would rather think that they could contain anything you would normally type in LyX, that means not arbitrary LaTeX. Therefore I don't think the part that patches TransManager is correct. > As I have already told you, many of the people I work with will not be > able to use 1.5 for a very very long time. And because we need to exchange > files, we have to stick to a "common standard" that works on different OS > flavors and different OS versions ... for the moment, this can only be LyX > 1.4, and if not, we will have to drop LyX going back to the "common" pure > LaTeX. If they can't upgrade to 1.5, how can they upgrade to 1.4.4? It looks like 1.5.0 will really have a lot of improvements over the 1.4.x series, and it will definitely be more stable than 1.4.0 was. Therefore I recommend to upgrade. Georg
