Sjur Moshagen wrote:
[WARNING - long e-mail]
(not any more ;-)
This is a lot of work, and I will not be able to do all of this, both in
terms of time and knowledge. The first question is easy enough though:
WDYT?
The solution to the first three use cases involves a value in a session.
T
[WARNING - long e-mail]
Den 26. sep. 2006 kl. 12.37 skrev Ross Gardler:
This brings me back to the idea of using the locationmap for locale
matching rather than Cocoons components, which have their problems
in our use case. Something like (be warned, I've not fully thought
this through and
On Tue, 2006-09-26 at 14:49 +0300, Sjur Moshagen wrote:
> Den 26. sep. 2006 kl. 12.37 skrev Ross Gardler:
>
> >> I can open http://localhost:/index.en.html and have my page in
> >> English. The problem with this solution is that it does not work
> >> nicely in a webapp environment (e.g. fo
Den 26. sep. 2006 kl. 15.00 skrev Thorsten Scherler:
Using the locationmap is fine, but not until content negotiation is
working.
Just want to remark that the LocaleAction should as well work in
the lm.
Thanks for pointing it out - whatever can be done to make both the
webapp and the CL
Den 26. sep. 2006 kl. 12.37 skrev Ross Gardler:
I can open http://localhost:/index.en.html and have my page in
English. The problem with this solution is that it does not work
nicely in a webapp environment (e.g. forrest run), because this
locale encoding does not communicate with the l
Sorry, sluggish/no internet connection and lots of work, prevent me to
be a bigger help.
some remarks:
On Tue, 2006-09-26 at 08:56 +0300, Sjur Moshagen wrote:
> Den 25. sep. 2006 kl. 17.17 skrev Gav:
>
> >> 3) when doing a forrest seed, the translation files in whiteboard/
> >> plugins/o.a.f
Den 26. sep. 2006 kl. 10.34 skrev Ross Gardler:
Does this new i18n solution require a ?locale=xx in the URL in any
situations? If so then this is not a good solution. It will break
the static build of the site since "?" is not a valid character in
filenames, Cocoon therefore encodes this wh
Sjur Moshagen wrote:
Den 26. sep. 2006 kl. 10.34 skrev Ross Gardler:
Does this new i18n solution require a ?locale=xx in the URL in any
situations? If so then this is not a good solution. It will break the
static build of the site since "?" is not a valid character in
filenames, Cocoon theref
Sjur Moshagen wrote:
Den 26. sep. 2006 kl. 09.07 skrev Sjur Moshagen:
Den 26. sep. 2006 kl. 08.56 skrev Sjur Moshagen:
I'll try to create one super-issue and add the existing (and new)
issues as sub-issues to that one.
Hm, I received the following error message when I tried to create a
sub
Sjur Moshagen wrote:
Den 26. sep. 2006 kl. 02.14 skrev Gav:
In this case shouldn't the fallback be defined as a specific language,
i.e. English. In which case the fallback should be
"ContractsMessages_en.xml" shouldn't it (as opposed to
"ContractMessages.xml").
Sounds like the best way, h
Gav wrote:
-Original Message-
From: Ross Gardler [mailto:[EMAIL PROTECTED]
Sent: Monday, 25 September 2006 10:54 PM
To: dev@forrest.apache.org
Subject: Re: Dispatcher i18n update + three more issues
Gav wrote:
2) There should probably be a default/fallback
Den 26. sep. 2006 kl. 09.07 skrev Sjur Moshagen:
Den 26. sep. 2006 kl. 08.56 skrev Sjur Moshagen:
I'll try to create one super-issue and add the existing (and new)
issues as sub-issues to that one.
Hm, I received the following error message when I tried to create a
sub-task to my newly cr
Den 26. sep. 2006 kl. 08.56 skrev Sjur Moshagen:
I'll try to create one super-issue and add the existing (and new)
issues as sub-issues to that one.
Hm, I received the following error message when I tried to create a
sub-task to my newly created super-issue http://issues.apache.org/
jira/b
Den 25. sep. 2006 kl. 17.17 skrev Gav:
3) when doing a forrest seed, the translation files in whiteboard/
plugins/o.a.f.plugin.internal.dispatcher/messages/ should be included
in the src/documentation/translations/ directory, with a proper note
on them being useful only with the dispatcher.
Den 26. sep. 2006 kl. 02.14 skrev Gav:
In this case shouldn't the fallback be defined as a specific
language,
i.e. English. In which case the fallback should be
"ContractsMessages_en.xml" shouldn't it (as opposed to
"ContractMessages.xml").
Sounds like the best way, haven't tested Sjurs
> -Original Message-
> From: Ross Gardler [mailto:[EMAIL PROTECTED]
> Sent: Monday, 25 September 2006 10:54 PM
> To: dev@forrest.apache.org
> Subject: Re: Dispatcher i18n update + three more issues
>
> Gav wrote:
>
> >> 2) There shou
Gav wrote:
2) There should probably be a default/fallback ContractsMessages.xml
file, which should really be the file above (ie the English one, if
one wants to have English as the fallback language, which I expect
one does). Not having one will at least cause some noise in the log
files, an
> -Original Message-
> From: Sjur Moshagen [mailto:[EMAIL PROTECTED]
> Sent: Monday, 25 September 2006 8:20 PM
> To: dev@forrest.apache.org
> Subject: Dispatcher i18n update + three more issues
>
> Hello all,
>
> AS seen in JIRA, I have found a set of errors
Hello all,
AS seen in JIRA, I have found a set of errors in Dispatcher and
Forrest regarding i18n, and submitted patches for them. With those
patches, Dispatcher should be ready to go re i18n - almost:-) There
are still three more issues for which I can't submit a patch (I think):
1) one
19 matches
Mail list logo
