Smalltalk › Pharo › Pharo Smalltalk Users

Gettext with pharo 3 and seaside 3.1.2

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

45 messages Options

123

Peter Schorsch

Sep 07, 2014; 1:32pm

Gettext with pharo 3 and seaside 3.1.2

Hi,

Just started with pharo and seaside. Now I want to write an example
seaside-application but with a multi lingual interface. So I installed
pharo3 and then seaside via configuration browser.

But then I had to realize that the seaside-gettext package was not
installed; and also no gettext package. I found a gettext package in
the repository http://smalltalkhub.com/mc/PharoExtras/Gettext.

I installed the package ConfigurationOfGettext, but the
configuraitonof-browser does not show it. So I installed the package
Gettext via monticello.

Then I found the seaside-gettext packages in the repository
http://smalltalkhub.com/mc/Seaside/Seaside30Addons and installed via
monticello the packages Seaside-Gettext-Core and
Seaside-Gettext-Examples.

Then I open a webbrowser to watch the gettext example. But there I only
see:

fontsize

* locale
* locale
* locale
* locale
* locale

That looks for me like gettext is not working with pharo3 and seaside
3.1.2

Any help is welcome - best a mini howto for gettext with pharo3 and
seaside 3.1.2

Thanks in advance

Ben Coman

Sep 07, 2014; 2:44pm

Re: Gettext with pharo 3 and seaside 3.1.2

I don't know anything about Seaside or Gettext packages, however I
notice one thing (below)...

Peter Schorsch wrote:

> Hi,
>
> Just started with pharo and seaside. Now I want to write an example
> seaside-application but with a multi lingual interface. So I installed
> pharo3 and then seaside via configuration browser.
>
> But then I had to realize that the seaside-gettext package was not
> installed; and also no gettext package. I found a gettext package in
> the repository http://smalltalkhub.com/mc/PharoExtras/Gettext.
>
> I installed the package ConfigurationOfGettext, but the
> configuraitonof-browser does not show it.

The Pharo 3 Configuration Browser only looks at one repository...
http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo30
That repository is open for anyone to drop in a Configuration that works
for Pharo 3. There is a goal that some CI process will validate these
Configurations, but its not there yet.

However what you tried to do makes A LOT of cognitive sense. I'd never
thought of it that way, but it might be good if Configuration Browser
picked up Configurations manually loaded into the Image.

cheers -ben

> So I installed the package
> Gettext via monticello.
>
> Then I found the seaside-gettext packages in the repository
> http://smalltalkhub.com/mc/Seaside/Seaside30Addons and installed via
> monticello the packages Seaside-Gettext-Core and
> Seaside-Gettext-Examples.
>
> Then I open a webbrowser to watch the gettext example. But there I only
> see:
>
> fontsize
>
> * locale
> * locale
> * locale
> * locale
> * locale
>
> That looks for me like gettext is not working with pharo3 and seaside
> 3.1.2
>
> Any help is welcome - best a mini howto for gettext with pharo3 and
> seaside 3.1.2
>
> Thanks in advance
>
>
>

... [show rest of quote]

stepharo

Sep 07, 2014; 6:32pm

Re: Gettext with pharo 3 and seaside 3.1.2

In reply to this post by Peter Schorsch

On 7/9/14 15:32, Peter Schorsch wrote:
> Hi,
>
> Just started with pharo and seaside.

Welcome!

> Now I want to write an example
> seaside-application but with a multi lingual interface. So I installed
> pharo3 and then seaside via configuration browser.
>
> But then I had to realize that the seaside-gettext package was not
> installed; and also no gettext package. I found a gettext package in
> the repository http://smalltalkhub.com/mc/PharoExtras/Gettext.
>
> I installed the package ConfigurationOfGettext, but the
> configuraitonof-browser does not show it.

The configuration browser only shows the configurations that are
published in a given repository.
> So I installed the package
> Gettext via monticello.

I think that people will reply to you. I know that there was a conflict
between one class in the getText and one in Pharo30.

