Good question.
I just went through one of my backups. Recently they came up with TextBundle:
http://textbundle.org/ and they're using it in the iOS version, and maybe even the Mac (I don't have it yet).
If you look through the backup folder, you're going to find another one called Content with whatever folders you had on the app at the time, and if you look through that, you'll see these randomly named files with the .ulysses extension.
If you change it to something else, like txt, or whatever, it changes into a folder with this structure:
Code:
Content.xml
text.txt
And then an assets folder.
The XML file will have specific things like what type of Markdown you're using, and how it should be formatted, along with your tags, notes, etc.
Code:
<markup version="1" identifier="markdownxl" displayName="Markdown XL">
<tag definition="heading1" pattern="#"/>
<tag definition="heading2" pattern="##"/>
<tag definition="heading3" pattern="###"/>
<tag definition="heading4" pattern="####"/>
<tag definition="heading5" pattern="#####"/>
<tag definition="heading6" pattern="######"/>
<tag definition="codeblock" pattern="''"/>
<tag definition="comment" pattern="%%"/>
<tag definition="divider" pattern="----"/>
<tag definition="nativeblock" pattern="~~"/>
<tag definition="blockquote" pattern=">"/>
<tag definition="orderedList" pattern="\d."/>
<tag definition="unorderedList" pattern="*"/>
<tag definition="unorderedList" pattern="+"/>
<tag definition="unorderedList" pattern="-"/>
<tag definition="code" startPattern="`" endPattern="`"/>
<tag definition="delete" startPattern="||" endPattern="||"/>
<tag definition="emph" startPattern="*" endPattern="*"/>
<tag definition="emph" startPattern="_" endPattern="_"/>
<tag definition="inlineComment" startPattern="++" endPattern="++"/>
<tag definition="inlineNative" startPattern="~" endPattern="~"/>
<tag definition="mark" startPattern="::" endPattern="::"/>
<tag definition="strong" startPattern="**" endPattern="**"/>
<tag definition="strong" startPattern="__" endPattern="__"/>
<tag definition="annotation" startPattern="{" endPattern="}"/>
<tag definition="link" startPattern="[" endPattern="]"/>
<tag definition="footnote" pattern="(fn)"/>
<tag definition="image" pattern="(img)"/>
<tag definition="video" pattern="(vid)"/>
</markup>
And it basically has a recreated version of the text with the above definitions, and then the attachments are noted at the bottom (keywords here):
Code:
<attachment type="keywords">food,random,blah</attachment>
The text.txt file is just the plain text.
And then your assets folder has your images/whatever.
They've tried to solve the problem where most Markdown apps are just useful for text and can have very little else without getting proprietary. You could simplify it for your needs with some Applescript. Probably will have a go at that actually.
I guess I'd rather deal with having to do this
now, then figure out how to read WYSIWYG files ten years later. There's lots and lots of threads where people can't open old Word files, etc.
