Bug 126703 - Dialog theming/UX - Language
Summary: Dialog theming/UX - Language
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: iOS Editor (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other iOS
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-05 09:51 UTC by Andreas Gruhler
Modified: 2021-02-09 12:45 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
The language of the dialog labels and buttons is different from the language in the menu bar (883.38 KB, image/png)
2019-08-05 09:52 UTC, Andreas Gruhler 		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 Andreas Gruhler 2019-08-05 09:51:56 UTC 
Description:
The language of the dialog box is different from the language in the menu bar.
Please find a screenshot attached that shows the difference.
Ideally, the language of the iOS settings is detected and used across all labels.

Steps to Reproduce:
1. Open "Paragraph Style" dialog on an iPad where "Language & Region" is set to German

Actual Results:
1. The dialog contains English labels/buttons, see screenshot attached

Expected Results:
1. The dialog should present all labels in the correct language (German in this case)


Reproducible: Always


User Profile Reset: No



Additional Info:
Collabora iOS Version: 4.1.48
Comment 1 Andreas Gruhler 2019-08-05 09:52:36 UTC 
Created attachment 153136 [details]
The language of the dialog labels and buttons is different from the language in the menu bar
Comment 2 Andreas Gruhler 2020-04-14 20:17:21 UTC 
I can no longer reproduce this issue in 4.2.2, thus, I am going to close this ticket.

The dialogues are translated (or at least the ones I was able to check).

Thank your for your effort!
Comment 3 Xisco Faulí 2021-02-09 12:45:39 UTC 
Thanks for retesting the issue with the latest version.
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been
identified.