@mrkwr - just what I needed. You probably have them already, but if not the process of getting the OPML export templates (the process uses two) is simple. Just as in v5, go to the File menu -> Built-in Templates -> OPML. TB will create root-lvel container for the templates needed and place the templates inside that. It will also add the 'HTML Template' prototype to the file. Of course, if you're mote expert with OPML you can further modify the templates or simply write your own. The export process simply uses the templates you direct - if set up for OPML, then your export is OPML files, etc.
Assumption: you're using the built-in OPML templates. If not insert your appropriate template names in the steps below. The main OPML export template is called "OPML" (same as v5) and uses a recursing child template "OPML Item".
So, to export a given container and all its descendants as an OPML file:
- Select the container to export.
- Open the Inspector (Cmd+1).
- If not already selected, click the '<>' button in the top button bar to select the HTML Inspector.
- Select the 'Export' sub-tab. It should look like the screen grab in the last post above in this thread.
- Leave the tick-boxes as they are shown above, except un-tick 'Export Children'.
- Optionally set 'File Name' for the exported filename without a file extension.
- Change 'Extension' from '.html' to '.opml (don't overlook the starting period).
- From the 'Template' pop-up, pick the OPML main template. They are listed by path so in a default set-up with built-in versions it will be '/Templates/OPML'.
- Optionally set an 'Export' location or use the current setting.
You are now set up to export the OPML, but there's one further issue - and it's a glitch I've just reported - you need to use File -> HTML Export to run the export. As such it exports the whole document. To avoid that, for all root level notes/containers - assuming you don't use export except for OPML - that select each in turn in HTML Inspector and untick 'Export' and 'Export Children'. For any ancestors from root to your OPML container, only untick 'Export', so that descendants can still export.
As with v5, if you're exporting from a non-root level container (i.e. $OutlineDepth >1) the export to the OS folder specified in the HTML Inspector will occur but nested within a set of parent containers. To explain, if container Z is a child of container Y which is a child of root-level container X and we export to the Desktop, the latter will create a folder X, nesting folder Y which will contain the OPML file for Z.
Sidenote, it you do occasional exports of discrete parts of your TBX to OPML then consider making a prototype 'OPML container'. Most of the settings (bar the OS export folder) are actually attributes so can be set and inherited. If you need to export notes both to OPML and in other formats, this is possible but as it takes some setting up I won't confuse but describing it here - just ask if needed,