Summary: | FORMATTING fractions displayed misleading and calculated wrong | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Horst <homaka> |
Component: | Spreadsheet | Assignee: | Noel Power <nopower> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | rb.henschel |
Version: | 3.6.2.2 release | ||
Hardware: | Other | ||
OS: | All | ||
See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=38097 | ||
Whiteboard: | target:4.0.0 target:3.6.5 | ||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 44446 | ||
Attachments: |
TFRACXLS.XLSX
TFRACXLS.XLSX |
Description
Horst
2012-10-19 21:35:17 UTC
Created attachment 68818 [details]
TFRACXLS.XLSX
There are two issues: 1. Wrong display 2. Lost fixed denominator in format I have written bug 56419 for the lost format. So this issue can cover the problem with the wrong display. Issue 38097 and issue 31449 seem different to me, because they are about formatting via style and here direct formatting is used. I'll have a crack at making the format force the denominator (In reply to comment #3) > I'll have a crack at making the format force the denominator ? This issue is about the missing space between integer part and fraction. (In reply to comment #4) > (In reply to comment #3) > > I'll have a crack at making the format force the denominator > > ? This issue is about the missing space between integer part and fraction. Format should be ?/8 25/8 or (3 1/8) since ?/? does ( and has always in both excel and calc ) display 22/7 it seems to me that modifying the current display '31/8' by adding some space in order to get to a result like '3 1/8' isn't the right thing to do. For me it seems we should aim to have the resultant display be '25/8' to be consistent ( and also to make importing from xlsx easier ) That's what I mean by 'making the format force the denominator' That makes sense I hope Yes it is clear now. Format code "# ?/8" should result in "3 1/8" display. Format code "?/8" should result in "25/8" display. (In reply to comment #6) > Yes it is clear now. > Format code "# ?/8" should result in "3 1/8" display. > Format code "?/8" should result in "25/8" display. (In reply to comment #6) > Yes it is clear now. > Format code "# ?/8" should result in "3 1/8" display. > Format code "?/8" should result in "25/8" display. great, I am not very familiar with all those format possibilities and I just talked to Eike and he agrees with the above too, I will take bug Noel Power committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=0cd1ae1f9b85261e6915471938c5f6c3e0ec9283 don't always show integer part for fraction formats with hard denom fdo#56205 The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Noel Power committed a patch related to this issue. It has been pushed to "libreoffice-3-6": http://cgit.freedesktop.org/libreoffice/core/commit/?id=4e57d13eca14fb4b0dd2c5a27eba1647b207b0d2&g=libreoffice-3-6 don't always show integer part for fraction formats with hard denom fdo#56205 It will be available in LibreOffice 3.6.5. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. Works fine in Version 3.6.5.0+ (Build ID: 95637e2). And fixed another bug (not reported). Inputline shows now correctly the decimal representation of the fraction, before we had the entered string. Good job guys:)) marking as fixed (In reply to comment #10) > Inputline shows now correctly the decimal representation of > the fraction, before we had the entered string. Good job guys:)) that sounded sortof familiar :-) took me a while to recall but actually I believe this is the same as what was reported in bug #55875 ( there was a separate fix for that ) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.