[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (OFFICE-1895) RIGHTB and friendsis incompletely specified
[ http://tools.oasis-open.org/issues/browse/OFFICE-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622#action_15622 ]
Dennis Hamilton commented on OFFICE-1895:
-----------------------------------------
NEEDS-DISCUSSION
I think we need to work on the levels of abstraction here, even if there are implementation defined.
For example,
I can see both CHAR(codepoint) and CHAR(codepoint, codespace) where codepoint is always an integer-castable value and code is some agreed way (either a string or a number, maybe rules for both) of specifying the codespace.
Likewise, CODE(char) and CODE(char, codespace) where char is castable to a text string of one character (or none) and codespace is as above.
In the absence of codespace, the mapping is implementation defined.
There might be a way to set a global codespace (and it might be a hosting parameter), and that might be specifiable in a document at some level of granularity, but I think the second doesn't have to be handled in the OpenFormula specification itself.
Conceptually, this is extendable to functions like RIGHT(B), MIDDLE, LEFT, etc.
EDGE CASE: There is a problem in byte-oriented (I would say octet but that is because it has been the standard nomenclature for a very long time) cases because if we are extracting from a charset (not a codespace), we have the problem of there not being a proper representation. (E.g., if I extract the second frame of a surrogate pair, or one or more follower bytes of UTF-8 or Shift-JIS.)
EDGE CASE: There is also a problem because in terms of the reference code space of XML, there are certain code points which are prohibited. This means there has to be an escape convention beyond the convention of XML (character entities) in order to be able to express such a char or string value in the XML document in which a cell value is represented for interchange.
Finding and specifying a proper layering of the relevant abstractions should allow us to navigate this morass.
> RIGHTB and friends is incompletely specified
> --------------------------------------------
>
> Key: OFFICE-1895
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-1895
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: OpenFormula
> Affects Versions: ODF 1.2
> Reporter: Andreas Guelzow
> Assignee: Eric Patterson
> Fix For: ODF 1.2
>
>
> 6.6.6 RIGHTB
> Summary: Return a selected number of text characters from the right, using byte position.
> This description fails to indicate what happens in the likely situation that the selected bytes do not form a complete character sequence. Should that be an error or move to a correct position?
> Similarly for the otehr ...B functions
--
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]