Thanks so much for your reply. Quick answers in turn…
-I’m actually using an older version of OmniOutliner, so it’s unlikely that an upgrade would affect the way that it’s reading MarginNote’s Export output;
-I’m not using iPadOS 13 for any of these exports, so that’s not relevant in this case;
-I’m not sure what you mean by suggesting that import / export my “documents to a more compatible app.” I’m importing regular PDFs, and I’m only using MarginNote’s Export output formats – that is, these are the Export file formats that MarginNote provides!
-Also, as I’ve informed you before, many users continued to have problems with other MarginNote’s Export output formats (e.g., in MarginNote’s DEVONthink rtf/rtfd file format), including: this export format creates another set of filenames and tiles (i.e., often starting with the “P0000_” prefix), a lot of extra space between the blocks of text in the notes, a combination of plain and stylized text, and an inability to change smart quotes / apostrophes to straight quotes / apostrophes.
(Again, this is why many users have asked MarginNote to create OPML, CSV, Tab-delim exports!)
As a result, many users have to rely on third-party apps, like TextSoap or BBBEdit, to clean up all of these problems with MarginNote exports.
But…these third-party apps cannot correct the problem that I first identified in this post, namely: MarginNote’s OmniOutliner is creating export errors, specifically: It’s creating inconstant names / tiles under OmniOutliner’s Topic column that MarginNote generates – or it leaves the names / tiles blank under OmniOutliner’s Topic column if users don’t provide titles for each MarginNote notes.
Anyway, I hope you understand that I’m not trying to be critical, but help inform MarginNote about these problems so that they can take appropriate measures to fix them. Thank you again for all of your help and hard work!