RTF export: final paragraph isn’t terminated with \par. Edits get lost when the file is reopened in Scrivener.

Post Reply
o4xmkdgee
Posts: 2
Joined: Sun Nov 01, 2026 10:32 pm

RTF export: final paragraph isn’t terminated with \par. Edits get lost when the file is reopened in Scrivener.

Post by o4xmkdgee »

I'm sending this bug error through here since Scrivener doesn't seem to release new windows update anymore, I'm sending an error report to Scrivener too, but I wouldn't be holding my breath, and I've used this program for years so I'd be really thankful if you could also try a hotfix on your end. I found this error by myself and used Claude to create, edit and compare multiple imported and exported files through both programs, and reached this conclusion:
When TextMaker saves a document as RTF, it omits the paragraph mark (\par) after the last paragraph. Scrivener imports such files without any error, but it silently keeps its previous version of the document and discards every edit made in TextMaker. Adding a single \par before the final closing brace makes the same file import correctly, with no other changes.

Steps to reproduce:
1.- Create a short RTF document in Scrivener for Windows and sync it to a cloud folder with Scrivener’s “Sync with External Folder” feature. This also reproduces with a document created in any app, as long as it’s then saved by TextMaker. [/list]
2.- Open the .rtf in TextMaker for Android, add a line of text at the end, and save as RTF. Don’t press Enter after the last line.
3.- Sync the folder back into Scrivener.

Expected: the new line appears in Scrivener.
Actual: Scrivener reports the document as updated and takes a pre-sync snapshot, but the content is unchanged. All edits from TextMaker are lost.

Posible explanation from inspecting the RTF code: TextMaker’s file ends like this, with no \par after the last paragraph:

Code: Select all

…\loch\f0 (This line of text was added in TextMaker)}
If I add \par before the closing brace by hand and change nothing else, Scrivener imports the file correctly:

Code: Select all

…\loch\f0 (This line of text was added in TextMaker)\par
}
Ending the document with an empty line in TextMaker also works, because TextMaker then writes the \par itself. Leaving out the final \par is tolerated by some readers, such as LibreOffice. But Microsoft Word and Scrivener always terminate the last paragraph. Always writing the final \par would make TextMaker’s RTF more broadly compatible.

Thank you for your attention.
o4xmkdgee
Posts: 2
Joined: Sun Nov 01, 2026 10:32 pm

Re: RTF export: final paragraph isn’t terminated with \par. Edits get lost when the file is reopened in Scrivener.

Post by o4xmkdgee »

A correction and an update to my earlier report.

I reported that the missing \par after the last paragraph caused another application (Scrivener) to discard my edits. Further testing showed this was not the cause. TextMaker’s RTF files, including the ones without a final \par, do import correctly. Please disregard that part. (Another small issue showed up, when the source document has no header or footer, TextMaker still writes empty {\header…\par} and {\footer…\par} groups. Some applications import these as blank paragraphs at the top of the document. Omitting empty header and footer groups would avoid this.)

The actual problem was that TextMaker for Android’s backup option writes a .bak file into the same folder as the document on every save [e.g. "Test 5.bak"]. When documents live in a synced folder (in my case, a Scrivener sync folder kept in MEGA), these backups travel with the documents. Scrivener then mistook the backup for the actual document and imported the old text. Turning backups off solved the problem.

My suggestion is that while enabling the backup option, allow for choosing a separate folder for them, as the desktop versions can, or name backups so they can’t be mistaken for the document, e.g. in a dedicated subfolder.

Thanks for your attention, have a nice day c:
Post Reply

Return to “TextMaker NX for Android”