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] Updated: (OFFICE-2950) 19.364number:transliteration-format - "...which number characters to use." ???For what? (I know the answer, I think, but we don't say here.)



     [ http://tools.oasis-open.org/issues/browse/OFFICE-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Durusau updated OFFICE-2950:
------------------------------------

    Issue Type: Bug  (was: Improvement)

> 19.364 number:transliteration-format - "...which number characters to use." ??? For what? (I know the answer, I think, but we don't say here.) 
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: OFFICE-2950
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2950
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>    Affects Versions: ODF 1.2 Part 1 CD 5
>            Reporter: Patrick Durusau
>             Fix For: ODF 1.2 Part 1 CD 5
>
>
> 19.364 number:transliteration-format - "...which number characters to use." ??? For what? (I know the answer, I think, but we don't say here.)
> Now reads: "The number:transliteration-format attribute specifies which number characters to use."
> This is a case where I would concede the recasting of the text lost information but some critical bits were missing even in the 1.0 text.
> Which read:
> *****
> 14.7.10
> The various number:transliteration-* attributes specify the native number system of the
> style to display the number using, for example, CJK number characters. The notation is inspired
> by the W3C XSLT 2.0 draft, see ยง12.3 of [XSLT2]. However, to be able to fully distinguish
> between all possible native number systems additional attributes are needed in combination. For
> example, Korean uses 11 different systems where the digits are not always different but short and
> long and formal and informal forms exist.
> *****
> Then,
> *****
> Transliteration Format
> The number:transliteration-format attribute specifies which number characters to use.
> The value of the attribute is the digit "1" expressed as a native number.
> If no format is specified the default ASCII representation of Arabic digits is used, other
> transliteration attributes present in this case are ignored.
> *******
> Do you see the missing part?
> We never say that the value of the digit "1" expressed as a native number identifies a set of digits in a particular language in the Unicode standard. 
> That is implied but not very well. 
> Plus in its current structure, we need to identify the number:transliteration-* attributes that are to be ignored. 
> Possibly a note on usage of the other attributes? 

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