HTML might be considered "easy", but, unless I am missing something, it does not retain the outline order; the exported folders and files are sorted alphabetically. The copy/paste approach is nice, but it does not create the individual files I would like to import into Scrivener, nor does it transfer the contents of the notes. A simple, user-friendly OPML export would be great.

Asaf, Exported HTML files never have an order in the way your describe it - they are just files. It is the links within the HTML themselves that give effective structure. OPML is just another form of mark-up (like HTML, XML, etc.) only less standardised than HTML. The latter fact means you need to plan which parts of your TBX need exporting - TB can't always guess your intent.

Please download and try this demo TBX file which shows how to do OPML export. Do the demo and see if the output imports correctly into Scrivener (an app I don't have/know). If so, just copy the 2 templates used by the demo across to your own documents (you can drag-drop between TBXs). If stuck on how to use the templates in your own TBX, do ask back here. Tip: to help us help you in the latter case, it would be useful if you post a small specimen TBX showing your style of TBX layout so we've a common reference.

Everyone does their export a little differently, so don't be downhearted if your first guess at wiring up your own TBX for OPML export doesn't work. I'm sure we can help.

OK, I've prepared a new demo. NOTE: I don't believe OPML was really intended for multi-paragraph data like this so if it doesn't work you might need to look at using a different format. Let us know if this works.

Also, if this doesn't work, please post an example of an OPML file that does work as you expect.

Well, the OPML exports from Tinderbox as asked for so the error is on the Scrivener end. The code you post proves the point. OmniOutliner is exporting 'text' in a non-standard OPML <oultine> attribute called '_note'. Scrivener has clearly been hardwired to use Omni's private extension to the OPML. I did look at the Scrivener site and its manual but the latter neglects to mention how its OPML import works and what OPML extensions it requires; you might help yourself by posted a request on the Scrivener forums that they add something to the manual about OPML; if the app expects non-standard input it helps to know what the variations are.

I've posted another demo that - based on the OO example to give above - outputs code that is compatible Scrivener custom OPML extensions.

(Tinderbox can't create the <extensionState> tag as the export code doesn't give access to that info but again, the tag is a non-standard Omni addition to OPML.)

I think the last demo ought to solve the problem as I've fixed the TB OPML export to mirror that of OmniOutliner (OO).  The problem may be if you are putting more than one paragraph of text in your TB notes and XML (the code used for OPML) created doesn't sit well with Scrivener's XML parser. Anyway please tell me how you got on with the last demo I made for you (OPML-for-Scrivener.tbx). Specifically, you need to try the export/import process with TB notes that have zero or one paragraphs of text, before trying export with notes that may have greater than one paragraph of text. Let me know the results of that.

I appreciate you don't want to get involved in the tech side of this, but unfortunately you're asking for something for which there isn't a simple answer. A 'universal translator' is still in the realms of science fiction! The problem here is you want a push-and-go solution for something which doesn't use a consistent syntax.

My hunch is Scrivener has a kludge to accept whatever OO's OPML output is.  Hover, the latter';s not documented. Can you make an OO note with more than one paragraph of text and successfully get it into scrivener.  If so I'd need to see the file (not just the code pasted into a forum post) so I can see how OO deals with paragraph delimiters.

If OO OPML only imports to Scrivener only works when there's one paragraph of text then that's a limitation on the Scrivener end that we can't work around here.

It looks like there's already a solution as quoted here, in the Scrivener support thread. AmberV - the forum moderator over at Scrivener support forums - is also a Tinderbox user and pretty code savvy.  My hunch is this is a problem better followed up on the scrivener support forum. TB can emit HTML, XML, OPML, etc., but what we don't know is what Scrivener will import. From the app's author's comments it doesn't parse any OPML but rather only a very particular layout.

The forums at Scrivener sound pretty helpful so I think that's your best bet at this point.  If you know exactly what's needed but not how to produce it, call back here and we can have a go at making something suitable.

Thanks. I sincerely appreciate your efforts on this.
Keith, author of Scrivener, is keen to resolve the TBx-->Scrivener export issue. How do I get you folks to talk directly?

I still maintain that the best way to get a book-like structure from Tinderbox to Scrivener is via the HTML exporter engine. I have posted new, detailed instructions in the Scrivener forum in response to the sister thread, here:

http://www.literatureandlatte.com/forum/viewtopic.php?f=2&t=7244&p=59063#p59...

Using the method I describe, you'll have a fully retained outline order, rich text with long document support, and styled titles. The method is simple enough that it could be tweaked fairly easily to produce different results. There are sample files provided, and using those you can see how you can from from Tb to Scriv in ten seconds, once you have the system built.

The only downside to the method is that by working around file system definitions, titles become somewhat generic and numbered. This may or may not be a deal breaker, but if you keep your titles short (very short), you may still be able to work something in by adjusting the scene and chapter rules to `$HTMLExportFileName = $SiblingOrder + " - " + $Name`