Ver 3 OPML change breaks XML parsing

[Timothy J.Wood]

   You can get UTF-8 output by selecting it in the "Text" preferences 
pane.  There is finer-grain control of this via some user defaults that 
aren't currently exported in the UI:

OOPlainTextStringEncoding
OOOPMLStringEncoding
OOMOREStringEncoding
OODefaultStringEncoding
OOStringsStringEncoding

   So, if you always want UTF-8 for OPML, you can do the following in 
Terminal

	defaults write com.omnigroup.OmniOutlinerPro3 OOOPMLStringEncoding 
"iana UTF-8"

   Adding better support for export options is high on our to-do list.

-tim



On Jan 7, 2005, at 3:51 PM, Robin Trew wrote:

> In Ver3, a small change in the OPML export format has broken XML 
> parsing by standard software.
>
> Ver 2 used
> 	encoding="UTF-8"
>
> in the first line of its OPML files, and this was happily processed by 
> XML parsers like expat (try the Realbasic implementation for example).
>
> the new use of
>
> 	encoding="MACINTOSH"
>
> in Ver 3
>
> triggers an error and actually prevents parsing by standard XML 
> software.
>
> Could you revert to the use of an XML - compliant symbol at this point 
> ?
>
> Thanks !
>
> RT
>
> _______________________________________________
> OmniOutliner-Users mailing list
> OmniOutliner-Users at omnigroup.com
> http://www.omnigroup.com/mailman/listinfo/omnioutliner-users
>