Bug 40378 - Defined names are improperly saved as lowercase
Summary: Defined names are improperly saved as lowercase
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Master old -3.6
Hardware: All All
: high major
Assignee: Eike Rathke
URL:
Whiteboard: target:3.5.0 target:3.4.6
Keywords: regression
: 42310 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-08-25 09:35 UTC by James
Modified: 2012-02-08 09:25 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Demonstrate defined name bug (7.10 KB, application/vnd.oasis.opendocument.spreadsheet)
2011-08-25 09:35 UTC, James 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James 2011-08-25 09:35:47 UTC 
Created attachment 50569 [details]
Demonstrate defined name bug

Open the attached spreadsheet. You will see there are two defined names: BonusSTR and HandAttackDC.

BonusSTR is defined to be "(HandAttackDC*5)". You will see, however, that LO has improperly saved the definition as "(handattackdc*5)". In other words, all lower case. Naturally, you will get an error if you use BonusSTR in a formula. If you correct the capitalization of HandAttackDC in the definition of BonusSTR, it will work correctly, and the capitalization will be retained, only in your current session. If you save and quit, HandAttackDC will again incorrectly be lowercase when you reopen the spreadsheet.
Comment 1 Eike Rathke 2011-08-25 15:56:17 UTC 
Working on this. The actual problem is not case sensitivity but the order in which defined names are encountered during import. BonusSTR needs HandAttackDC that is not present yet, hence it works when changing anything in the definition of BonusSTR later as it is recompiled then.
Comment 3 GerardF 2011-09-04 10:45:03 UTC 
*** Bug 40590 has been marked as a duplicate of this bug. ***
Comment 4 GerardF 2011-10-27 08:20:37 UTC 
*** Bug 42310 has been marked as a duplicate of this bug. ***