OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (OFFICE-2769) Needs-discussion:6.19.2 ARABIC function and Turkish "i"s



    [ http://tools.oasis-open.org/issues/browse/OFFICE-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19489#action_19489 ] 

Dennis Hamilton commented on OFFICE-2769:
-----------------------------------------

[From David LeBlanc <http://lists.oasis-open.org/archives/office/201006/msg00255.html> who still seems unable to comment on JIRA, Mon, 28 Jun 2010 22:34:58 -0700 ]

"""
As far as I can tell, there is no analogue to that function in Excel, so this is purely my $0.02, but any time you're dealing with character conversion, you have to consider locale.

Just looking at the first few pages of the Unicode character set, there are a large number of different 'I' characters. Some of them even repeat - for example, 0x03AA and 0x00CF are both 'I' with a diaeresis.

I don't have a link to the story, but not considering locale in text messages got someone killed in Turkey. One of a pair of squabbling lovers sent the other a text message, it didn't have the correct 'I', which changed the meaning to something seriously insulting, things got physical, and one ended up dead.

IMHO, if you're converting to and from Roman numerals, then the definition of Roman numerals that I'm aware of involved the Latin characters I, X, V, M, D, and C (and you sometimes see these in lowercase). If I were writing a parser to convert those, I'd consider anything else an error, or a non-number.
"""

[From Andreas Guelzow, on the list, <http://lists.oasis-open.org/archives/office/201006/msg00256.html>,
Tue, 29 Jun 2010 00:30:09 -0600 ]

"""
On Mon, 2010-06-28 at 23:34 -0600, David LeBlanc wrote:
> As far as I can tell, there is no analogue to that function in Excel,
> so this is purely my $0.02, but any time you're dealing with character
> conversion, you have to consider locale.

This issue has nothing to do with character conversion, and as far as
OpenFormula is concerned we should not consider locale. 

> IMHO, if you're converting to and from Roman numerals, then the
> definition of Roman numerals that I'm aware of involved the Latin
> characters I, X, V, M, D, and C (and you sometimes see these in
> lowercase). If I were writing a parser to convert those, I'd consider
> anything else an error, or a non-number.

I would agree with this!

Andreas
"""

> Needs-discussion: 6.19.2 ARABIC function and Turkish "i"s
> ---------------------------------------------------------
>
>                 Key: OFFICE-2769
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2769
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: OpenFormula
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Eric Patterson
>
> In Turkish Locales, there are dotted and undotted versions of upper and lowercase "i"s.  Should the Arabic function accept all 4 types as inputs for conversion to Roman numerals?

-- 
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]