I am quite proud that I managed to embed the json file of the menus in the PDF for both the iOS and web version 
Makes it super convenient to be able to have a nice PDF file that you can also import to edit! Also the app has a preview extension to render the native json format (.rmenu/ .relationshipmenu) as a PDF when opening it in files 
#fileformat Friday! ...because sometimes size does matter! Remember ACE? #digipres #obsoletearchive https://preservation.tylerthorsted.com/2025/09/12/ace/
Huh.
Right this second is when I learned that the .mobi file format is owned by Amazon !
Hmmm, advice please.
So; say you're a #opensource #vector image editor and a volunteer pops in to help write a new compatibility to some proprietary #fileformat.
Say the volunteer makes progress and one day a brand new account claiming to be the founder at the #proprietary company of said format offering the volunteer a job.
To me; this is clearly a way to foreclose work on compatibility. The #foss equiv of buying out a competitor.
But how should the project moderate this kind of message?
I don’t suppose anyone has reverse-engineered the old 90ies Apple DocViewer file format? I know someone decoded THINK Reference, but I'm kinda hoping that DocViewer will be better than PDF for extracting structured info from Inside Macintosh.
Sadly there's an MS Word display app called “DocViewer”, so web search is kinda difficult.
