Ok, I understand its purpose now. It's not supposed to be read by humans ;)

"vlad" wrote:Indeed. Hopefully it's not biggie if we'll correct this.

I was thinking that maybe this line could be editable by the user. You know, something like the page setup when you print from a browser and you want to insert the date and page number in the header or footer...



You could use literals and variables for node type (%T), node caption (%C), path (%P), depth (%D) and position (%N) in the tree...

I can see uses like the current one

--- [%T] %C --- Path:%P (Depth: %D) ---

and like that :

Chapter %N - for a short story or a novel, useful to print out drafts for editing

Day %N: %C - for a travel diary (Day 5: My first day in Brazil)

Lesson #%N - "%C" - for teachers and such (Lesson #6 - "How to plant tomatoes")

### - the '###' literal is used by the yWriter software to split text files into different scenes

Could be improved with page-break and new-line variables, a definable number of blank lines before and after the header line, a font and size choice, and a left/center/right alignment...

Now that definitely is more a feature request than a bug report :D



Lush

It's in English with purpose - to enable import in third-party applications with automatic restore of hierarchy position. I'm not aware if someone is using this, but the point is this - using this information it's easy to write code/script which will convert such RTF file to any other file format and restore tree structure.

…there should be a space between the last closing parenthesis and the three hyphens…

Indeed. Hopefully it's not biggie if we'll correct this.

Hi,



Not a bug per se, but when exporting to RTF, the 'headers' are not translated:

--- MyFolderNoteName --- Path: MyPath\ToMyFile (Depth: 2)---

'Folder', 'Note', 'Path' and 'Depth' are lacking translation strings.



(and to nitpick a bit, there should be a space between the last closing parenthesis and the three hyphens ;))



Lush