Thank you for the report.
Yes, they should use the same string that is already used in the tabs.

Reproduced French UI in:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 1b463f697405e64a03378fb38a32172c4d3c25e6
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: fr-FR
Calc: threaded

Bibisected with linux-64-6.2 repository to first bad commit 5f599610abef8efb0c0bca0593fcef941fbe2ebc which points to the fix for bug 67248 and bug 119956:

commit a9ec212c1b545d745285f0ab3119a80713b1d1f2
author	Regina Henschel <rb.henschel@t-online.de>	Fri Sep 14 18:56:23 2018 +0200
committer	Regina Henschel <rb.henschel@t-online.de>	Fri Sep 21 11:32:34 2018 +0200
tdf#67248 Use localized layer name only for display in UI
Reviewed-on: https://gerrit.libreoffice.org/60507

Regina, what are your thoughts? The greyed-out name in the dialog does look like a bug currently, and should display the localised name in my opinion. We can use the UI name there while still disallowing the use of the internal name when the field is editable.

In addition, instead of the error message string:
"The name chosen already exists."
We could use the more transparent:
"This name can't be used: it is either reserved or the name of another layer."

(In reply to Stéphane Guillou (stragu) from comment #2)
> Regina, what are your thoughts? The greyed-out name in the dialog does look
> like a bug currently, and should display the localised name in my opinion.
> We can use the UI name there while still disallowing the use of the internal
> name when the field is editable.

I don't know, whether it is possible to use the UI name in the field. On the other hand you now see, which terms are internally actually used and therefore forbidden for own layers. So for me it is not a bug to show the internal names.

> 
> In addition, instead of the error message string:
> "The name chosen already exists."
> We could use the more transparent:
> "This name can't be used: it is either reserved or the name of another
> layer."

That is possible. You need to create a new STR_WARN_LAYER_NAME_DUPLICATE because the current STR_WARN_NAME_DUPLICATE is also used for line ends.

Dear lol,

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