[
http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12360960 ]
helena commented on FOR-506:
The catalogue file can it support mutliple languages or
one cat file per language:
catalogues
catalogue
message key=/message
/catalogue
catalogue
[
http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12360964 ]
helena commented on FOR-506:
Excuse my initial comment - slopy wording.
In the patchI18n.diff file, the nesting is not clear:
map:generator name=text2xml
[
http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12317756 ]
David Crossley commented on FOR-506:
Some html validation issues ...
Re: FOR-592 - pelt and i18n clarifications
http://marc.theaimsgroup.com/?t=11231601642
Do not
[
http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12313425 ]
David Crossley commented on FOR-506:
Thanks, would you please do an 'svn update' and verify that the accented
character is okay. Subversion reported conflicts for other
Cordialement,
Cyriaque,
David Crossley (JIRA) a crit :
[ http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12313425 ]
David Crossley commented on FOR-506:
Thanks, would you please do an 'svn update' and verify that the accented
Cyriaque Dupoirieux wrote:
David Crossley wrote:
Thanks, would you please do an 'svn update' and verify that the accented
character is okay.
It's Okay,
Subversion reported conflicts for other reasons, so i applied it by hand.
Also i tweaked it to be consistent with the others. I we
Pedro I. Sanchez wrote:
I can not reproduce this. Forrest site works for me.
Are you on Linux or Windows?
debian 3.1
I don't understand. How can it work for you?
how can it does not work for you?
This line in sitemap.xmap is the one that determines the catalogue to
use and as you can
Pedro I. Sanchez wrote:
The string $(env.LANG} works well inside main/forrest.build.xml. It was
the default before you made changes to the trunk. But the same string is
ignored when you use it inside webapp/sitemap.xmap (skin labels are
looked up in the English dictionary, even if LANG=es_ES).
On Thu, 2005-09-06 at 12:56 +0200, Juan Jose Pablos wrote:
Pedro I. Sanchez wrote:
The string $(env.LANG} works well inside main/forrest.build.xml. It was
the default before you made changes to the trunk. But the same string is
ignored when you use it inside webapp/sitemap.xmap (skin labels
On Wed, 2005-01-06 at 12:02 +0200, Juan Jose Pablos wrote:
Pedro I. Sanchez wrote:
Anyway, first I verified that setting value=es_ES in
main/webapp/sitemap.xmap indeed works. It brings the Spanish strings
from the right catalogue. I also verified that value=${env.LANG} does
*not* work.
[
http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12312725 ]
Cyriaque Dupoirieux commented on FOR-506:
-
Hi,
If someone creates an empty CommonMessages_fr.xml, I'll send a french
patch...
Do not hard-code site-visible
[
http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12312807 ]
Thorsten Scherler commented on FOR-506:
---
I just did a copy of the english one and renamed to _fr.
BTW you could have done that yourself by:
cp CommonMessages_us.xml
On Sun, 2005-05-06 at 14:04 +0200, Thorsten Scherler wrote:
This is key for me. If I cannot specify the language when I run
forrest to build my site then this is not a good solution. I guess the
other option would be to hard-code value=es_ES in the above. At least
this would be just one
On Sat, 2005-06-04 at 23:03 -0400, Pedro I. Sanchez wrote:
On Sun, 2005-05-06 at 04:19 +0200, Thorsten Scherler wrote:
On Sat, 2005-06-04 at 20:55 -0400, Pedro I. Sanchez wrote:
snip/
My version of the Spanish messages would be the following:
catalogue
message key=Font
Pedro I. Sanchez wrote:
On Sun, 2005-05-06 at 04:19 +0200, Thorsten Scherler wrote:
On Sat, 2005-06-04 at 20:55 -0400, Pedro I. Sanchez wrote:
...
Nice, can you prepare a patch and add it to this issue? I will apply it
then, thx. I reckon there are more to come. ;-)
Index:
[
http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12312633 ]
Ross Gardler commented on FOR-506:
--
When this issue is complete the FAQ How can I internationalise (i18n) my
content? needs updating.
Do not hard-code site-visible message
On Sat, 2005-04-06 at 06:06 +0200, Thorsten Scherler (JIRA) wrote:
[
http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12312612 ]
Thorsten Scherler commented on FOR-506:
---
The patch enables i18n support for forrest. Mainly it is
Pedro I. Sanchez wrote:
On Sat, 2005-04-06 at 06:06 +0200, Thorsten Scherler (JIRA) wrote:
[ http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12312612 ]
Thorsten Scherler commented on FOR-506:
---
...
So what we need is that
1) we
On Sat, 2005-04-06 at 23:49 +0200, Thorsten Scherler wrote:
On Sat, 2005-06-04 at 21:36 +0100, Ross Gardler wrote:
Pedro I. Sanchez wrote:
On Sat, 2005-04-06 at 06:06 +0200, Thorsten Scherler (JIRA) wrote:
[
On Sat, 2005-06-04 at 20:55 -0400, Pedro I. Sanchez wrote:
snip/
My version of the Spanish messages would be the following:
catalogue
message key=Font size:Tamaño del texto:/message
message key=Last Published:Fecha de publicación:/message
message key=SearchBuscar/message
message
On Sun, 2005-05-06 at 04:19 +0200, Thorsten Scherler wrote:
On Sat, 2005-06-04 at 20:55 -0400, Pedro I. Sanchez wrote:
snip/
My version of the Spanish messages would be the following:
catalogue
message key=Font size:Tamaño del texto:/message
message key=Last Published:Fecha de
[
http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12312612 ]
Thorsten Scherler commented on FOR-506:
---
The patch enables i18n support for forrest. Mainly it is focus right now on the
i18n support for skins (in particular pelt).
The
The following comment has been added to this issue:
Author: Cyriaque Dupoirieux
Created: Thu, 26 May 2005 11:12 AM
Body:
Excellent, but I don't think it's a minor problem.
My own skin - originally based on pelt - is now far from the original one
generally for translation reason.
The following comment has been added to this issue:
Author: Ross Gardler
Created: Thu, 26 May 2005 11:50 AM
Body:
Can you describe what you think the problem would be with this propsed solution
of extending skinconf.xml?
For example:
i18n lang=en
token name=lastPublished
The following comment has been added to this issue:
Author: Pedro I. Sanchez
Created: Thu, 26 May 2005 2:26 PM
Body:
Couple of comments:
1. It could work, but for me to test it I would like to get clarification on
two things:
a) How do you enable the i18n .. /i18n thing to
The following comment has been added to this issue:
Author: Ross Gardler
Created: Thu, 26 May 2005 2:48 PM
Body:
My question was to it was to Cyriaque who said your proposal was not
sufficient. I was asking why and adding details to the proposal.
But since you ask for more info
26 matches
Mail list logo
