Uwe Stöhr <[EMAIL PROTECTED]> writes: > This tex2lyx version id for LyX 1.6 and not for LyX 1.4.
Sure, but if we declare that a file is in some version, it should really be of this version. We are going to have problems otherwise. >> The process is not that you dump a big tex2lyx patch and then others >> are required to try it out. A better approach would have been first to >> implement the missing features in 245 that you could fix (actually, we >> are probably at 247 now). > > I just don't want to support commands in the way of LyX 1.4. because > then the work has to be done to be ready for LyX 1.6's format again. Well, the parts that handle language change and encoding are probably OK. Also, since we have new font scheme and you just introduced framed.sty support (right?) the format can probably be upgraded to 247. Things in your patch that look like <247 are: support for \lyxline, \selectlanguage, \foreignlanguage, \inputencoding, shaded note, framed note, font settings, updated language support (?), support for document encoding, updated support for amsmath. That is still a big part of your work. > OK, then I remove my patch until somebody fixes the unicode stuff. > (I'll try this too.) Thanks, but try to keep the parts that still make sense. It is in this sense that I wrote that a flurry of small patches (for each feature, almost) are easier to handle. >> This is the difficult part, but it has to be done anyway. Then continue the >> easy road of new features. > > Easy road? It was not very easy. Sorry, I did not want to belittle your work. From my experience of tex2lyx, adding a new feature ranges from trivial (a new macro) to horrible (nested environments). Now that you have found your way in tex2lyx code, I trust that you will find the work easier. JMarc
