Bug 117548 - [Mac] Wrong auto-generated shortcut keys in Traditional Chinese version
Summary: [Mac] Wrong auto-generated shortcut keys in Traditional Chinese version
Status: RESOLVED DUPLICATE of bug 115361
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.3.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-10 12:50 UTC by Franklin Weng
Modified: 2018-05-10 12:56 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Wrong shortcut key in Chinese (7.17 MB, image/jpeg)
2018-05-10 12:52 UTC, Franklin Weng 		Details
Version information (174.11 KB, image/jpeg)
2018-05-10 12:52 UTC, Franklin Weng 		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 Franklin Weng 2018-05-10 12:50:58 UTC 
Description:
When starting the LibreOffice center in Mac, the auto-generated shortcut keys becomes Chinese instead of English, which could not use.

Only in center, not other components.

Steps to Reproduce:
1. Install LibreOffice in Mac
2. Start LibreOffice center
3.

Actual Results:  
Wrong shortcut keys as attachment.

Expected Results:
Shortcut keys should not be in Chinese.


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (Linux; Android 7.0; SM-N9208 Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.158 Mobile Safari/537.36
Comment 1 Franklin Weng 2018-05-10 12:52:03 UTC 
Created attachment 142013 [details]
Wrong shortcut key in Chinese
Comment 2 Franklin Weng 2018-05-10 12:52:59 UTC 
Created attachment 142014 [details]
Version information
Comment 3 eisa01 2018-05-10 12:56:29 UTC 
Thanks for reporting! This seems to confirm the unconfirmed bug 115361

Being a latin keyboard user, am I correct that these shortcut keys are not possible to press/type?

*** This bug has been marked as a duplicate of bug 115361 ***