[OASIS Issue Tracker] (OFFICE-3271) rfc-language attributes

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Patrick Durusau updated OFFICE-3271:
------------------------------------
    Proposal: 
Consolidate number:rfc-language-tag, style:rfc-language-tag, table:rfc-language-tag, style:rfc-language-tag-asian, style:rfc-langauge-tag-complex into style:rfc-language, datatype 18.3.16.

Consolidate: number:language, fo:language, table:language, style:language-asian, style:language-complex into fo:language, datatype 18.3.17

Consolidate: number:script, fo:script, table:script, style:script-asian, style-script-complex into fo:script, datatype 18.3.29

Consolidate: number:country, fo:country, table:country, style:country-asian, style:country-complex into fo:country, datatype 18.3.11.

Update language and references as appropriate.

(I pasted in as a comment, a summary of the relevant attributes, their datatypes and the text from ODF 1.2 for your convenience.)

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