JOSM devs,
I am slightly unhappy about the fact that we have control characters
(more specifically, the "record separator" 0x1e - someone must really
have read their standards) in the config file. This means that I cannot
simply email someone and say "add this line to your config file" (e.g.
to support a new imagery source).
I would like to change that to a semicolon. (Plan: prepend config file
with a line that goes @version=something, so we can see whether we have
an old-style or new-style file, support old-style on reading but only
new-style on writing, escape any existing semicolons and backslashes
with a backslash.)
Any objections? Or does someone maybe have plans for a grand re-write of
the config file code anyway, maybe changing to "ini" file syntax, XML,
or YML? The countless "config.option.0"-style entries cry out for some
structured config file format but I'm not a big fan of XML configs...
Bye
Frederik
_______________________________________________
josm-dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/josm-dev
