Problems with OmniOutliner export

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.

I hope @Support-Team can correct this soon. Thanks.

1 Like

Yes, I’ve faced this same problem, myself. I hope they can address it, along with other glitches in MarginNote exports. Thank you.

Hi Jprint,

Third parties’s compatibility with marginote may be lowered owing to upgrades of these apps(e.g.Format changes). Anyway,we will carry on our work on development to get with it in time.
Meantime,I suggest you export your documents to a more compatible app first and then export from it to these apps you prefer to use,which is a feasible compromise.

Last but not least,please bear it in mind that iPadOS 13 seems to have some troubles in compatibility of export across apps .

Best regards,
Lanco
MN Support Team

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!

Hi jprint,

I’ve got your request and trying to reproducing the issue as you mentioned.

We think highly of Integration Support&compatibility. Again,thank you for your report ,which has been put into our dev. assignment now.

Best Regards,
Lanco
MN Support Team

1 Like

Thanks, @Lanco-MN_Support. I appreciate that, but it doesn’t appear that @Support-Team has done anything to correct these problems yet. When do you expect these changes will be made by @marginnote ?

Thanks.

I‘m still directly exchanging ideas with developer Min. We are planning a big change to MN3 data management. Across hashtags, searching engine, UID and export needs. And we see change the notebook format to opml is possible which means sync with opml files. And this opml files contains UID information. For a long-term consideration,we will try to provide a Mod platform maintained by your Community force using AppleScript or sth else.

1 Like