[odf-discuss] .ott file format

Damon Anderson damon at corigo.com
Wed Feb 21 09:22:49 EST 2007


Daniel,

A technical question about ODF. How does the specification define the  
transition between ASCII, extended, ASCII, and UTF-16HEX. I see OOo making  
mistakes for example where they convert the ampersand (&) to HTML (&)  
rather than UTF-16HEX, that can't be allowed in the ODF spec surely?

- English is a Germanic derived language filled with romance... but ASCII  
is the greatest current limitation in finding a common format for all the  
world's computer users to communicate with. *** BAN ASCII ***

-Damon

On Wed, 21 Feb 2007 20:54:00 +0700, Daniel Carrera  
<daniel.carrera at zmsl.com> wrote:

> On Wed, 2007-21-02 at 20:51 +0700, Damon Anderson wrote:
>> Actually the most important point you made was the dependence on the
>> extension as in Windows. I have to use MS so often that I forget that  
>> many
>> of it's quirks are un-necessary.
>
> The difference is a bit more than the file extension. The file has a
> different mimetype.
>
> -- English is essentially a West Germanic language that's trying very
> hard to look like a Romance one.



-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/



More information about the odf-discuss mailing list