> Then I found the seaside-gettext packages in the repository
> http://smalltalkhub.com/mc/Seaside/Seaside30Addons and installed via
> monticello the packages Seaside-Gettext-Core and
> Seaside-Gettext-Examples.
>
> Then I open a webbrowser to watch the gettext example. But there I only
> see:
>
> fontsize
>
> * locale
> * locale
> * locale
> * locale
> * locale
>
> That looks for me like gettext is not working with pharo3 and seaside
> 3.1.2
>
> Any help is welcome - best a mini howto for gettext with pharo3 and
> seaside 3.1.2
>
> Thanks in advance
>
>

... [show rest of quote]

Marcus Denker-4

Sep 08, 2014; 8:08am

Re: Gettext with pharo 3 and seaside 3.1.2

On 07 Sep 2014, at 20:32, stepharo <[hidden email]> wrote:

>
> On 7/9/14 15:32, Peter Schorsch wrote:
>> Hi,
>>
>> Just started with pharo and seaside.
>
> Welcome!
>
>> Now I want to write an example
>> seaside-application but with a multi lingual interface. So I installed
>> pharo3 and then seaside via configuration browser.
>>
>> But then I had to realize that the seaside-gettext package was not
>> installed; and also no gettext package. I found a gettext package in
>> the repository http://smalltalkhub.com/mc/PharoExtras/Gettext.
>>
>> I installed the package ConfigurationOfGettext, but the
>> configuraitonof-browser does not show it.
> The configuration browser only shows the configurations that are published in a given repository.
>> So I installed the package
>> Gettext via monticello.
>
> I think that people will reply to you. I know that there was a conflict between one class in the getText and one in Pharo30.

... [show rest of quote]

There is an issue here:

https://pharo.fogbugz.com/f/cases/13655/System-Localization-and-Gettext-have-classes-with-identical-names

Marcus

HilaireFernandes

Sep 08, 2014; 9:16am

Re: Gettext with pharo 3 and seaside 3.1.2

In reply to this post by Peter Schorsch

What is the purpose of the seaside-gettext package ?
Is it a relic or is it useful? Gettext is orthogonal to Seaside.

Hilaire

Le 07/09/2014 15:32, Peter Schorsch a écrit :
> But then I had to realize that the seaside-gettext package was not
> installed; and also no gettext package. I found a gettext package in
> the repositoryhttp://smalltalkhub.com/mc/PharoExtras/Gettext.
>
> I installed the package ConfigurationOfGettext, but the
> configuraitonof-browser does not show it. So I installed the package
> Gettext via monticello.

--
Dr. Geo - http://drgeo.eu
iStoa - http://istao.drgeo.eu

http://drgeo.eu

Alain Busser

Sep 08, 2014; 10:18am

Re: Gettext with pharo 3 and seaside 3.1.2

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

On Mon, Sep 8, 2014 at 1:16 PM, Hilaire <[hidden email]> wrote:

What is the purpose of the seaside-gettext package ?
Is it a relic or is it useful? Gettext is orthogonal to Seaside.

Hilaire

Le 07/09/2014 15:32, Peter Schorsch a écrit :

But then I had to realize that the seaside-gettext package was not
installed; and also no gettext package. I found a gettext package in
the repositoryhttp://smalltalkhub.com/mc/PharoExtras/Gettext.

I installed the package ConfigurationOfGettext, but the
configuraitonof-browser does not show it. So I installed the package
Gettext via monticello.

--
Dr. Geo - http://drgeo.eu
iStoa - http://istao.drgeo.eu

... [show rest of quote]

Usman Bhatti

Sep 08, 2014; 10:35am

Re: Gettext with pharo 3 and seaside 3.1.2

In reply to this post by Peter Schorsch

Hi Peter,

For my application needs (English -> French), I normally use the gettext package from STHub and it works without any problems for me.

http://smalltalkhub.com/#!/~PharoExtras/Gettext

