On Tue, Feb 11, 2003 at 02:46:48PM +0100, Jean-Marc Lasgouttes wrote: > Andre> The tokenizer should be ok unless someone starts changing > Andre> catcodes ore redefines macros. The "backend" (i.e. writing the > Andre> proper .lyx constructs) is far from working, let alone > Andre> complete... > > Are you sure that producing a .lyx file is the way to go?
No. But it has certain benefits: - No dependence on LyX proper. - Small. - No need to access fragile LyX internals. > Another way would be to build a lyx document and then write it. Yes. Actually that's what I intended originally. But it turned out while removing stuff from the math parser, that writing the .lyx is feasible and less effort. And as long as the LyX core is the mess it is I'd rather avoid internal interfaces as these are more likely to change than the comparatively stable external format. > This would mean that you do not need to update the program everytime > there is a change of interfaces. I do not have to. If all tex2lyx does is to produced lyxformat 222 reliably, the burden to create future formats is shifted to lyx2lyx. Of course, if at one point of time the format has evolved too far, tex2lyx might get an update. > I presume that you thought about that. So what are your reasons for doing > it like you do now? See above. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
