On Tue, May 31, 2005 at 08:24:17PM +0200, Sven Schreiber wrote:
> Hi, I just stumbled over what I think is a little quirk in tex2lyx. When
> I convert a file that contains {\ss} latex codes, using the tex2lyx -
> lyx2lyx - lyx 1.3.5 procedure from the wiki (on windows), the braces
> appear as ERT in the final lyx file, although they are redundant.
>
> The braces don't do any harm, they're only redundant.
Now just hang on for a second and try to figure out the kind of effort
needed to prove that a certain construnct in a .tex file is redundant.
> 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)
Well, why not write "Soße" in your .tex. Works since the end of the
previous millenium...
> So is it possible for tex2lyx to recognize a pair of braces that simply
> serves to delimit latex codes from surrounding text, and remove them in
> the lyx file? That would be great.
It is 'possible'. However, it is almost impossible in this area to get
anything right in all cases, so I am somewhat reluctant to have too many
'clever' additions to tex2lyx, especially if these additions are
specific to certain laguages only.
> 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.
As far as I am concerned this is rather ugly output of WinEdt. People
could always run the thing through perl -e 's:{\\ss}:ß:' if they want
to have an automated conversion. Or convince the WinEdt folk to
produce 'suitable' output.
Andre'
