Language Data Values

[sil.linguist]

In Ukelele I find that I can set the language value, and the script value and the region value.  I have two questions about this:

1. Where are these values stored in the keyboard files? I have parsed the XML .keylayout file and I am missing where these values are stored. Are these values only stored in the .bundle packages?

2. How does one declare that a keyboard is designed for two or more languages? Are multiple language values declare-able available?

- Hugh

[Sorin Paliga]

These values are not very important now, they are heritage labels. If Unicode encoding is chosen, a keylayout may theoretically cover all Unicode blocks. You may also choose Central European or Cyrillic.

I have no idea where these values are stored, I guess they are somewhat included in the keyboard ID, which has a lower and an upper limit. Negative values are Unicode.

--
You received this message because you are subscribed to the Google Groups "Ukelele Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ukelele-user...@googlegroups.com.
To post to this group, send email to ukelel...@googlegroups.com.
Visit this group at http://groups.google.com/group/ukelele-users.
For more options, visit https://groups.google.com/d/optout.

[John Brownie]

On 3/06/2015 5:41, sil.linguist wrote:

In Ukelele I find that I can set the language value, and the script value and the region value.  I have two questions about this:

1. Where are these values stored in the keyboard files? I have parsed the XML .keylayout file and I am missing where these values are stored. Are these values only stored in the .bundle packages?

They are only stored in bundles.

2. How does one declare that a keyboard is designed for two or more languages? Are multiple language values declare-able available?

You can't. Only one language code is supported. Ask Apple if you would like to have more than one, but I doubt that it can be done without changing the way it's implemented.

John
--
John Brownie, john_b...@sil.org or j.br...@sil.org.pg
Summer Institute of Linguistics      | Mussau-Emira language, Mussau Is.
Ukarumpa, Eastern Highlands Province | New Ireland Province
Papua New Guinea                     | Papua New Guinea

[Sorin Paliga]

John

Let me understand the issue correctly. In many, if not all, keylayouts i have created, there are usually more than one unicode blocks.

The problem occurs, I guess, with a specific behavior, e.g. RTL scripts, in which case I do not know one can combine RTL and LTR in one keylayout. Otherwise, one keylayout may contain IPA, CMD, Cyrillic, Greek and many other chars based on the Latin alphabet.

Is there anything I am missing?

Best

[sil.linguist]

Thanks John, 

That is as I feared.

- Hugh

[John Brownie]

On Wed Jun 03 2015 17:24:51 GMT+1000 (PGT) Sorin Paliga wrote:

John

Let me understand the issue correctly. In many, if not all, keylayouts i have created, there are usually more than one unicode blocks.

The problem occurs, I guess, with a specific behavior, e.g. RTL scripts, in which case I do not know one can combine RTL and LTR in one keylayout. Otherwise, one keylayout may contain IPA, CMD, Cyrillic, Greek and many other chars based on the Latin alphabet.

Is there anything I am missing?

I think you're confusing two things. There are the Script codes, which are part of the XML file, and define the range(s) of Unicode characters that the keyboard layout is supposed to produce, and the intended language code, which is for support of the Press and Hold functionality (that brings up a popover to choose a character variant). For Script, choosing Unicode is almost always the right choice. Intended language is targeted more at the user's habits.

[Tom Gewecke]

On Jun 3, 2015, at 3:24 AM, Sorin Paliga wrote:

> The problem occurs, I guess, with a specific behavior, e.g. RTL scripts, in which case I do not know one can combine RTL and LTR in one key layout.

Key layouts are irrelevant to directional behavior. You can have both RTL and LTR without problem. Apple's Hebrew layout has Latin on caps lock.

[Sorin Paliga]

OK, why is then language so relevant? I am still confused, but let it be so, not relevant to the whole topic. :)

[Grzegorz Rolek]

On 03 Jun 2015, at 11:55, Sorin Paliga <sorin....@gmail.com> wrote:

> OK, why is then language so relevant?

Sorin, John has explained that already:

> There are the Script codes [...] and the intended language code, which is for support of the Press and Hold functionality (that brings up a popover to choose a character variant). For Script, choosing Unicode is almost always the right choice. Intended language is targeted more at the user's habits.


The key word here is ‘habits’, as the users of different languages want the character variants in the pop-up to be compiled or arranged in a different way. I can imagine that German users expect to have the umlauts exposed up front on the appropriate vowels, for example. French speakers — not necessarily so.

Regards,
Grzegorz Rolek

[Sorin Paliga]

Oh, pop-ups! Yes, of course...