GetText so far not including in the Configuration Browser but we should include it. There is also a configurationOf for Gettext and some explanation in Pharo book how to use the package.

http://pharo.gemtalksystems.com/book/LanguageAndLibraries/Localisation/PreparingImage/

I dont know the seaside version and I have never tested it.

usman

On Sun, Sep 7, 2014 at 3:32 PM, Peter Schorsch <[hidden email]> wrote:

Hi,

Just started with pharo and seaside. Now I want to write an example
seaside-application but with a multi lingual interface. So I installed
pharo3 and then seaside via configuration browser.

But then I had to realize that the seaside-gettext package was not
installed; and also no gettext package. I found a gettext package in
the repository http://smalltalkhub.com/mc/PharoExtras/Gettext.

I installed the package ConfigurationOfGettext, but the
configuraitonof-browser does not show it. So I installed the package
Gettext via monticello.

Then I found the seaside-gettext packages in the repository
http://smalltalkhub.com/mc/Seaside/Seaside30Addons and installed via
monticello the packages Seaside-Gettext-Core and
Seaside-Gettext-Examples.

Then I open a webbrowser to watch the gettext example. But there I only
see:

fontsize

* locale
* locale
* locale
* locale
* locale

That looks for me like gettext is not working with pharo3 and seaside
3.1.2

Any help is welcome - best a mini howto for gettext with pharo3 and
seaside 3.1.2

Thanks in advance

... [show rest of quote]

Stephan Eggermont-3

Sep 08, 2014; 5:07pm

Re: Gettext with pharo 3 and seaside 3.1.2

In reply to this post by Peter Schorsch

Depending on your exact needs, you might be better of with the QCMagritte
based multi-language support.

https://www.youtube.com/watch?v=cTut44Xs3_U

To try download a QCMagritte image from
https://ci.inria.fr/pharo-contribution/job/QCMagritte/

start a seaside adapter
ZnZincServerAdaptor startOn: 8081.

browse to the qcmagritte application.
http://localhost:8081/qcmagritte

tutorial is at
http://localhost:8081/

Stephan

HilaireFernandes

Sep 08, 2014; 6:01pm

Re: Gettext with pharo 3 and seaside 3.1.2

In reply to this post by Alain Busser

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

mathontologieimport.png (57K) Download Attachment

source2.st.zip (22K) Download Attachment

http://drgeo.eu

HilaireFernandes

Sep 08, 2014; 6:05pm

Math Ontologie on Pharo 3.0

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
>>
>
>

... [show rest of quote]

--
Dr. Geo - http://drgeo.eu
iStoa - http://istao.drgeo.eu

http://drgeo.eu

Sven Van Caekenberghe-2

Sep 08, 2014; 7:07pm

Re: Math Ontologie on Pharo 3.0

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 <[hidden email]> 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
>
>

... [show rest of quote]

Screen Shot 2014-09-08 at 21.03.01.png (267K) Download Attachment

FrenchCircle.st (1K) Download Attachment

Clément Béra

Sep 09, 2014; 1:43am

Re: Math Ontologie on Pharo 3.0

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 <[hidden email]>:

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 <[hidden email]> 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
>
>

... [show rest of quote]

Marcus Denker-4

Sep 09, 2014; 7:56am

Re: Gettext with pharo 3 and seaside 3.1.2

In reply to this post by HilaireFernandes

I will have a look and check… (with the first goal to add an issue tracker entry for it)
On 08 Sep 2014, at 20:01, Hilaire <[hidden email]> wrote:

> 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
> <mathontologieimport.png><source2.st.zip>

... [show rest of quote]

Alain Busser

Sep 09, 2014; 12:12pm

Re: Math Ontologie on Pharo 3.0

In reply to this post by Clément Béra

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 <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]> 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
>
>

... [show rest of quote]

... [show rest of quote]

Clément Béra

Sep 09, 2014; 1:25pm

Re: Math Ontologie on Pharo 3.0

