[squeak-dev] Cuis update

>  
>
> Bert Freudenberg wrote:
>> Below that the paste from ru.wikipedia. These are actual question
>> marks (ASCII 63), the Mac VM does not paste Unicode even if setting
>> SqueakEncodingType to UTF-8 (only the extended clipboard plugin does
>> this).
>
> Fortunately, at least that part is very easy to fix. I asked our CEO
> if we could release our clipboard support code back to the community
> and he agreed, so find attched an sqMacUIClipBoard.c version which
> does support Unicode copy/paste properly via UTF-8 (this should work
> as a drop-in replacement to the existing sqMacUIClipBoard.c). Brought
> to you by the friendly folks at Qwaq.
>
> Cheers,
>   - Andreas

> Juan Vuletich wrote:
>> Is there some Windows VM parameter to get 8 bit clipboard data?
>
> Starting with the 3.10 series the Windows VMs use UTF-8 exclusively
> and consistently in its entire interface. All strings passed into or
> out of the Windows VM use UTF-8. This is true for clipboard as well as
> files, directories  etc.
>
>> But on Windows I get 2 bytes, 195 and 161, and these non-unicode
>> images get confused.
>
> If you want to use non-ascii characters you will need an encoder and a
> decoder for the range of characters your image supports. You can start
> from here:
>
>   http://bugs.squeak.org/view.php?id=7314
>
> This has a *very* fast conversion to and from UTF-8 encoded
> representations for strings and the only thing you need to change is
> to restrict the incoming unicode value in utf8ToSqueak to whatever
> range of characters you support.
>
> Cheers,
>   - Andreas

> BTW, the image needs to deal with different VMs using various encoding
> for clipboard data. Currently, a check is made, to assume UTF-8 if on
> Windows, and MacRoman elsewhere. It seems Mac will support UTF-8 soon.
>
> I think we need a new primitive, perhaps #clipboardEncoding, or
> #vmTextEncoding, that could answer UTF-8 / MacRoman / ASCII and may be
> others. That would ease supporting various VMs with the same image.
>
> WRT keyboard events, it seems not to be necessary. VMs store Unicode
> keystrokes in different slots in the event buffer, than the one used for
> MacRoman. So, the image can tell, right?
>
> What do you think?

> Bert Freudenberg wrote:
>> Below that the paste from ru.wikipedia. These are actual question  
>> marks (ASCII 63), the Mac VM does not paste Unicode even if setting  
>> SqueakEncodingType to UTF-8 (only the extended clipboard plugin  
>> does this).
>
> Fortunately, at least that part is very easy to fix. I asked our CEO  
> if we could release our clipboard support code back to the community  
> and he agreed, so find attched an sqMacUIClipBoard.c version which  
> does support Unicode copy/paste properly via UTF-8 (this should work  
> as a drop-in replacement to the existing sqMacUIClipBoard.c).  
> Brought to you by the friendly folks at Qwaq.
>
> Cheers,
>  - Andreas
> <LICENSE.txt><sqMacUIClipBoard.c>

>
> Juan Vuletich wrote:
>> BTW, the image needs to deal with different VMs using various
>> encoding for clipboard data. Currently, a check is made, to assume
>> UTF-8 if on Windows, and MacRoman elsewhere. It seems Mac will
>> support UTF-8 soon.
>>
>> I think we need a new primitive, perhaps #clipboardEncoding, or
>> #vmTextEncoding, that could answer UTF-8 / MacRoman / ASCII and may
>> be others. That would ease supporting various VMs with the same image.
>>
>> WRT keyboard events, it seems not to be necessary. VMs store Unicode
>> keystrokes in different slots in the event buffer, than the one used
>> for MacRoman. So, the image can tell, right?
>>
>> What do you think?
>
> Although you are technically correct, I think the days of Latin1 only
> support are simply over and I would prefer to move forward and leave
> them completely behind us. The best way to achieve this is when all
> VMs use UTF-8 everywhere and all VMs produce Unicode input characters.
> The changes to support this aren't difficult (just a bit tedious) and
> the image side is trivial for those images that don't need (or want)
> to support Unicode. I really don't see any value in fiddling with
> different encodings since UTF-8 is both canonical and well supported.
>
> Cheers,
>   - Andreas

> Bert Freudenberg wrote:
>> Below that the paste from ru.wikipedia. These are actual question  
>> marks (ASCII 63), the Mac VM does not paste Unicode even if setting  
>> SqueakEncodingType to UTF-8 (only the extended clipboard plugin  
>> does this).
>
> Fortunately, at least that part is very easy to fix. I asked our CEO  
> if we could release our clipboard support code back to the community  
> and he agreed, so find attched an sqMacUIClipBoard.c version which  
> does support Unicode copy/paste properly via UTF-8 (this should work  
> as a drop-in replacement to the existing sqMacUIClipBoard.c).  
> Brought to you by the friendly folks at Qwaq.
>
> Cheers,
>  - Andreas
> <LICENSE.txt><sqMacUIClipBoard.c>