[Vm-dev] Re: [Pharo-users] Get "Invalid utf8 input detected" error for a filename

[Igor Stasenko]

On 24 March 2011 16:15, Denis Kudriashov <dionisiydk at gmail.com> wrote:
>
> Hello,
>
> I have similar problem when running pharo from windows user with russian letters in login.
> Debugger opened in SecurityManager stuff during image startUp procedure.
> I ask in past why pharo/squeak doing SecurityManager logic. But without explanation.
>
Denis,
please file the issue on Cog tracker (if its not works on Cog as
well), so it won't be lost in mailing list.
http://code.google.com/p/cog/issues/list

There is already an issue for linux..
So, most probably is not works on windows as well.

> 2011/3/24 Igor Stasenko <siguctua at gmail.com>
>>
>> I think this is VM-related issue.
>>
>> On 24 March 2011 15:31, Juraj Kubelka <juraj.kubelka at gmail.com> wrote:
>> > For now I am able to fix it by following code:
>> > #+BEGIN_SRC
>> > Locale current.  "a Locale(en)"
>> > Latin2Environment class compile: 'fileNameConverterClass
>> > ^ISO88592TextConverter'.
>> > Locale switchToID: (LocaleID isoLanguage: 'cs').
>> > LanguageEnvironment clearDefault.
>> > LanguageEnvironment defaultFileNameConverter. "an ISO88592TextConverter"
>> > #+END_SRC
>> > It is not perfect, directories with Czech characters is not possible to
>> > browse. But I do not mind for now. It is anyway strange, because my
>> > operating system environment is cs_CZ.UTF-8. And files are encoded in UTF-8.
>> > But FileDirectory>>primLookupEntryIn:index: returns file names in a one byte
>> > encoding. It is not valid Latin1 or Latin2.
>> > If anyone knows better solution, please let me know.
>> > Thanks in advance.
>> > Juraj
>> > On Wed, Mar 23, 2011 at 2:10 PM, Juraj Kubelka <juraj.kubelka at gmail.com>
>> > wrote:
>> >>
>> >> Hi,
>> >> If I try to execute:
>> >> (FileDirectory on: '/home/jura') directoryNames
>> >> it says "Invalid utf8 input detected"
>> >> (UTF8TextConverter>>errorMalformedInput), because of a directory named
>> >> 'Veřejné' ('ř' character is the wrong one). In the file system it is the
>> >> right. FileDirectory>>primLookupEntryIn:index: returns a wrong ByteString
>> >> ('Ve?ejné').
>> >> It was tested on Pharo 1.1.1 and Moose 4.3 where I am not able to use a
>> >> Moose Panel tool because of the problem.
>> >> Am I able to solve this problem somehow? Set-up something...
>> >> Thank you in advance,
>> >> Juraj
>> >
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko AKA sig.
>
>
>



-- 
Best regards,
Igor Stasenko AKA sig.