To export a note as plain text, the contents of the export template is ^text(plain)^ - whether you use Text or HTML export.

File -> 'Export as text' exports one file containing one or more note's content as aggregated via Nakakoji view. By default the file is exported as 'exported file' (no extension). The default output silently overwrites the default output but if you specify a filename it will warn of overwrites. So you could select each note in turn, open Nakakoji view, select the built-in 'text' template and use the export button.

File -> 'Export as HTML' exports the whole doc to HTML, which isn't what you want. There are way to set up the whole doc so bits don't export.  For any note you don't want to export set $HTMLDontExport to true (or un-tick 'Export' on HTML view). For any container for whom you want to suppress all output, set $HTMLExportChildren to false (or un-tick 'Export children' in HTML view). For a few notes, it's simplest to export each via HTML view.

To do the latter, select the note, open HTML view and select the built-in 'plain-text'  template.  If you don't want the default HTML export filename type a name in the 'File name:' box.  Change the 'File Extension:' to '.txt' (include the period!). Then click 'Export'. The first time you do that for a doc you'll be asked for the export location, thereafter the the doc's last used location is remembered. The exported note will be in the export folder is root level. You notes will export into a folder called "Notes" in the export root folder as HTML export reflects the doc hierarchy.

OK then, as described, export the whole file to HTML. Either configure the doc to not export what you don't need, or export all and ditch the exported files. TB's HTML export is designed to export everything (set to export). There is no feature to just export a subsection, e.g. one branch of an outline - at least none I've come across.

A workaround if the above is all too difficult. Open a new TBX, drag all 123 files across to it (i.e. copying them), then setup HTML export (if not already done in the source TBX) export the new file to HTML, throw away the extra TBX when done.

Ah, well $HTMLExportFileNameSpacer - through an unenvisaged usage - might work.

[Later]Tested. Yay. Set the above attribute to " " (a single space). Easiest way is to set an agent to:

query:   inside("Notes")    or "/Notes" if Notes is root level
action:   $HTMLExportFileNameSpacer = " "

If you use odd characters - anything illegal in HTML filenames - in your notes' $Name these characters too will become spaces (see why). Still, I think that fixes your problem.

For once, an upside to an unintended (mis-)use of an attribute.

The practical limit is explained on my article on $HTMLFileNameMaxLength, though it's not a page you'd otherwise rush to read!

It looks like TB still uses 'Classic' Mac max filename length limits. If you need longer, I'd mail in a feature request to move to OS X based limits.

For now, testing in v5.9.1, it looks like the maximum allowed filename length - with a '.txt' extension is 27, or 31 if you use no extension.

Don't forget, it's not all Tinderbox' fault, you could try addressing Scrivener's limitations at the other end.  I'm less well placed to comment on the latter as I don't have/use the app. It is worth bearing in mind, as often here we go through complex changes/workarounds just because of the limitations of other apps. Of course, other apps developers are less flexible, but that doesn't sound the case with Scrivener.

If your notes are using $Text, or its first paragraph as the $Name, consider moving the text back into $Text and using a shorter name. It might not be the process you originally intended but it might achieve the same end

Another approach, use TB Export as Text to export all the notes as one piece of text via a template that delimits each note's content with an easily searched for marker string, e.g. "##########". Then in Scrivener, after import use its equivalent of Explode (surely it has one?) to tease the single run of text back in to 123 notes.

Scrivener has an "Import and Split" feature that will split a text file based on a user-defined token (default is "#", no quotes).  The note names are truncated, though longer than 32, I believe.   Scrivener also definitely imports OPML, which is what I use to get material from Tinderbox to Scrivener.

By 'fault', I didn't mean 'blame'.   Rather, I was suggesting avoiding the trap to which we're all prone of continuing to push on the closed door in front of us just because it's we were doing when we became stuck. It's a trap I'll admit to falling into more often than I should.

As I'd hoped, some fellow Scrivener users seem to come up with some good alternatives. TB's OPML is pretty solid now after a series of improvements through v5. I've updated my notes on OPML import and export as well as giving code for two export templates (here and here) to use for OPML export.

I've also updated my old OPML-for-Scrivener.tbx demo. Despite the name of the file you can use it to export OPML for use with any app accepting valid OPML. I hope that helps...

I'm brand new to scrivener (been playing with it for a few days, then pulled the trigger on the cross promotion Mark just sent out), but my initial thought was that SimpleNote would be the "smoothest" transition.  Any Scrivener users ran across problems or issues on that front that would make the OPML way more attractive?

One side note: is there a technical reason that led to the fact that aliases don't get synced by simplenote?  In thinking about Scrivener-TBX cross-pollination, I was imagining creating a boolean attribute (Scrivener) that I could use to "tag" notes that I wanted to send to Scrivener, then use an agent to put aliases in the Simplenote container.  Since aliases don't sync, this plan didn't work.