Denis, His problem is much more fundamental: his Pharo image does not start up (correctly) because some of its paths (his directory/folder names) where Pharo is located uses Cyrillic characters. He has no chance to fix this. I think this is a problem with FileSystem path decoding on Windows. First we needed a way to reproduce this exactly, as always.
Sven > On 10 Nov 2017, at 11:44, Denis Kudriashov <[email protected]> wrote: > > Hi. > Sorry for the late response. I skipped your mail somehow. > > You need to try CP1251 converter. In past I used CP1251TextConverter from > http://www.squeaksource.com/RussianSupport.html. > But now there is very nice ZnCharacterEncoder hierarchy which provides out of > the box main encodings. To get cp1251 encoder evaluate: > 'cp1251' asZnCharacterEncoder > I not tried to use it in practice. So I could not give you examples for this. > But I hope it gives you directions to look at. > > And question for others: should not we deprecate old TextConverter's and move > to zn encoders completely? > > 2017-11-01 7:15 GMT+01:00 Викентий Потапов <[email protected]>: > > Good day! > Now i download fresh latest pharo archive and unzipped it to C:\Pharo 6.1. > The error still exists. > Debugging shows that error comes with reading from environment varaible: > ... > ByteString(String) > convertFromWithConverter: > FilePathEncoder class decode: > WindowsResolver(platformResolver) resolveString: > WindowsResolver(platformResolver) directoryFromEnvVariableNamed:or: > ... > > it tries to read 'USERPROFILE', get envValue 'C:\Users\Викентий' and can't > parse cyrillic characters in this path. > > Please, tell me how to fix it by myself. > > Best regards, Vikenti. > > > > >
