Bug 101769 - LibreOffice Calc does not save language style of xslx file
Summary: LibreOffice Calc does not save language style of xslx file
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:xls, filter:xlsx
Depends on:
Blocks: Spell-Checking
  Show dependency treegraph
 
Reported: 2016-08-28 19:16 UTC by Hector Espinoza
Modified: 2025-05-27 03:12 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
xlsx file to test bug (7.09 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2016-08-28 19:19 UTC, Hector Espinoza
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hector Espinoza 2016-08-28 19:16:19 UTC
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0
Build Identifier: LibreOffice 5.0.6.2

This bug is not related with updating the red underline of spell check as reported in other bug.
This is simply that the language of the document is not saved.

Reproducible: Always

Steps to Reproduce:
1.Open an xlsx file.
2.Change the language too a new one: press F11 -> Default > right click > modify > font > choose new language > press OK
3.Save the document
4.Open the document and check the language following step 2, you will find that the new language was not saved.
Actual Results:  
the language is not saved

Expected Results:  
the language should be the one saved before

[Information automatically included from LibreOffice]
Locale: en-US
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes


Reset User Profile?No
Comment 1 Hector Espinoza 2016-08-28 19:19:44 UTC
Created attachment 127059 [details]
xlsx file to test bug
Comment 2 Julien Nabet 2016-08-28 21:06:19 UTC
On pc Debian x86-64 with master sources updated today, I could reproduce this.

I noticed this on console:

warn:vcl:23719:1:vcl/unx/generic/fontmanager/fontconfig.cxx:865: In glyph fallback throwing away the language property of en because the detected script for '0x9f3' is Bengali and that language doesn't make sense. Autodetecting instead.
Comment 3 m_a_riosv 2016-08-28 21:39:22 UTC
Reproducible also.
Win10x64
Version: 5.1.5.2 (x64)
Build ID: 7a864d8825610a8c07cfc3bc01dd4fce6a9447e5
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; 
Locale: es-ES (es_ES); Calc: CL
LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4

I think inherited from OOo, with AOo happens saving as xls. (xlsx it's not possible)
Comment 4 Cor Nouws 2016-08-29 12:29:26 UTC
maybe a stupid question, but does xlsx support that?
I can't find to set the language in Excel anyway..
Comment 5 m_a_riosv 2016-08-29 15:39:13 UTC
Hi Cor, I have not excel to test, but theoretically it should be possible at least for number format. (https://support.office.com/en-us/article/Format-a-date-the-way-you-want-8e10019e-d5d8-47a1-ba95-db95123d273e)
Comment 6 QA Administrators 2017-10-23 13:45:22 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2019-12-03 13:52:18 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2021-12-03 04:20:54 UTC Comment hidden (obsolete)
Comment 9 ady 2023-05-27 14:49:46 UTC
FWIW:

* cell's direct formatting is not the same as modifying the style.

* [CTRL]+[1] > "Numbers" tab has a "Language" selection;

* [CTRL]+[1] > "Font" tab has a "Language" selection.

* Menu Tools > Options > Language Settings > Languages > Formats area has a "Language" selection;

* Menu Tools > Options > Language Settings > Languages > Defaults Languages for Documents area has a "Language" selection.

I am not sure which of all these "Language" selections are actually supported by Excel in its own xls and/or xlsx formats. This should be verified before reporting the fail to save/export any of these attributes from Calc to xls(x).
Comment 10 QA Administrators 2025-05-27 03:12:16 UTC
Dear Hector Espinoza,

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