On Thu, Jun 18, 2009 at 10:20 PM, Georg Baum<georg.b...@post.rwth-aachen.de> wrote: > For practical reasons, I would strongly suggest not to import the > information, but to use the file as is. That way, it will be easy to > exchange additions/fixes in both directions. Please note that a python > parser does exist already: development/tools/unicodesymbols.py. If you need > to store some additional information, it might be interesting for LyX as > well, and the format is not set into stone.
I saw unicodesymbols.py and used it to figure out how to import the information, thanks! If it is any use for LyX, I can export the Unicode char code and the corresponding math mode command that I have for eLyXer; but I lack other information like text mode command, TeX package, etc. There should be some 200 commands not in unicodesymbols. > If you import the information and maintain your own version, the two sources > will diverge rather sooner or later, and that would be a pity. For the moment I can import new versions of the file using a bundled tool: $ exportconfig --importcfg py which is prepared to do the job however many times are necessary: it only adds new symbols which are not already in eLyXer's configuration. This way it can be synchronized as needed. Alex.