2014-09-09 14:12 GMT+02:00 Alain Busser <[hidden email]>:

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 <[hidden email]> 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 <[hidden email]>:
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 <[hidden email]> 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
>
>

... [show rest of quote]

... [show rest of quote]

... [show rest of quote]

HilaireFernandes

Sep 09, 2014; 1:43pm

Re: Gettext with pharo 3 and seaside 3.1.2

In reply to this post by Marcus Denker-4

Absolutely right. I open a ticket for Alain
https://pharo.fogbugz.com/f/cases/13980/Math-Ontologie-on-Pharo-3-0.

Alain I suggest you get your hand in the Pharo bug tracker
(http://bugs.pharo.org) and create yourself an account[1] there to
comment and to report additional problem you may meet.

[1] https://pharo.fogbugz.com/default.asp?W41

Le 09/09/2014 09:56, Marcus Denker a écrit :
> I will have a look and check… (with the first goal to add an issue tracker entry for it)
> On 08 Sep 2014, at 20:01, Hilaire<[hidden email]> wrote:

--
Dr. Geo - http://drgeo.eu
iStoa - http://istao.drgeo.eu

http://drgeo.eu

HilaireFernandes

Sep 09, 2014; 1:44pm

Re: Gettext with pharo 3 and seaside 3.1.2

In reply to this post by Marcus Denker-4

http://drgeo.eu

Sven Van Caekenberghe-2

Sep 09, 2014; 5:07pm

Re: Math Ontologie on Pharo 3.0

In reply to this post by Clément Béra

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 <[hidden email]> wrote:

>
>
> 2014-09-09 14:12 GMT+02:00 Alain Busser <[hidden email]>:
> 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 <[hidden email]> 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 <[hidden email]>:
> 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 <[hidden email]> 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
> >
> >
>
>
>
>
>

... [show rest of quote]

Henrik Sperre Johansen

Sep 10, 2014; 8:41am

Re: Math Ontologie on Pharo 3.0

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 <[hidden email]> 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 <[hidden email]> wrote:
>
>>
>>
>> 2014-09-09 14:12 GMT+02:00 Alain Busser <[hidden email]>:
>> 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 <[hidden email]> 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 <[hidden email]>:
>> 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 <[hidden email]> 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
>>>
>>>
>>
>>
>>
>>
>>
>
>

... [show rest of quote]

signature.asc (859 bytes) Download Attachment

Johan Brichau-2

Sep 13, 2014; 7:57am

Re: Gettext with pharo 3 and seaside 3.1.2

In reply to this post by HilaireFernandes

Hi,

The Seaside-Gettext package is in the Seaside repository http://www.smalltalkhub.com/#!/~Seaside/Seaside30Addons

The package in the PharoExtras repository is a relic.

The ConfigurationOfSeaside3 correctly references the Seaside-Gettext package and it’s absolutely functional (using this in production systems).

What is a bit silly is that the ConfigurationOfSeaside3 relies on people chosing the appropriate groups to load and the Pharo configuration browser always loads the default transparantly.

I will probably update that for Seaside 3.2.0, so that the default loads everything for newcomers, but for the current version some load configurations might rely on it and that’s the way it is.

Johan

On 08 Sep 2014, at 11:16, Hilaire <[hidden email]> wrote:

What is the purpose of the seaside-gettext package ?
Is it a relic or is it useful? Gettext is orthogonal to Seaside.

Hilaire

Le 07/09/2014 15:32, Peter Schorsch a écrit :
But then I had to realize that the seaside-gettext package was not
installed; and also no gettext package. I found a gettext package in
the <a href="repositoryhttp://smalltalkhub.com/mc/PharoExtras/Gettext">repositoryhttp://smalltalkhub.com/mc/PharoExtras/Gettext.

I installed the package ConfigurationOfGettext, but the
configuraitonof-browser does not show it. So I installed the package
Gettext via monticello.

--
Dr. Geo - http://drgeo.eu
iStoa - http://istao.drgeo.eu

... [show rest of quote]

123