[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OFFICE-3271) rfc-language attributes
[ https://issues.oasis-open.org/browse/OFFICE-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=70655#comment-70655 ]
Patrick Durusau commented on OFFICE-3271:
-----------------------------------------
My research summary on the text of ODF 1.2 on these attributes:
The attributes: number:rfc-language-tag, style:rfc-language-tag, table:rfc-language-tag, style:rfc-language-tag-asian, style:rfc-langauge-tag-complex, all share the same data type: language, 18.3.16.
These attributes are used in cases where:
number:language, number:script and number:country or
fo:language, fo:script and fo:country or
table:language, table:script and table:country or
style:language-asian, style:script-asian and style:country-asian or
style:language-complex, style:script-complex and style:country-complex, in combination are insufficient to designate a language.
Then use attribute (listed below). If attribute not supported, use implementation dependent values for the attribute combinations listed above.
All of the language combination attributes share common datatypes as follows:
number:language, fo:language, table:language, style:language-asian, style:language-complex - all share the datatype: 18.3.17
number:script, fo:script, table:script, style:script-asian, style-script-complex - all share the datatype: 18.3.29
number:country, fo:country, table:country, style:country-asian, style:country-complex - all share the datatype: 18.3.11
Text from ODF 1.2:
****19.356 number:rfc-language-tag
The number:rfc-language-tag attribute specifies a language identifier according to the rules of [RFC5646], or its successors.
It shall only be used if its value can not be expressed as a valid combination of the number:language, number:script and number:country attributes.
Producers may add support for consumers that don't support the number:rfc-language-tag attribute by specifying number:language, number:script and number:country attributes with values as close as possible to the actual value of the number:rfc-language-tag attribute. Producers shall not use values for these attributes that contradict the value of the table:rfc-language-tag attribute.
[data type language, 18.3.16]
Â
****19.512 style:rfc-language-tag
The style:rfc-language-tag attribute specifies a language identifier according to the rules of [RFC5646], or its successors.
It shall only be used if its value can not be expressed as a valid combination of the fo:language, fo:script and fo:country attributes.
Producers may add support for consumers that don't support the style:rfc-language-tag attribute by specifying fo:language, fo:script and fo:country attributes with values that are implementation-dependent.
[data type language, 18.3.16]
Â
****19.703 table:rfc-language-tag
The table:rfc-language-tag attribute specifies a language identifier according to the rules of [RFC5646], or its successors.
It shall only be used if its value can not be expressed as a valid combination of the table:language, table:script and table:country attributes.
Producers may add support for consumers that don't support the table:rfc-language-tag attribute by specifying table:language, table:script and table:country attributes with values that are implementation-dependent.
The table:rfc-language-tag attribute augments the table:language, table:script and table:country attributes. It shall only be used if its value could not be expressed as a valid combination of those. The value shall be a language identifier according to the rules of [RFC5646], or its successors. If a fall-back is provided for consumers that do not support the table:rfc-language-tag attribute, producers should add table:language, table:script and table:country attributes whose values are as close as possible to the value of the table:rfc-language-tag attribute. Producers shall not use values for these attributes that contradict the value of the table:rfc-language-tag attribute.
[data type language, 18.3.16]
Â
****20.335 style:rfc-language-tag
The style:rfc-language-tag attribute specifies a language identifier according to the rules of [RFC5646], or its successors.
It shall only be used if its value can not be expressed as a valid combination of the fo:language, fo:script and fo:country attributes.
Producers may add support for consumers that don't support the style:rfc-language-tag attribute by specifying fo:language, fo:script and fo:country attributes with values that are implementation-dependent.
The attribute is evaluated for any [UNICODE] characters that are not of type asian or complex. 20.348
[data type language, 18.3.16]
Â
****20.336 style:rfc-language-tag-asian
The style:rfc-language-tag-asian attribute specifies a language identifier according to the rules of [RFC5646], or its successors.
It shall only be used if its value can not be expressed as a valid combination of the style:language-asian, style:script-asian and style:country-asian attributes.
Producers may add support for consumers that don't support the style:rfc-language-tag-asian attribute by specifying style:language-asian, style:script-asian and style:country-asian attributes with values that are implementation-dependent.
This attribute is evaluated for [UNICODE] characters that are of type asian. 20.348.
[data type language, 18.3.16]
Â
****20.337 style:rfc-language-tag-complex
The style:rfc-language-tag-complex attribute specifies a language identifier according to the rules of [RFC5646], or its successors.
It shall only be used if its value can not be expressed as a valid combination of the style:language-complex, style:script-complex and style:country-complex attributes.
Producers may add support for consumers that don't support the style:rfc-language-tag-complex attribute by specifying style:language-complex, style:script-complex and style:country-complex attributes with values that are implementation-dependent.
This attribute is evaluated for [UNICODE] characters that are of type complex.. [note typo]
[data type language, 18.3.16]
> rfc-language attributes
> -----------------------
>
> Key: OFFICE-3271
> URL: https://issues.oasis-open.org/browse/OFFICE-3271
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Improvement
> Components: Locale, Part 1 (Schema), Public Review
> Affects Versions: ODF 1.3
> Reporter: Patrick Durusau
> Assignee: Patrick Durusau
> Priority: Critical
> Fix For: ODF 1.3
>
>
> The current rfc-language attributes, number:rfc-language-tag, style:rfc-language-tag, table:rfc-language-tag, style:rfc-language-tag-asian, style:rfc-langauge-tag-complex, need to be re-cast into a single mechanism for specifying languages.
> This should be part of a general consolidation and cleansing of the style mechanism, if some version of CSS or FO isn't faithfully profiled as a style mechanism. My preference would be to simply use an *accurate* profile of FO.
--
This message was sent by Atlassian JIRA
(v7.7.2#77003)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]