Hello, I encountered a problem when trying to export the Gettext file in Pharo 3.0. In a Pharo 3.0 image, load Gettext and then do the following: TextDomainManager registerCategoryPrefix: 'Fuel' domain: 'Fuel'. GetTextExporter exportTemplate. Apparently, there are some deprecations and doing proceed on them shows a DNU: "RBMethodNode does not understand isMessageNode" I can report the bug somewhere to later find some time to correct it but Pharo bug tracker might not be the right place. Any ideas where this bug should be reported? If someone knowledgeable about RB related stuff can have a look at it, it would be great. tx, usman
thanks usman do you have the expression to load gettext in pharo 3.0 On 28 Feb 2014, at 15:36, Usman Bhatti <usman.bhatti@gmail.com> wrote:
Hello,
I encountered a problem when trying to export the Gettext file in Pharo 3.0. In a Pharo 3.0 image, load Gettext and then do the following:
TextDomainManager registerCategoryPrefix: 'Fuel' domain: 'Fuel'.
GetTextExporter exportTemplate.
Apparently, there are some deprecations and doing proceed on them shows a DNU: "RBMethodNode does not understand isMessageNode"
I can report the bug somewhere to later find some time to correct it but Pharo bug tracker might not be the right place. Any ideas where this bug should be reported?
If someone knowledgeable about RB related stuff can have a look at it, it would be great.
tx, usman
Hi Usman, I committed a new version that fixes a number of things. More is needed because I notice the exporter is not detecting the domain<->categories mapping anymore. Johan On 28 Feb 2014, at 15:36, Usman Bhatti <usman.bhatti@gmail.com> wrote:
Hello,
I encountered a problem when trying to export the Gettext file in Pharo 3.0. In a Pharo 3.0 image, load Gettext and then do the following:
TextDomainManager registerCategoryPrefix: 'Fuel' domain: 'Fuel'.
GetTextExporter exportTemplate.
Apparently, there are some deprecations and doing proceed on them shows a DNU: "RBMethodNode does not understand isMessageNode"
I can report the bug somewhere to later find some time to correct it but Pharo bug tracker might not be the right place. Any ideas where this bug should be reported?
If someone knowledgeable about RB related stuff can have a look at it, it would be great.
tx, usman
On 01 Mar 2014, at 09:57, Johan Brichau <johan@inceptive.be> wrote:
More is needed because I notice the exporter is not detecting the domain<->categories mapping anymore.
On second view, it seems the Seaside package for gettext is not compatible anymore with changes in recent history. So, gettext on its own should be good to go now. Let me know, since I am now mostly focusing on the seaside extension that uses it cheers Johan
Hi Johan, On Sat, Mar 1, 2014 at 10:47 AM, Johan Brichau <johan@inceptive.be> wrote:
On 01 Mar 2014, at 09:57, Johan Brichau <johan@inceptive.be> wrote:
More is needed because I notice the exporter is not detecting the domain<->categories mapping anymore.
On second view, it seems the Seaside package for gettext is not compatible anymore with changes in recent history. So, gettext on its own should be good to go now.
Let me know, since I am now mostly focusing on the seaside extension that uses it
For me, it is working now and the problem seems to be fixed. I have a desktop app so I am not using it with Seaside and everything seems to be working normally. tx a lot, Usman
cheers Johan
participants (3)
-
Johan Brichau -
Pharo4Stef -
Usman Bhatti