Bug 94036 - Proposed keyboard layout for Jawi
Summary: Proposed keyboard layout for Jawi
Status: RESOLVED FIXED
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: xkb
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-07 18:08 UTC by fikr4n
Modified: 2016-06-02 21:22 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Modified/new files as well as the diff (19.40 KB, text/plain)
2016-02-07 18:08 UTC, fikr4n
Details
The diff (5.69 KB, patch)
2016-02-07 18:12 UTC, fikr4n
Details | Splinter Review
The diff v2 (added Brunei) (6.44 KB, patch)
2016-02-07 23:55 UTC, fikr4n
Details | Splinter Review
The diff v3 (added ڠ) (6.49 KB, patch)
2016-02-08 00:59 UTC, fikr4n
Details | Splinter Review
The diff v4 (fix parens, quotes, and comparison ops) (5.67 KB, patch)
2016-04-05 22:59 UTC, fikr4n
Details | Splinter Review
The diff against 9f0f6e9 (5.67 KB, patch)
2016-04-05 23:13 UTC, fikr4n
Details | Splinter Review
Diff v5 against commit 9f0f6e9276391b9d0878721c0871d6a78dab1d91 (6.08 KB, patch)
2016-05-08 13:27 UTC, fikr4n
Details | Splinter Review
Diff against commit db8272080e8d50328b40d4072ea1424ea0784b50 (1.29 KB, patch)
2016-05-21 23:22 UTC, fikr4n
Details | Splinter Review

Description fikr4n 2016-02-07 18:08:58 UTC
Created attachment 121574 [details]
Modified/new files as well as the diff

Here I try to create a new keyboard layout for Jawi which is/was used in Malaysia, Brunei, South Thailand, South Philippines, and Indonesia. I am new to xkeyboard-config, please correct me if there is something wrong. Attached modified and new files as well as the diff with commit 4a48ae39506bfd78db073376ce21dbbdc48dc55d.

This one is modified from Arabic (Buckwalter) which is based on Latin characters on US keyboard layout. The reason is that most computers in Indonesia and Malaysia use US keyboard layout labelled with Latin characters instead of Arabic characters. It is a good idea if someone create another variant which is based on pure Arabic keyboard.
Comment 1 fikr4n 2016-02-07 18:12:46 UTC
Created attachment 121575 [details] [review]
The diff

I am sorry, Bugzilla does not recognize that the file I uploaded before was a tar.gz, so I re-upload one of the content.
Comment 2 fikr4n 2016-02-07 23:55:27 UTC
Created attachment 121580 [details] [review]
The diff v2 (added Brunei)

I add a new patch which includes Brunei (bn).
Comment 3 fikr4n 2016-02-08 00:59:06 UTC
Created attachment 121581 [details] [review]
The diff v3 (added ڠ)

I am sorry, I wrote the configuration at late night so I forgot a character. Now I've added it and tested/compared to the list of Jawi alphabet at https://en.wikipedia.org/wiki/Jawi_alphabet#Letters.

The attachment is still diff for branch 4a48ae39506bfd78db073376ce21dbbdc48dc55d instead of diff for my previous diff.
Comment 4 fikr4n 2016-02-08 02:42:48 UTC
Guys, I need your suggestion. Arabic Buckwalter uses ORNATE LEFT PARENTHESIS (U+FD3E) and ORNATE RIGHT PARENTHESIS (U+FD3F) instead of LEFT PARENTHESIS (U+0028) and RIGHT PARENTHESIS (U+0029) like in default Arabic layout. This layout is modification of Arabic Buckwalter so currently it uses the "ornate" ones. However I think that the "regular" ones are more frequently used. So which one should this layout use? If I replace them with the regular ones, should "«" and "»" quotations be replaced too (with "<" and ">" comparison signs) to make it consistent?
Comment 5 Sergey V. Udaltsov 2016-04-03 23:34:19 UTC
(In reply to fikr4n from comment #4)
> Guys, I need your suggestion. Arabic Buckwalter uses ORNATE LEFT PARENTHESIS
> (U+FD3E) and ORNATE RIGHT PARENTHESIS (U+FD3F) instead of LEFT PARENTHESIS
> (U+0028) and RIGHT PARENTHESIS (U+0029) like in default Arabic layout. This
> layout is modification of Arabic Buckwalter so currently it uses the
> "ornate" ones. However I think that the "regular" ones are more frequently
> used. So which one should this layout use? If I replace them with the
> regular ones, should "«" and "»" quotations be replaced too (with "<" and
> ">" comparison signs) to make it consistent?

Sorry, I really cannot have any opinion on that. Perhaps you need to talk to other Arabic-speaking people. Should I apply your patch now or wait till you decide finally?
Comment 6 fikr4n 2016-04-05 22:59:10 UTC
Created attachment 122740 [details] [review]
The diff v4 (fix parens, quotes, and comparison ops)

Thank you for your reply. Finally I've decided to use left_paren and right_paren like in standard Arabic keyboard. I've attached the final (final until now :D) diff.

Best regard
Comment 7 fikr4n 2016-04-05 23:13:25 UTC
Created attachment 122741 [details] [review]
The diff against 9f0f6e9

I am sorry I forgot to pull the newest when I created the diff before. So this is the diff against commit 9f0f6e9. The difference between it and the diff before is only at line numbers.
Comment 8 fikr4n 2016-05-08 13:27:34 UTC
Created attachment 123551 [details] [review]
Diff v5 against commit 9f0f6e9276391b9d0878721c0871d6a78dab1d91

Change log:
- Add more characters for 3rd and 4th shift (AltGr)
- Change characters at Shift+E and Shift+O to ێ and ۆ
- Change character at period key to general period/dot, urdu dot moved to 3rd shift
Comment 9 Sergey V. Udaltsov 2016-05-18 14:31:22 UTC
Thank you, I committed your patch. Also had to patch symbols/Makefiles.am

Could you please fix invalid ISO 639 codes ms and in - you added them to rules.base.xml.in. They should be 3-letter. Thanks
Comment 10 fikr4n 2016-05-21 23:22:22 UTC
Created attachment 123962 [details] [review]
Diff against commit db8272080e8d50328b40d4072ea1424ea0784b50

Thank you for accepting my patch. Here is the new diff/patch. I've changed two-letter ISO 639 to three-letter based on https://www.loc.gov/standards/iso639-2/php/English_list.php, specifically "id" -> "ind" and "ms" -> "msa".
Comment 11 Sergey V. Udaltsov 2016-06-02 21:22:56 UTC
Good, committed!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.