The only problem I can see with file format is that listings can have
a large number of parameters and lexer may not be able to read the
whole string. Right now, I save/load/transport parameter strings like

language=Python,float

in the form of

language=Python!float

but ! may (I am not sure) be used in some options.

The only solution I can think of is the HTML way, where special
characters are encoded in &1023; etc for storage and transportation.
Does anyone know how to implement this?

If encode decode can be implemented in InsetListingsParams, many
heuristic parts of the implementation can be strengthened. I can then
claim beta quality of this patch.

Cheers,
Bo

Reply via email to