[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:comment-tabpanel&focusedCommentId=70659#comment-70659 ] 

Michael Stahl commented on OFFICE-3271:
---------------------------------------

The -asian and -complex attributes go back at least to Microsoft Word, which decided to store all text formatting properties in triplicate, one property for "simple" scripts, one for CJK, and one for "complex" scripts.

I'm afraid any consolidation here is going to cause significant interop issues.

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