Sven Schreiber wrote:
> Example: the latex input So{\ss}e should appear as Soße in the lyx file.
> (Hope the German es-zett is preserved in the mail.) What appears is:
> So<ert>{</ert>ß<ert>}</ert>e.
>
> Tried to workaround with So\ss{}e, which gives
> Soß<ert>{</ert><ert>}</ert>e (still two different ert insets)
Thanks for the report, this is fixed now (see my other mail).
> Btw, note that all the {\ss} in the input file were caused by the WinEdt
> (very popular windows latex shell) function to automatically save
> non-ascii input as ascii-latex-codes. So I guess this (minor) problem
> may appear more often in the future when lyx on windows is more
> widespread, and many people want to import their non-English latex files
> into lyx.
Recognizing {\ss} in tex2lyx would be possible but too much special casing
IMHO. What do others think?
It would be something like
Token t = p.get_token();
if (t.asInput() == "{") {
if (p.net_token().asInput() == "\\ss") {
t = p.get_token();
if (p.next_token().asInput() == "}") {
t = p.get_token();
// handle "\\ss"
} else {
p.put_back();
// handle "{"
}
} else {
// handle "{"
}
}
Georg
