G-Node
File extension '.odml'
In a previous version all odml files had the file extension .odml. After support for JSON and YAML was added, the .odml file extension was no longer supported.
Some people still use the .odml file extension, since it makes odml xml files easier to spot.
This issue raises the question whether we could support a compromise solution by adding a secondary .odml.xxx file extension. This makes odml files easy to spot, but keeps the appropriate file format extension which is important e.g. when viewing xml files in a browser or automatically detecting the format via the extension.
As examples, the file extensions of all saved files would look like this:
example.odml.xml, example.odml.json, example.odml.yaml
I'm not at all against this. One consideration is that it will show the extension .odml in file browsers that hide known extensions (Windows by default). This will probably only happen for XML.
I also think this is a good compromise. The only point I would like to add is, that in case of filename handling using string manipulation instead of proper package functions, this might lead to unexpected results. But I guess nobody here is doing this anyway, right?
