IIRC, there are two sources of imported code in Monticello. By default it reads from the DataStream encoded .bin file, which stores source containing wide character as... a binary WideString. Unless the .bin file is somehow corrupted, importing non-ascii .mcz therefore works as long as you have a working DataStream reader. * If that path fails, it will read from the .st file, which, IIRC, had utf8 encoding added quite recently by Nicolas Cellier.
So to narrow this down further, one has to ask: For what reason did the DataStream reading fail? - Did the DataStream get written (correctly)? - Did the DataStream fail to read a correctly written file? (f.ex. due to class shape changes in image, without proper backwards compat reading methods added) Why didn't the fallback .st work? - Did the .st file write out as utf8? (could be the case not if written from an older image, but then I'd expect the FileStream to barf, not the compiler) - Did the .st get written as the *correct* utf8? - Did the .st file read in as utf8? Once which combination of those things failed in this case is found, it should be easier to see what a fix could/should be. Cheers, Henry * Which is why non-ascii packages at least used to fail to import in Gemstone, their DataStream reader could not translate WideString instances to the proper internal string representations, and the fallback .st didn't use to be properly encoded. IIRC, the VW reader goes straight for the .st, so same problem there. There's a reason Seaside has ascii-only as a requirement :) On 09 Sep 2014, at 7:07 , Sven Van Caekenberghe <s...@stfx.eu> wrote: > Check/read my mail again: I don't think it is the compiler (my tests show it > is not), then it must be Monticello, in the sense that it treats its input > stream (encoding) wrongly. > > On 09 Sep 2014, at 15:25, Clément Bera <bera.clem...@gmail.com> wrote: > >> >> >> 2014-09-09 14:12 GMT+02:00 Alain Busser <alain.bus...@gmail.com>: >> Is this a reproducible case? >> http://ss3.gemstone.com/ss/MathsOntologie/MathsOntologie-AlainBusser.68.mcz >> >> >> Well I tried to merge that in the latest Pharo 4. >> >> With Opal I got the error 'unknown character' >> >> With the old compiler I got unmatched string quote. >> >> If it's French, could it be a ' ? >> >> It looks like a parser bug to me... >> >> >> I hope not :-) >> >> Alain >> >> On Tue, Sep 9, 2014 at 5:43 AM, Clément Bera <bera.clem...@gmail.com> wrote: >> What kind of bug do you have with accent ? Do you have a stack trace ? >> >> More importantly, can you give us a reproducible case ? I will investigate >> tomorrow if you have a reproducible case to check if this is due to Opal. >> >> It may also be recent changes related to fonts. >> >> 2014-09-08 21:07 GMT+02:00 Sven Van Caekenberghe <s...@stfx.eu>: >> I don't think it is related to Opal: I made a test class with an instance >> variable, accessor and class comment with accents - which I can file out and >> file in: >> >> >> >> >> >> >> >> I tested in 3.0 and 4.0 >> >> The problem might be with Monticello. >> >> >> On 08 Sep 2014, at 20:05, Hilaire <hila...@drgeo.eu> wrote: >> >>> Oh, by the way, it looks like the accents are on the instance variable >>> names. >>> >>> I edited the subject to not pollute the original discussion thread. >>> >>> Hilaire >>> >>> Le 08/09/2014 20:01, Hilaire a écrit : >>>> Marcus, >>>> >>>> Alain's MathOntologie package provide Classes and Messages with French >>>> accent, to ease the understanding of programming to high school students. >>>> I am suspecting the new compiler or something related does not accepted >>>> accented caracters or something different to ASCII. >>>> >>>> Alain, in your package I noted the sources is not utf-8 but iso-8859-15 >>>> (8 bits), I converted it to utf-8 and tried to get it loaded in Pharo3, >>>> but still accent characters caused problem, see screenshot. >>>> >>>> Enclosed source file utf-8 converted and improper imported source code >>>> with accented variable name. >>>> >>>> Hilaire >>>> >>>> Le 08/09/2014 12:18, Alain Busser a écrit : >>>>> Hi, >>>>> >>>>> I don't know if it is related but I have problems importing french files >>>>> inside Pharo 3: Anytime when there is an accentuated character there is >>>>> an error, and the file is not imported. Even if the character is a quote >>>>> inside double quotes (like in "it don't work") there is an error >>>>> message. Right now I can't import MathsOntologie >>>>> (http://ss3.gemstone.com/ss/MathsOntologie/MathsOntologie-AlainBusser.68.mcz) >>>>> >>>>> into Pharo 3 and I have to go on developing it in Pharo 1.4... >>>>> >>>>> Alain >>>>> >>>> >>>> >>> >>> >>> -- >>> Dr. Geo - http://drgeo.eu >>> iStoa - http://istao.drgeo.eu >>> >>> >> >> >> >> >> > >
signature.asc
Description: Message signed with OpenPGP using GPGMail
