Native language support

Hi all.
I would like to use Pharo in my native language (Ukrainian in my case or Cyrillic), but I cannot enter some capital letters to Workspace / System Browser because it's fails on letters: CapsLock or Shift+<Keys> -> [~YGJK"V].
That behavior take place only in Pharo ver. 3 and 4. In Pharo 2.0 all keys working good! What is wrong? Platform - Windows XP

I got a mail that suggest a fix:

https://pharo.fogbugz.com/f/cases/15085/non-english-character-input

(I have attached it as a file-out, you can just drag-n-drop it on the pharo

desktop)

We should check if that solves the problem.

On Wed, Mar 4, 2015 at 10:37 AM, Nick Doodka <[hidden email]> wrote:

Hi all.
I would like to use Pharo in my native language (Ukrainian in my case or Cyrillic), but I cannot enter some capital letters to Workspace / System Browser because it's fails on letters: CapsLock or Shift+<Keys> -> [~YGJK"V].
That behavior take place only in Pharo ver. 3 and 4. In Pharo 2.0 all keys working good! What is wrong? Platform - Windows XP

--

--
Marcus Denker  --  [hidden email]
http://www.marcusdenker.de

Nick Doodka wrote
> next error MessageNotUnderstood:Character>>isArrow.

What is the exact image version (incl. update number)?



-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Native-language-support-tp4809392p4810892.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Now it is Pharo3.0 Latest update: #30862 and Pharo4.0 Latest update: #40474, but previous updates worked the same (ignore cyrillic capital letters ЁНПОЛЄМ)

What is the exact image version (incl. update number)?

I meant specifically regarding the #isArrow error. I don’t think you can be having this in 3.0, so you mean #40474 correct? Is it only after you change the language?

Cheers,
Sean

---

View this message in context: Re: Native language support

Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Hi Nick,

Thanks for chasing the bug down.

Since the code for event handling is probably going to change in favor of SDL2 events soon, I think it should be good to also provide some tests for this, to detect any regression or problem, or at least to document expected behavior. Do you have any pointers of what should be tested? Which are the cases that worked or not and in which keyboard layouts?

Guille

El jue., 12 de mar. de 2015 a la(s) 8:48 a. m., Nick Doodka <[hidden email]> escribió:

After series of trial and error methods I found acceptable solution of my problem. That is chunk of code from Pharo 2.0 should be copy&paste to appropriate place in method HandMorph>>generateKeyboardEvent. This way let me to avoid problems with mouse wheel freezing or generating errors.

i.e.
.....
"Adjustments to provide consistent key value data for different VM's:
- charCode always contains unicode code point.
- keyValue contains 0 if input is outside legacy range"
"If there is no unicode data in the event, assume keyValue contains a correct (<256) Unicode codepoint, and use that"
    (charCode isNil or: [charCode = 0])
        ifTrue: [charCode := keyValue].
"If charCode is not single-byte, we definately have Unicode input. Nil keyValue to avoid garbage values from some VMs."
    charCode > 255 ifTrue: [keyValue := 0].
.....

Full version of patched method I attach as zip-archive for v3 and v4 apart. I suppose developers should correct this method in next releases of Pharo for the sake non-english users support. Thanks for helping and advises.

2015-03-10 16:10 GMT+02:00 Sean P. DeNigris <[hidden email]>:

Now it is Pharo3.0 Latest update: #30862 and Pharo4.0 Latest update: #40474, but previous updates worked the same (ignore cyrillic capital letters ЁНПОЛЄМ)

What is the exact image version (incl. update number)?

I meant specifically regarding the #isArrow error. I don’t think you can be having this in 3.0, so you mean #40474 correct? Is it only after you change the language?

Cheers,
Sean

---

View this message in context: Re: Native language support

Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

After series of trial and error methods I found acceptable solution of my problem. That is chunk of code from Pharo 2.0 should be copy&paste to appropriate place in method HandMorph>>generateKeyboardEvent. This way let me to avoid problems with mouse wheel freezing or generating errors.

i.e.
.....
"Adjustments to provide consistent key value data for different VM's:
- charCode always contains unicode code point.
- keyValue contains 0 if input is outside legacy range"
"If there is no unicode data in the event, assume keyValue contains a correct (<256) Unicode codepoint, and use that"
    (charCode isNil or: [charCode = 0])
        ifTrue: [charCode := keyValue].
"If charCode is not single-byte, we definately have Unicode input. Nil keyValue to avoid garbage values from some VMs."
    charCode > 255 ifTrue: [keyValue := 0].
.....

Full version of patched method I attach as zip-archive for v3 and v4 apart. I suppose developers should correct this method in next releases of Pharo for the sake non-english users support. Thanks for helping and advises.

2015-03-10 16:10 GMT+02:00 Sean P. DeNigris <[hidden email]>:

Now it is Pharo3.0 Latest update: #30862 and Pharo4.0 Latest update: #40474, but previous updates worked the same (ignore cyrillic capital letters ЁНПОЛЄМ)

What is the exact image version (incl. update number)?

I meant specifically regarding the #isArrow error. I don’t think you can be having this in 3.0, so you mean #40474 correct? Is it only after you change the language?

Cheers,
Sean

---

View this message in context: Re: Native language support

Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.