Bug 126824 - Most strings in Calc Data Provider shown in English
Summary: Most strings in Calc Data Provider shown in English
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.1.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Data-Provider
  Show dependency treegraph
 
Reported: 2019-08-11 15:13 UTC by milupo
Modified: 2023-03-26 03:23 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot untranslated Data Provider (27.90 KB, image/png)
2019-08-11 15:13 UTC, milupo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description milupo 2019-08-11 15:13:45 UTC
Created attachment 153294 [details]
Screenshot untranslated Data Provider

Hi,

most strings of Data Provider in Tools --> Data Provider... are shown in English. Tested with Upper Sorbian, Lower Sorbian, German, and Czech locales. I attached a screenshot of Upper Sorbian (hsb) Data Provider: Daty --> Poskićowar datow...

Expected:

Strings should be shown translated.

Thanks.
Comment 1 milupo 2019-08-11 16:17:36 UTC
It's in Data --> Data Provider, not in Tools --> Data Provider, of course. Sorry for that.
Comment 2 Jean-Baptiste Faure 2019-08-11 19:40:24 UTC
Confirmed in LO 6.3.1.0+ with French localization. As French translation of the UI is complete according to Pootle, it seems that some strings have not been tagged as translatable.

Same problem in LO 6.1.4 and 6.2.5.

Setting status to NEW.

Best regards. JBF
Comment 3 Julien Nabet 2019-08-12 15:27:04 UTC
Code pointer:
https://opengrok.libreoffice.org/xref/core/sc/source/ui/miscdlgs/dataproviderdlg.cxx?r=b8a0f8c6#195

Manuj: noticing your commits on this part, thought you might be interested in making the items translatable.
Comment 4 QA Administrators 2023-03-26 03:23:27 UTC
Dear milupo,

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