Subject: RE: [office-formula] Re: (fwd) Should OpenFormula BASE() and DECIMAL() definitionslist character set?
I'm assuming you mean the character encoding expressed at the XML level, such as: <?xml version="1.0" encoding="ISO-8859-1"?> Do we need to say anything more here than what the XML Recommendation says? What else would you have? Restrict encoding to an enumerated subset of encodings? In any case, I think things are cleaner if we keep OpenFormula independent of XML, since there is not necessary connection to markup at all, if we partition this right. OpenFormula should define conformance for two things: 1) The syntax of a conforming OpenFormula expression, which would be expressed as BNF and other constraints on a Unicode string 2) Constraints on the values returned by a conforming OpenFormula expression -Rob "Dennis E. Hamilton" <email@example.com> wrote on 05/06/2009 03:38:32 PM: > > Subject: > > RE: [office-formula] Re: (fwd) Should OpenFormula BASE() and DECIMAL > () definitions list character set? > > Does there need to be something said about what happens when the content.xml > (or any other XML file) uses an encoding other than one for Unicode? My > understanding is that other encodings are referenced to Unicode in and out, > but not sure whether this has been clarified anywhere in ODF specifications > nor in OpenFormula, where the ability to correctly interpret and to preserve > on export may be impaired (though hopefully not for any of the printable > Basic Latin characters of Unicode). > > - Dennis > > -----Original Message----- > From: firstname.lastname@example.org [mailto:email@example.com] > Sent: Wednesday, May 06, 2009 11:34 > To: David A. Wheeler; Eike Rathke; Michael Brauer; OASIS ODFF SC; > firstname.lastname@example.org > Subject: [office-formula] Re: (fwd) Should OpenFormula BASE() and DECIMAL() > definitions list character set? > > I checked with our local Unicode guru, to make sure we were expressing > this right. He confirmed that it is correct to refer to the "value space" > as Unicode "characters" and "strings", and the serialized versions as > "encoded characters". > > [ ... ] >