Hi Philipp, On Thu, May 13, 2010 at 7:21 PM, Philiрp Rеichmuth <[email protected]> wrote: > This isn't obviously what eLyXer was designed for and there were some > glitches, such as having to patch extra values into ContainerConfig for > parsing custom character style insets. But eLyXer in its current state > would be a good basis for a universal LyX file parser and document object > model in Python; one could then refactor the HTML converter to work on this > document object model. This would be useful for everybody processing LyX > files with Python scripts, also if the file format eventually changes > towards XML or whatever. It's obviously nothing for an 1.0 release, more > like 2.0, but what do you think of it?
I think it's great! In fact I have always thought as one of the benefits of having an external LyX->HTML converter that there is an alternative implementation of the LyX format, even if not complete yet and read-only. If you want we may move the discussion to elyxer-users for eLyXer specifics, as LyX users may find it boring. Thanks, Alex.
