Bug 4102

Created attachment 2875 [details] [review]
New Iranian keyboard layout, based on proposed new standard

It has a default basic layout with 3 levels.  Also support optional 4th level
for ascii numbers.  It's not part of the standard, but useful for professional
users.	Also the keypad section is not part of standard, but it's the correct
behaviour, when apps/libs support Persian numbers in numeric widgets.

I did a mistake and used xorg as product.  Now I change the product and reassign
to maintainer of xkb.

Absolutely correct to assign it to us. I will commit it ASAP.

committed to xkeyboard-config CVS

Thanks a lot.

Just to make sure, on my Fedora Core 4 I have two Ir layouts installed:

/usr/X11R6/lib/X11/xkb/symbols/pc/ir
/usr/X11R6/lib/X11/xkb/symbols/ir

apparently one should be removed.  Or if there really is any reason for the two,
both should be updated.

Behnam, we have a situation here. There is a copyright statement on the variant
(Sharif FarsiWeb, Inc.), which is a problem. Could this variant be relicensed
under mit/x11 license?

Just to let you know - if we do not settle on the licesing issue, I'd have to
remove the variant, which I do not like to do.

Of course, feel free to relicense it to mit/x11.

But, please rename the additions, as new Iranian/Kurdish added to Iranian set. 
You can add Persian to these layouts, as its main usage is Persian language.
It's not the only for Persian and may be used for other local languages, but
it's better than listing as "Pro/.../Kurdish /...".

> Of course, feel free to relicense it to mit/x11.
Thanks a lot!

> But, please rename the additions, as new Iranian/Kurdish added to Iranian set. 
> You can add Persian to these layouts, as its main usage is Persian language.
> It's not the only for Persian and may be used for other local languages, but
> it's better than listing as "Pro/.../Kurdish /...".

OK, so far the IDs of layouts (excluding hiddens) are:
"basic"
"pro"
"keypad"
"pro_keypad"
"ku"
"ku_f"
"ku_alt"
"ku_ara"

How would you recommend to rename them? Please include the descriptions for the
group.

Behnam, can we trim them down?
Do we even have to keep "basic"?

Bugzilla Upgrade Mass Bug Change

NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO.

  - benjsc
    fd.o Wrangler

No activity.

I finally got to clean up the Iranian Persian layout.  Going to attach the git patch.

Following are the unsolved issues:

- Should we talk about making a separate "kur" file for Kurdish layouts again?  I highly recommend to remove Latin-based Kurdish layouts from the "ir" file.

- "ir" file has some rules in common with "af" one.  The most important ones are
the SPCE [1] and Eastern Indo-Arabic keypad digit bindings.  We can move this special SPCE binding (which has ZWNJ) to "nbsp" file, and the keypad digit bindings to "keypad" file.

Created attachment 29359 [details] [review]
0001-Update-Iran-Persian-layout.patch

- Update the standard info to ISIRI 9147
- Reduce the number of Persian layouts to only 2
- Use "pes_" for the name of Persian parts
- Add Narrow NBSP

> - Should we talk about making a separate "kur" file for Kurdish layouts again? 
I would say no. I'm trying to avoid any political issues here. If people of nation "aaa" live in the state "bb", the layout/variant belongs to the file symbols/bb. I guess, that is simple enough, and (nearly) unambiguous too. Both "aaa" and "bb" are defined in terms of ISO codes, of course.

> I highly recommend to remove Latin-based Kurdish layouts from the "ir" file.
Are you saying that in Iran there are no Kurds who'd use that layout?

> - "ir" file has some rules in common with "af" one.  The most important ones
> are
> the SPCE [1] and Eastern Indo-Arabic keypad digit bindings.  We can move this
> special SPCE binding (which has ZWNJ) to "nbsp" file, and the keypad digit
> bindings to "keypad" file.
I guess that's ok, if you think they would make sense as separate xkb options (for various Asian countries/languages).

I've committed your first patch. You forgot to include changes for base.xml.in - I amended the fix. Looking forward for the second patch (for xkb option).

Please keep in mind - the freeze for the new version starts this Tuesday

very glad to see more unicode (narrow nbsp…) trickling down xkb, congratulations all

(In reply to comment #15)
> I would say no. I'm trying to avoid any political issues here. If people of
> nation "aaa" live in the state "bb", the layout/variant belongs to the file
> symbols/bb. I guess, that is simple enough, and (nearly) unambiguous too. Both
> "aaa" and "bb" are defined in terms of ISO codes, of course.

I have no political interest in this. As Kurdish culture is distributed in at least 3 states, I just though the rules for Arabic would work better here.

Kurdish and Azari are considered as regional languages by the constitution.  So it actually makes sense to have them under "Iranian" group.

> Are you saying that in Iran there are no Kurds who'd use that layout?

But yes, the problem is that the Latin script for Kurdish is not used in Iran.


> I guess that's ok, if you think they would make sense as separate xkb options
> (for various Asian countries/languages).

Good, so you and Nicolas are both agree with that.  Going to prepare it for the Tuesday freeze.


(In reply to comment #16)
> I've committed your first patch. You forgot to include changes for base.xml.in
> - I amended the fix.

Thanks for the quick commit, and the base.xml fix.

I make follow up bugs for the general ideas.  Closing this bug as it's fixed by the last patch.

Bug #23995: Add ZWNJ/ZNJ mappings on SPCE to "nbsp" feature list