[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=70658#comment-70658 ] Regina Henschel edited comment on OFFICE-3271 at 8/5/18 8:15 PM: ----------------------------------------------------------------- LibreOffice writes fo:language, fo:country, style:language-asian, style:country-asian, style:language-complex and style:country-complex together into the style:text-properties element of the style:default-style. Therefore for LibreOffice it is not possible to use fo:language instead of style:language-asian or style:language-complex, and it is not possible to use fo:country instead of style:country-asian or style:country-complex. Word 365 too writes these six attributes together in the style:default-style element. was (Author: regina.henschel): LibreOffice writes fo:language, fo:country, style:language-asian, style:country-asian, style:language-complex and style:country-complex together into the style:text-properties element of the style:default-style. Therefore for LibreOffice it is not possible to use fo:language instead of style:language-asian or style:language-complex, and it is not possible to use fo:country instead of style:country-asian or style:country-complex. > 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]