Of course, similar code and change in Morphic, see bottom of change report http://lists.squeakfoundation.org/pipermail/squeak-dev/2011-August/160926.html and follow links.

This came after http://lists.squeakfoundation.org/pipermail/squeak-dev/2011-August/160923.html

But then, there were some complaints of English keyboard users...
http://lists.squeakfoundation.org/pipermail/squeak-dev/2011-August/160968.html

and then later http://forum.world.st/Re-squeak-dev-shift-enclose-broken-in-trunk-td4543316.html

I don't remember how the issue ended, or even if it properly ended...
(That's where an issue tracker should shine, but Squeak one is not really used/maintained).


2014-08-27 17:27 GMT+02:00 Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com>:
I encountered this in Squeak too, because French keyboard is not better than german one :(

Nicolas Cellier uploaded a new version of ST80 to project The Trunk:
http://source.squeak.org/trunk/ST80-nice.136.mcz

==================== Summary ====================

Name: ST80-nice.136
Author: nice
Time: 4 August 2011, 10:43:00.836 am
UUID: 6f8b2f4c-8c8c-48a8-ba32-
bb5b37d827d0
Ancestors: ST80-ul.135

#shiftEnclose: is hardcoding the keyboard layout, which is not compatible with foreign keyboards and modern VM, and prevents correct enclosing to work.

This version rather use a normal #enclose:
A (ParagraphEditor initialize) postscrip is necessary.

=============== Diff against ST80-ul.135 ===============



2014-08-27 17:11 GMT+02:00 Max Bareis <max.bareis@me.com>:



>
>�� �� ��I am curious, because this substitution does not make any sense to
>�� �� ��me. The keyCharacter is always the "real" character ( $( instead
>�� �� ��of $9 ). Also it seems that this substitution reduces the keyboard
>�� �� ��to the en-Layout, therefore breaks the separation of concerns.
>
>
>
> I hope this gets resolved, as it is really annoying with a german
> Keyboard.
>
> And look at the issues:
> 11436 &lt;https://pharo.fogbugz.com/default.asp?11436&gt; and
> 4646 &lt;https://pharo.fogbugz.com/default.asp?4646&gt;
>
>Should the core team take action?
>
>Stef

For me, there is no urgency. I sent it to the mailing list, because I used
the wrong words for the issue search and didn't find any issue. As it is
already on the issue list and I have a workaround (replacing the method in
my download bash file for zeroconf) it is ok.

Max






--
View this message in context: http://forum.world.st/Substitution-of-to-in-TextEditor-shiftEnclose-tp4775052p4775087.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.