Bug Hunting Session
Bug 47143 - activate support for "complex text layout" based on user's keyboard layout
Summary: activate support for "complex text layout" based on user's keyboard layout
Status: RESOLVED DUPLICATE of bug 47969
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-09 03:31 UTC by Masoud Pourmoosa
Modified: 2012-08-08 13:11 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Masoud Pourmoosa 2012-03-09 03:31:51 UTC
Today I saw this bug in launchpad,

https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/274552

and just because of that I decided to make an account here and give a suggestion to make LibreOffice even better!

That bug was reported because the user didn't know that he/she should activate complex text layout (CTL) support before starting with LibreOffice. CTL support is ESSENTIAL for users of RTL languages like Hebrew, Arabic, but it's not active by default, and many users don't know how to activate it.

I think one good solution is to look for keyboard layouts in the system. If LO finds keyboard layouts of certain languages, it will activate support for CTL. Now the question is, is there any way in LibreOffice to find keyboard layouts installed on the system? I know that this is very OS-specific, but I hope something is already written for that. If yes, then this fix can be easily implemented.
Comment 1 Masoud Pourmoosa 2012-03-25 02:59:27 UTC
I have just noticed this bug in launchpad:

https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/927931
Comment 2 sasha.libreoffice 2012-05-31 03:08:10 UTC
Thanks for new idea
IMHO it is applicable only for Windows. On UNIX it is not allowed for application to know what keyboard installed or used.
Comment 3 bfoman (inactive) 2012-08-08 13:11:56 UTC

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