Outliner 1.2 and copy-paste text export changes

[Jeremy Reichman]

The new Outliner 1.2 changes the way copy and paste is handled with other 
applications. (I noticed it because it adversely affected a 
slightly-scripted workflow I'd already built around OO.)

I select the entire contents of an outline in OO. The outline has its 
status checkboxes hideen, and has no extra columns.

I paste the text into BBEdit 6.5. It pastes in with each new outline line 
marked with a dash ("-") instead of the older version's asterisk ("*"). It 
also hard wraps the text to an abnormally narrow column width, which did 
not happen in the previous version.

I have not changed any settings in BBEdit 6.5 since upgrading to OO 1.2. I 
also had the default preferences from OO 1.2.

If I export text (a much more lengthy process) from OO, I can open it up 
in BBEdit 6.5 and it will more closely match the output I had before. 
However, this is only after I change the text export prefs in OO to use an 
asterisk for all levels of outlines. Also, OO seems to put an extra blank 
line at the beginning of the text export file.

My process depends upon the previous text-pasting behavior of OO, to the 
extent that I have BBEdit doing some grep searching and replacing on each 
line. Unless I change the prefs back to match what OO did naturally before,
  and then to a text export, my AppleScripting needs to be modified. 
Grepping the text output from OO by default is now more involved, because 
each outline line can start with a different character.

I can't really test this change when pasting to TextEdit, because it 
appears to paste according to the RTF export preferences (it has triangles 
and stuff).

Pasting into Word v.X also seems to follow the RTF export prefs, but loses 
the triangles in the process -- instead, I get just a double-quote mark in 
the AppleGothic font.

Anyway, I don't care as much about TextEdit or Word right now, because 
they aren't in this workflow that I've built.

My idea for how to work with this:

-	make the cut/copy action exactly mimic the output of the current 
text/RTF export settings, as it seemed to do before in OO 1.1

-	allow multiple saved sets of export prefs for text and RTF

-	include a saved set for text and RTF that does what OO 1.1 did (which 
was simpler for exports)

-	include a saved set for text and RTF that does what OO 1.2, because 
obviously this is desired by some

-	let the user save sets of export settings, appropriate for different 
jobs

-	let the user choose the saved set for text/RTF exports in the export 
dialog

-	allow the saved set configuration to be called when AppleScripting a 
"export as" or cut/copy action, so that AppleScripters can precisely 
define how they want the data exported

-	allow on-demand change of the text/RTF settings when doing an 
AppleScripted "export as" or cut/copy action, so that a saved set does not 
have to be present (which helps when distributing scripts to others)


Thanks!

For now, I think I'll be reverting back to OO 1.1 because it was simpler 
for my work.


--
Jeremy Reichman