office message

Subject: [OASIS Issue Tracker] (OFFICE-4056) CLONE - was Office-3695 - <number:fraction> appears as new element (incorrectly)

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: office@lists.oasis-open.org
Date: Tue, 28 Jan 2020 20:40:00 +0000 (UTC)

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

Patrick Durusau updated OFFICE-4056:
------------------------------------
    Affects Version/s: ODF 1.3

> CLONE - was Office-3695 - <number:fraction> appears as new element (incorrectly)
> --------------------------------------------------------------------------------
>
>                 Key: OFFICE-4056
>                 URL: https://issues.oasis-open.org/browse/OFFICE-4056
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: New Feature
>          Components: Formatting Properties, Part 1 (Schema)
>    Affects Versions: ODF 1.3
>            Reporter: Andreas Guelzow
>            Assignee: Andreas Guelzow
>            Priority: Major
>             Fix For: ODF 1.3 Errata
>
>
> In ODF 1.2 the <number:fraction> element has the attribute number:denominator-
> value. If this attribute is not present, a denominator that is appropriate for
> displaying the number is used. Clearly what is considered appropriate will be implementation dependent/defined. For example LibreOffice considers the appropriate denominator for of:=PI() to be 7 although a denominator of 113 would create a much closer approximation. From a user perspective if formatting a number as a fraction usually the size of the denominator is important even if the exact chosen denominator does not matter. Some implementations, for example Gnumeric, permit the user to determine a maximum number of digits to be used in the choice of the denominator. Currently Gnumeric stores that information in a foreign element: gnm:max-denominator-digits. In the interest of interoperability it would be desirable to include a similar attribute in the ODF1.3 standard.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)