[ http://tools.oasis-open.org/issues/browse/OFFICE-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19250#action_19250 ]
Eike Rathke commented on OFFICE-2663:
-------------------------------------
I don't think the issue goes away under Unicode. The example of CODE(), as a code page dependent non-interoperable function, may be bad, but the issue still remains with the UNICODE(), LEFT(), MID(), RIGHT() and LEN() functions. There are 4 flavors of normalization defined in the Unicode Standard, NFC, NFD, NFKC, and NFKD, all of which may deliver different results, though practically probably NFC would be used. I think we don't want to impose normalization or decomposition on evaluators, nor do we want to define normalization for the CONCATENATE() function and the infix operator "&".
The conclusion is that we can define a character in a position dependent context only as the Unicode code point scalar value.
How to express?
> Public Comment: What is a 'character'? (ODF 1.2, Part 2)
> ---------------------------------------------------------
>
> Key: OFFICE-2663
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-2663
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: OpenFormula
> Reporter: Robert Weir
> Priority: Blocker
>
> Copied from office-comment list
> Original author: Alex Brown <>
> Original date: 24 Apr 2010 08:18:59 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/201004/msg00004.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
