You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Earlier this year Jim Horne updated the XPF format from version 1.0 to the current version 2.0, in part to be similar to the output of his Across Lite To Text program. Among the other changes he made is some of the XML tags are renamed, thus the XPFv2.0 files cannot be read by XWord, hence this issue.
The text was updated successfully, but these errors were encountered:
Adding support for reading the new version shouldn't be too difficult. One question here is what we should do when saving - do we just save using the new version too, or is there value in maintaining backwards compatibility by saving in the old format? Some options could be:
Support XPF 2.0 as a fully separate format (so user has to choose to save in 1.0 or 2.0)
Drop write support for XPF 1.0; always write as 2.0.
Write as 2.0 except when the original input was XPF 1.0, in which case we use that version.
Earlier this year Jim Horne updated the XPF format from version 1.0 to the current version 2.0, in part to be similar to the output of his Across Lite To Text program. Among the other changes he made is some of the XML tags are renamed, thus the XPFv2.0 files cannot be read by XWord, hence this issue.
The text was updated successfully, but these errors were encountered: