There is a logical bug, in the OPML export/import modules, which needlessly breaks oo3->OPML->oo3 round-tripping.
This concerns the handling of boolean columns ("checkbox" columns).
Whereas the default status checkbox is encoded as _status="checked" in OPML, and can be round-tripped back into a boolean checkbox, the handling of any additional checkbox columns is defective, converting booleans into irretrievable integers.
For example, a checkbox column named "Flagged" in Omnioutliner would get encoded by the OPML exporter as Flagged="0", and would be brought back into Omnioutliner not as a checkbox field but as an integer field with zeroes and ones, breaking the data structure and the simple round-tripping.
A bug, I would submit :-)
This concerns the handling of boolean columns ("checkbox" columns).
Whereas the default status checkbox is encoded as _status="checked" in OPML, and can be round-tripped back into a boolean checkbox, the handling of any additional checkbox columns is defective, converting booleans into irretrievable integers.
For example, a checkbox column named "Flagged" in Omnioutliner would get encoded by the OPML exporter as Flagged="0", and would be brought back into Omnioutliner not as a checkbox field but as an integer field with zeroes and ones, breaking the data structure and the simple round-tripping.
A bug, I would submit :-)
Threaded Mode