After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 163438 - Get better font metrics for var width value formats (General and '*')
Get better font metrics for var width value formats (General and '*')
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Main System
git master
Other All
: Normal enhancement
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2005-01-09 10:40 UTC by Alberto Maria
Modified: 2007-02-24 01:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
a snapshot taken from Excel (56.14 KB, image/jpeg)
2005-01-13 22:30 UTC, Alberto Maria
Details

Description Alberto Maria 2005-01-09 10:40:55 UTC
Asterisc symbol behaviour in:  Format - cells - number - (Custom)
Usually in Excel the use of * stays to repeat an fill the cell with the symbol
followed by.
In accountancy it is used to maintain alligned on the left the symbol of the
local Value symbol (e.g. $, €, £...) while on right there is the number entered.

This happens if you import an xls file where there are numbers with accounting
format: the numbers loose their format, or at least they are not represented as
if they were in Excel.
Thanks
Regards
Alberto Maria
Comment 1 Andreas J. Guelzow 2005-01-09 20:30:42 UTC
I guess this is really an enhancement request. `*' doesn't mean anything special
in gnumeric's formats.
Comment 2 Jody Goldberg 2005-01-13 03:34:30 UTC
We have basic support in place for this with known limitations.  Please supply a
sample format string that is not working as expected.
Comment 3 Alberto Maria 2005-01-13 22:30:59 UTC
Created attachment 35983 [details]
a snapshot taken from Excel

Thanks for Your great work! - Regards Alberto
Comment 4 Jody Goldberg 2005-01-14 06:10:12 UTC
Ahh, I see the problem.  Things are partially fixed, but the bogus font
measurement is way off.  We'll need to do this properly.

The rest is likely to be a 1.6 level change.
Comment 5 Morten Welinder 2007-02-24 01:48:14 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.