Bug 129826 - Storing language based user defined format codes of cells does not work for color code based entries.
Summary: Storing language based user defined format codes of cells does not work for c...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Number-Format
  Show dependency treegraph
 
Reported: 2020-01-06 07:01 UTC by Ralf Hendel
Modified: 2024-05-01 03:15 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot after editing a user based format (927.79 KB, image/png)
2020-01-06 07:04 UTC, Ralf Hendel
Details
Screenshot after reopening the document (925.71 KB, image/png)
2020-01-06 07:05 UTC, Ralf Hendel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Hendel 2020-01-06 07:01:32 UTC
Description:
When adding a user defined format code for currency formatted fields, it works as long as you don't close the document. After closing and reopening it, the format code value is not contained in the list of available formats and the format value of the field is set back to the last available entry of the list.

This problem only remains if I use color codes like "FARBE01" or "FARBE22" instead of color names (FARBE is the German translation of COLOR). If I use "GREEN" or "GRÜN" (GRÜN ist German translation of GREEN).

I use libre office with English surface but on a German operating system. It works both entering color codes like "FARBE01" as well as "COLOR01". Bu when I enter "COLOR01", store the "Format cell" form and reopen the form, I find it translated to "FARBE01".

This brings me to the idea, that this behavior may have something to do with the translation handling of format codes.

Steps to Reproduce:
1.
Entering a user defined format code for currency formatted cells while using a format code like "FARBE01" or "COLOR01".

2.
Confirming that the cells will be displayed according the format code like expected.

3.
Storing and closing the document.

4.
Reopening the document.

5.
Confirming the unexpected behavior:

5.1.
The concerned cells won't be displayed according the format code like expected.

5.2.
The user-based entry is no longer available in the list for format codes. 

Actual Results:
The concerned cells won't be displayed according the format code like expected.
The user-based entry is no longer available in the list for format codes. 


Expected Results:
Using color format codes like "FARBE01" or "COLOR01" will still work after reopening the document.
User based entries of format codes like "FARBE01" or "COLOR01" will be available even after reopening the document. 


Reproducible: Always


User Profile Reset: No



Additional Info:
I use libre office with English surface but on a German operating system. It works both entering color codes like "FARBE01" as well as "COLOR01". Bu when I enter "COLOR01", store the "Format cell" form and reopen the form, I find it translated to "FARBE01".

This brings me to the idea, that this behavior may have something to do with the translation handling of format codes.
Comment 1 Ralf Hendel 2020-01-06 07:04:06 UTC
Created attachment 156955 [details]
Screenshot after editing a user based format

The functionality works as expected as long as you don't close the document and reopen it.
Comment 2 Ralf Hendel 2020-01-06 07:05:55 UTC
Created attachment 156956 [details]
Screenshot after reopening the document

The bug becomes visible after storing, closing and reopening the document:
The new user-based entry is no longer available in the list for format codes.
Comment 3 m_a_riosv 2020-01-07 22:35:00 UTC
Please detail what file format do you use to save.
Comment 4 Ralf Hendel 2020-01-08 07:26:11 UTC
I use OpenDocument Spreadsheet (.ods).
Thanks for working on this!
Comment 5 QA Administrators 2020-01-09 03:38:25 UTC Comment hidden (obsolete)
Comment 6 Buovjaga 2020-04-30 18:26:27 UTC
Repro, already in 3.3.0 (Win 10)

[FARBE22]"+"#.##0,00 [$€-407];[ROT]-#.##0,00 [$€-407]

Arch Linux 64-bit
Version: 7.0.0.0.alpha0+
Build ID: 623d6cf06ccba392c1993a3b0ad271d508205e73
CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5; 
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Calc: threaded
Built on 29 April 2020
Comment 7 QA Administrators 2022-05-01 03:38:35 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2024-05-01 03:15:01 UTC
Dear Ralf Hendel,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug