OPML and ASCII chars problems

[Brian C.]

It's unfortunate that Radio doesn't support UTF-8; we chose it for our 
output encoding because the XML spec states that you're supposed to 
support that format and UTF-16 at a bare minimum to be valid. We just 
assumed that Radio supported UTF-8. We'll probably add an encoding 
pop-up in a future version to work around this problem, but it'll have 
to be after 2.1.1 final - that code has been finalized.

    If you have any other questions or suggestions, please don't 
hesitate to contact me. When replying, please include the quoted text 
of this message. We really appreciate your help!

Sincerely,

Brian C.
Support Manager
Omni Group

On Thursday, November 14, 2002, at 12:01  PM, 
omnioutliner-users-request at omnigroup.com wrote:

> From: bertisonline at mac.com
> To: omnioutliner-users at omnigroup.com
>
> ------ Forwarded Message
> From: Marc Barrot <mbarrot at dig.fr>
> Date: Wed, 13 Nov 2002 09:26:00 -0500
> To: <radio-dev at yahoogroups.com>
> Cc: <omnioutliner-users-request at omnigroup.com>, <bertisonline at mac.com>
> Subject: Re: OPML and ASCII chars problems
>
>> From this point on, the shocking upper case title should be gone :-)
>
> I'm cross posting this message to Bertrand and to
> omnioutliner-users-request at omnigroup.com, as Bertrand did in his
> original
> message.
>
> Emmanuel. M. Decarie wrote:
>> And last but not least, if the OPML spec doesn't seems to specify an
>> encoding <http://www.opml.org/spec>, UserLand still specify that they
>> will use only ISO-8859-1 for storage.
>> So my guess is that if you change in Omni Outliner the xml encoding
>> to ISO-8859-1, everything should be fine (but I don't have Omni
>> Outliner to test this assumption).
>
> Thanks for the clarification Emmanuel.
>
> Since the latest version of OmniOutliner is still in a beta phase -
> 2.1.1
> beta 2 (v44) - I would recommend that the next release of OmniOutliner
> include an OPML export tab in the Preferences, similar to the text
> export
> and RTF export tabs, where the user would specify the default encoding
> for
> the exported outline's content.
>
> This way, the OmniGroup can still support UTF-8 if they feel like it,
> and
> keep compatibility with previous beta versions, while offering better
> compatibility with UserLand, which for now seems to have the largest
> user
> base for OPML documents. A typical win-win scenario :-)
>
> I've noticed that JOE, a java based open source outliner that uses OPML
> [1],
> allows almost a dozen encoding standards in its save and open dialogs.
>
> Cheers
>
> Marc
>
> 1: http://outliner.sourceforge.net/
>
> PS: Emmanuel, the actual url for activeRenderer is
>
> http://radio.weblogs.com/0104487/outlines/aR/activeRenderer.html
>
> Do familiarize yourself with it :-)
>
>
>
> ------ End of Forwarded Message
>
>
> --__--__--
>
>
>
> Subject: Re: OPML and ASCII chars problems
> Cc: omnioutliner-users at omnigroup.com
> To: bertisonline at mac.com
> From: "Bruce D'Arcus" <bdarcus at fastmail.fm>
>
>
> On Thursday, November 14, 2002, at 05:41 AM, bertisonline at mac.com 
> wrote:
>
>> This way, the OmniGroup can still support UTF-8 if they feel like it,
>> and
>> keep compatibility with previous beta versions, while offering better
>> compatibility with UserLand, which for now seems to have the largest
>> user
>> base for OPML documents. A typical win-win scenario :-)
>
> Here's another thought: why not tell the developers of Userland to
> support unicode?
>
> I'm not being snide here, and do believe Omni might add this option,
> but just pointing out the problem here from my perspective is Userland;
> not OO.
>
> Bruce
>
>
>
> --__--__--
>
> _______________________________________________
> OmniOutliner-Users mailing list
> OmniOutliner-Users at omnigroup.com
> http://www.omnigroup.com/mailman/listinfo/omnioutliner-users
>
>
> End of OmniOutliner-Users Digest