Download it now!
Bug 123739 - Regression - scientific notation now where numbers were shown before - cell padding now requires 1 digit of free space before and after a number, or the cell goes in scientific notation
Summary: Regression - scientific notation now where numbers were shown before - cell p...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.6.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Cell-Management
  Show dependency treegraph
 
Reported: 2019-02-27 13:29 UTC by icerabbit
Modified: 2019-10-03 03:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
cells with 6 digits go into scientific notation (12.30 KB, image/png)
2019-02-27 13:31 UTC, icerabbit
Details
bypass the problem with even smaller font showing how much space is required and wasted by padding (11.91 KB, image/png)
2019-02-27 13:33 UTC, icerabbit
Details

Note You need to log in before you can comment on or make changes to this bug.
Description icerabbit 2019-02-27 13:29:44 UTC
Description:
Case: Large and important Calc file going back 10 years, that was carefully laid out and setup, back in LO 3.x, updated fine through the years, using exact size width columns and Arial 6 to input about 36 columns and 44 rows, perfectly rendered on screen. 

Computer nor display have changed since OS X 10.12. 

Updated to LO 546 last year, and all of sudden I have lots of number cells with 2E+05 3E+05 etc 

Again, nothing changed to the computer setup, file, data, cell formatting, ... only LO updated. 

Upon investigation it seems that 1 digit's worth of free space is now required in front and behind the actual number, or LO Calc goes all 2E+05 3E+05 

Totally ineffective and unbelievable. The numbers fit just fine. Where is programmed padding requirement suddenly coming from, that I now have to reduce the formatting to Arial Narrow 5pt ?! 

Steps to Reproduce:
1. Open file created back in 3.x 4.x with 0.30" columns and font type Arial 6pt or 5pt, add numbers with 6 digits 
2. 
3.

Actual Results:
Six digits numbers are all rendered as 2E+05 3E+06 etc 

Expected Results:
Render the numbers legibly as old fashioned numbers on screen 


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
I don't know when this exactly came about. I use this important file intermittently. For at least 8 years. Once in a while I would get a ### on screen and the easy fix was to drop that cell from Arial 6 to Arial 5 and it would show the number again.

Having to use Arial 5 Narrow is painful to the eyes ...

And if I could, I would add screenshots that clearly show it is not required to go 5pt font because one could fit an 8 digit number in the box now !!! 

Please fix it by lowering the padding requirement to what it was. 

Please fix also drop the scientific notation method. It is undesirable to me. #### stands out visually. 2E+05 does not. 

I can be reached as icerabbitje@gmail.com 


---------//// OPEN GL REPORT //// ----------
Renderer: Intel HD Graphics 4000 OpenGL Engine
Vendor: Intel Inc.
Memory: 1536 MB
Version: 4.1 INTEL-10.25.17
Device: Macmini6,2
Shading language version: 4.10


Max texture size: 16384 x 16384
Max vertex texture image units: 16
Max texture image units: 16
Max geometry texture units: 16
Max anisotropic filtering value: 16
Max viewport size: 16384 x 16384
Max Clip Distances: 8
Max samples: 8


Extensions: 45


GL_ARB_tessellation_shader
GL_APPLE_texture_range
GL_EXT_framebuffer_multisample_blit_scaled
GL_ARB_viewport_array
GL_ARB_gpu_shader_fp64
GL_ARB_explicit_attrib_location
GL_NV_texture_barrier
GL_ARB_separate_shader_objects
GL_ARB_texture_storage
GL_ARB_gpu_shader5
GL_ARB_texture_swizzle
GL_EXT_texture_compression_s3tc
GL_ARB_texture_cube_map_array
GL_ARB_blend_func_extended
GL_ARB_vertex_attrib_64bit
GL_EXT_texture_sRGB_decode
GL_ARB_texture_gather
GL_EXT_texture_filter_anisotropic
GL_APPLE_row_bytes
GL_ARB_transform_feedback2
GL_ARB_transform_feedback3
GL_ARB_draw_indirect
GL_ARB_texture_query_lod
GL_ARB_draw_buffers_blend
GL_ARB_sample_shading
GL_ARB_internalformat_query
GL_ARB_timer_query
GL_ARB_shader_subroutine
GL_ATI_texture_mirror_once
GL_EXT_debug_marker
GL_APPLE_rgb_422
GL_ARB_vertex_type_2_10_10_10_rev
GL_EXT_debug_label
GL_ARB_texture_buffer_object_rgb32
GL_ARB_instanced_arrays
GL_APPLE_container_object_shareable
GL_ARB_ES2_compatibility
GL_APPLE_client_storage
GL_ARB_sampler_objects
GL_ARB_occlusion_query2
GL_ARB_shading_language_include
GL_ARB_texture_rgb10_a2ui
GL_APPLE_object_purgeable
GL_ARB_shader_bit_encoding
GL_APPLE_flush_render

Core features

v3.0 (100 % - 23/23)
v3.1 (100 % - 8/8)
v3.2 (100 % - 10/10)
v3.3 (100 % - 10/10)
v4.0 (100 % - 14/14)
v4.1 (100 % - 7/7)
v4.2 (15 % - 2/13)
v4.3 (0 % - 0/23)
v4.4 (0 % - 0/10)
v4.5 (0 % - 0/11)
v4.6 (0 % - 0/11)
vARB 2015 (0 % - 0/12)

OpenGL driver version check (Current: 4.1 INTEL-10.25.17, Latest known: ):
Latest version of display drivers found
According the database, you are running the latest display drivers for your video card.

Extension verification:
Comment 1 icerabbit 2019-02-27 13:31:36 UTC
Created attachment 149627 [details]
cells with 6 digits go into scientific notation

screenshots of cells with a 6 digit number, that were shown on screen and printed fine for years, now are unreadable scientific notation
Comment 2 icerabbit 2019-02-27 13:33:36 UTC
Created attachment 149628 [details]
bypass the problem with even smaller font showing how much space is required and wasted by padding

screenshot showing how calc requires me to change the font from Arial to Arial Narrow and down to 5pt ... the 6 digit number is finally shown again, but look at all the wasted padding space ... in the older days that would hold a 7 digit or 8 digit number
Comment 3 V Stuart Foote 2019-02-27 17:53:27 UTC
We're guessing here as we would need your document (anonymize by changing values to "8" s). But IIUC the autoformatting to Scientific notation for "General" numbers has not changed.

Font's change from system to build to system build--Arial on OSX is not Arial on Windows. Also LibreOffices font handling has been changed several times in the interim. There also have been changes to calc for calculating cell height and cell width, as well as adjustments to how "Use printer metrics for text formatting" behaves.

So it would be abnormal to not have some layout changes in the ensuing builds and versions of your document.

So please do this. Make a copy of the document. Then open the copy and select the active cells on the sheet, set your font size back to 6pt--and in the Column label area select one of the grid lines. Open context menu and apply "Optimal Width".

Are the resulting cell widths more acceptable--and does it fit as you'd prefer? Also, does selecting another font format things better than Arial? Perhaps a Monospaced font like Consolas, Liberation Mono, or DejaVu Sans Mono?
Comment 4 QA Administrators 2019-09-02 09:31:01 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2019-10-03 03:02:29 UTC
Dear icerabbit,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp