On 17.04.2009, at 06:41, Andreas Raab wrote:

> BTW, the situation doesn't seem to be quite as dire as one might  
> assume. Attached are two screenshots which were created by:
> a) Installing Dejavu first (download, click, choose "install font")
> b) Going to ru.wikipedia.org and el.wikipedia.org
> c) Copying and pasting the first article from the front page
> That is about the extent of functionality that I can verify and it  
> does seem to work allright except from the Character cr glyph  
> displayed in Dejavu (I'm not sure where that comes from).
>
> Perhaps half of the problems could be solved simply by installing  
> Dejavu by default?
>
> Cheers,
>  - Andreas

One of the problems, yes. But note your example only works because the  
Windows VM does paste unicode. On the Mac I get this:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Workspace.png
Type: image/png
Size: 10239 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20090417/a4bb55ab/Workspace.png
-------------- next part --------------


The first line shows DejaVuSans does work, has cyrillic glyphs.  
(DejaVuSans-Bold.ttf produces an error on import)

The second line shows typing does not work, I typed a cyrillic ? but  
it is treated as 0 (the utf32 problem).

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).

This is using the latest release of course (Squeak3.10.2-7179mac.zip  
from squeak.org's front page).

- Bert -

>
> Andreas Raab wrote:
>> Bert Freudenberg wrote:
>>> Err, we know quite well about these problems. Typing unicode chars  
>>> don't work because the utf32 charcode is not used by the released  
>>> image. To paste unicode text on the Mac you would need the image  
>>> support for the extendend clipboard plugin. But even if typing or  
>>> pasting works, the fonts only cover the latin-1 range, not full  
>>> unicode. Neither Freetype nor HostFonts nor Pango support is in  
>>> the released image, nor did we standardize on one.
>>>
>>> All of these issues have been solved already, but did not make it  
>>> into a release afaik.
>> Interesting. Goes to show that I haven't been paying much  
>> attention. But if the fixes are there (can you send some pointers?)  
>> it sounds like a perfect candidate to assemble those into 3.11 and  
>> get this stuff straight. For fonts, there is Dejavu (http://dejavu-fonts.org/ 
>> ) which is based on the Bitstream Vera family and should make for a  
>> virtually identical replacement.
>> Cheers,
>>  - Andreas
>
> <ru.wikipedia.png><el.wikipedia.png>