SmalltalkImage current vmVersion 'Squeak3.9 of 7 November 2006 [latest update: #7067]'
"About Squeak on Win32" 'Squeak 3.10.6 (release) from Aug 30 2007'
Size of Squeak.exe is 985600 bytes...
This VM is fine. I'm using it on windows xp with russian support enabled.
I forgot to mention --- I use Window Vista... if it matters
Now I try Locale switchToID: (LocaleID isoLanguage: 'ru').
This throws an exception in StrikeFont class >> setupDefaultFallbackFont (no #Accuat #Accujen #Accula etc. in the system).
I just comment that out and go on.
An exception in PainBoxMorph class >> localeChanged. The same 'decision'.
So far, locale seems to be russian...
I assume these workarounds are also fine, if you are able to enter Russian text.
I take it I'm not. Russian input maps to 'usual' symbols... And I just understood the function: russian 'a' maps to '0', the next ('�') to 1 etc...
However I don't see UTFClipboardInterpeter in Pharo, so you should have a problem with copy/paste. You can fileout it from squeak 3.9 though.
It's the problem to be solved hereafter...
Then I change fonts to one from windows (I tried Arial, Courier New, Times New Roman).
After that I open workspace (having font there changed) and 'print it':
file := MultiByteFileStream fileNamed: 'c:\Home\chaetal\Work\Pharo\russian\russian.txt'.
[file contents] ensure: [file close].
MultiByteFileStream doesn't know the encoding of the file and it uses system encoding as its best guess. 'TextConverter defaultSystemConverter' should yield ->an UTF8TextConverter in your case. If it does not - you may try to set an instance of UTF8TextConverter as a converter for MultiByteFileStream (instance side API).
Ivar 'converter' in the stream is set to 'an UTF8TextConverter', so it's ok here.
(where russian.txt is UTF-8 file with russian text).
This gives me a bunch of question marks... :(
Now these marks. To display Russian text you have to enable unicode font in places where you'd like to see it. For panes it is probably 'default text font' which needs to be set. You did it, right? Do you see, let's say, text rendered with Arial font in newly created workspaces?
Yes, I open new Workspace after selecting default text font and see it correctly... but russian symbols from the file (btw, latin symbols from that files are ok).
...I debugged the process of reading file (file contents) and discovered there is no LanguageEnvironment for russian in the image. So Unicode class >> value: give probably incorrect result. Is that the actual problem?