Text Export - points to consider

Unlike HTML Export, the Text Export (Nakakoji) view works on slightly different premises:

• you can effectively only have one Nakakoji view open at a time - it will refresh as you change selected note(s) in your main view.
• the default scope of opening a Nakakoji view is 'Selected note and contents' - it doesn't remember your last choice; if you need 'Selected notes' then you'll need to change that each time you open the view.
• the view always defaults to using the template specified it the app or doc preferences (latter takes priority if different).

So, if you change the current selection, your Nakakoji view will update. When opening the view you also need to make sure you select the desired scope. this is especially true if selecting a custom template that uses cascading sub-templates.

Do not use export-related codes like ^include^ or link creation codes in templates for Nakakoji use. and consider the impact of such codes existing in the text of actual notes. This view exports plain text without emphasis mark-up or links. Using includes can cause unintended loops that Tinderbox may struggle to resolve.

Depending on the scope chosen via the radio button, you may need to consider using different templates; experiment on small data sets whilst learning how to use text export templates.

Indenting is possible by using Tabs and ^indent^.

When looking at large selections such as the entire document, do allow time for the code window to render. In such circumstances, with lots of text, it is not unusual to see the spinning beachball 'busy' cursor. If so, allow the application time to complete the task.

If using templates that call - or recursively call - child notes, use the 'Selected notes' scope option (#3) rather than 'Selected note and contents' scope (#2 and the default).

Experimenting with large text selections and/or export templates - especially the first few times - it is a good idea to save your TBX before opening the view.

v4.7.1 fixes an issue where using ^title^ would result in characters like ampersands and others being HTML entified.

Licensed under Creative Commons Attribution-Noncommercial-Share Alike 3.0 License
[See aTbRef CC licence Attribution/Waiver info info]