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
If I think the folder format of yWriter or Manuskript, there is not really any obstacles using them close to native project format in MaweJS.
yWriter has some index files at the directory tree root, and it splits the scenes to individual RTF files. Fundamentally, there is no actual limitations why MaweJS should use its own XML-based file format to store projects. It could happily split scenes and parts in to a directory tree, and read them there.
So, one option for migrating projects from one tool to anohter, is that MaweJS just happens to have native support to use some foreign project format. It does not have to be entirely lossless.
At least Manuskript has a feature, that you can ZIP its project folder, and share it as an archive. This should not be a problem to MaweJS, vice versa: operating with one file instead of directory tree is generally easier.
The ultimate goal would be to support directly Scrivener project folders. Without much investigation I already know that not all things can be supported. Scrivener is not only a story editing software, you can do all sorts of other texts with that. It is like "Word" in the structured editors realm, meant for any types of texts.
The text was updated successfully, but these errors were encountered:
mkoskim
changed the title
Migration: Native support for foreign project formats
Migration: Native support to foreign project formats
Aug 11, 2023
If I think the folder format of yWriter or Manuskript, there is not really any obstacles using them close to native project format in MaweJS.
yWriter has some index files at the directory tree root, and it splits the scenes to individual RTF files. Fundamentally, there is no actual limitations why MaweJS should use its own XML-based file format to store projects. It could happily split scenes and parts in to a directory tree, and read them there.
So, one option for migrating projects from one tool to anohter, is that MaweJS just happens to have native support to use some foreign project format. It does not have to be entirely lossless.
At least Manuskript has a feature, that you can ZIP its project folder, and share it as an archive. This should not be a problem to MaweJS, vice versa: operating with one file instead of directory tree is generally easier.
The ultimate goal would be to support directly Scrivener project folders. Without much investigation I already know that not all things can be supported. Scrivener is not only a story editing software, you can do all sorts of other texts with that. It is like "Word" in the structured editors realm, meant for any types of texts.
The text was updated successfully, but these errors were encountered: