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 <sven@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 <hilaire@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