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
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 wrote:
>
>
> 2014-09-09 14:12 GMT+02:00 Alain Busser :
> Is this a reprodu
2014-09-09 14:12 GMT+02:00 Alain Busser :
> 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
Is this a reproducible case?
http://ss3.gemstone.com/ss/MathsOntologie/MathsOntologie-AlainBusser.68.mcz
I hope not :-)
Alain
On Tue, Sep 9, 2014 at 5:43 AM, Clément Bera wrote:
> What kind of bug do you have with accent ? Do you have a stack trace ?
>
> More importantly, can you give us a rep
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 S
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
