Sten Aksel Heien | 1 Oct 2003 12:15
Picon

i18n in Forrest

Hi all

Here is a norwegian translation for the fresh-site menu.

I still have problem seeing the strategy for translating a whole site 
- have multiple languages for one site.

Pointers needed :-)

--
Sten Aksel Heien - sah <at> objectnet.no
Attachment (menu_no.xml): text/xml, 720 bytes
Sten Aksel Heien | 1 Oct 2003 14:54
Picon

RE: i18n in Forrest

Hi again

Sorry for sending "menu_no.xml" once more, but first one was sent before I
had saved my last edit.

- Sten Aksel

> -----Original Message-----
> From: Sten Aksel Heien [mailto:sah <at> objectnet.no]
> Sent: 1. oktober 2003 12:16
> To: forrest-dev <at> xml.apache.org
> Subject: i18n in Forrest
>
>
> Hi all
>
> Here is a norwegian translation for the fresh-site menu.
>
> I still have problem seeing the strategy for translating a whole site
> - have multiple languages for one site.
>
> Pointers needed :-)
>
> --
> Sten Aksel Heien - sah <at> objectnet.no
>
Attachment (menu_no.xml): text/xml, 704 bytes
Konstantin Piroumian | 2 Oct 2003 07:59
Picon
Favicon

Re: i18n in Forrest

Thanks for the translation.
Committed.

Though, I have no idea how to check this. Anybody knows how to switch the
language on Forrest site?

Regards,
  Konstantin

From: "Sten Aksel Heien" <sah <at> objectnet.no>

> Hi again
>
> Sorry for sending "menu_no.xml" once more, but first one was sent before I
> had saved my last edit.
>
> - Sten Aksel
>
> > -----Original Message-----
> > From: Sten Aksel Heien [mailto:sah <at> objectnet.no]
> > Sent: 1. oktober 2003 12:16
> > To: forrest-dev <at> xml.apache.org
> > Subject: i18n in Forrest
> >
> >
> > Hi all
> >
> > Here is a norwegian translation for the fresh-site menu.
> >
> > I still have problem seeing the strategy for translating a whole site
(Continue reading)

Juan Jose Pablos | 3 Oct 2003 03:43

Re: i18n in Forrest

Konstantin Piroumian wrote:
> 
> Though, I have no idea how to check this. Anybody knows how to switch the
> language on Forrest site?
> 

on the bug there is a reference:
http://issues.cocoondev.org/jira/secure/ViewIssue.jspa?key=FOR-18

add project.i18n=true to forrest.properties
run:

forrest seed
forrest run

After that you need to change your language settings on your browser, 
for more info:

http://www.debian.org/intro/cn

Cheers,
Cheche

Konstantin Piroumian | 3 Oct 2003 09:31
Picon
Favicon

Re: i18n in Forrest

From: "Juan Jose Pablos" <cheche <at> che-che.com>
> Konstantin Piroumian wrote:
> >
> > Though, I have no idea how to check this. Anybody knows how to switch
the
> > language on Forrest site?
> >
>
>
> on the bug there is a reference:
> http://issues.cocoondev.org/jira/secure/ViewIssue.jspa?key=FOR-18
>
>
> add project.i18n=true to forrest.properties
> run:
>
> forrest seed
> forrest run

Ok, I'll try.

>
>
> After that you need to change your language settings on your browser,
> for more info:
>
> http://www.debian.org/intro/cn

Won't adding a 'locale=ru' parameter switch the language? AFAIR, you are
using LocaleAction in menu.xmap, which looks for a parameter first and then
(Continue reading)

Juan Jose Pablos | 3 Oct 2003 11:43

Re: i18n in Forrest

Konstantin Piroumian wrote:
> 
> 
> Won't adding a 'locale=ru' parameter switch the language? AFAIR, you are
> using LocaleAction in menu.xmap, which looks for a parameter first and then
> everything else.
> 

Yes it does, this is the order from o.a.c.acting.LocaleAction.java:

Request CGI parameter "locale"
Session attribute "locale"
First matching Cookie parameter "locale"
within each cookie sent with the current request
Locale setting of the requesting object

(in the case of language, if the above cases do not yield a valid value
the locale value of the server is used)

Cheers,
Cheche

Konstantin Piroumian | 3 Oct 2003 13:34
Picon
Favicon

Re: i18n in Forrest

From: "Juan Jose Pablos" <cheche <at> che-che.com>
> Konstantin Piroumian wrote:
> >
> >
> > Won't adding a 'locale=ru' parameter switch the language? AFAIR, you are
> > using LocaleAction in menu.xmap, which looks for a parameter first and
then
> > everything else.
> >
>
> Yes it does, this is the order from o.a.c.acting.LocaleAction.java:
>
>
> Request CGI parameter "locale"
> Session attribute "locale"
> First matching Cookie parameter "locale"
> within each cookie sent with the current request
> Locale setting of the requesting object
>
> (in the case of language, if the above cases do not yield a valid value
> the locale value of the server is used)

Cheche,

you are describing me the behavior of LocaleAction, but what I was asking is
why it doesn't work in Forrest? Maybe I am doing something wrong. I'll try
to start from scratch and see if it will work this time and will let you
know about the results.
(BTW, just take a look at the authors of LocaleAction at
http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/acting/LocaleAction.html
(Continue reading)

Juan Jose Pablos | 3 Oct 2003 16:30

Re: i18n in Forrest

Konstantin Piroumian wrote:
> you are describing me the behavior of LocaleAction, but what I was asking is
> why it doesn't work in Forrest?

I do not know because it does work for me.

I am using debian 3.0 mozilla 1.2 JDK 1.4

Jeff Turner | 1 Oct 2003 12:56
Picon
Favicon

Re: i18n in Forrest

On Wed, Oct 01, 2003 at 12:15:35PM +0200, Sten Aksel Heien wrote:
> Hi all
> 
> Here is a norwegian translation for the fresh-site menu.
> 
> I still have problem seeing the strategy for translating a whole site 
> - have multiple languages for one site.

Me too :)  Any volunteers for explaining how it works now, how it will
work eventually, and how we get from here to there?

--Jeff

> 
> Pointers needed :-)

Juan Jose Pablos | 3 Oct 2003 04:38

Re: i18n in Forrest

Jeff Turner wrote:
> Me too :)  Any volunteers for explaining how it works now, how it will
> work eventually, and how we get from here to there?
> 

out of bug #FOR-18 seems to me that we could aggree on this:

1) Eventually forrest provide translated content for the content that 
comes from forrest (copyright notice, some tags and stuff)

2) Menus,tabs could be provide by forrest but allow to overwrite by users

3) You have one XML source file per language

We will start by 1 and 2
A) Use catalogs for xsl:text output that belongs to forrest 
(menu,tabs,footer)

I am not sure if we will be using the lables of a keyword to find the 
translation e.g.

<my-page label"My label" />

if I use "My label" as the translation key, that key is case sensitive 
and "My label page" could have same meaning on that context.

If I use my-page as the translation key then I have not got access to 
the information displayed to the user that could be "Cool Label" and the 
translation could be wrong.

(Continue reading)


Gmane