Hi,
I tested the i18n features of forrest-0.7-dev
- made a new dir
- fresh forrest seed
- turned forrest.i18n on
- added index_es.xml to .../xdocs/
- (menu_es.xml, languages_es.xml, tabs_es.xml in distro)
- index.xml file was renamed index_es.xml
modified index_es.xml to display some Spani
Hi,
It doesn't make sense to have to add this:
modify cli.xconf and add this line:
if you are in a live web environment - if you need mulitiple languages.
If forrest.properties setting is project.i18n=true,
and a user-client browser is language n,
is it only that we need to create all the ca
Finally,
Does anything in this cocoon info page need to be implemented?
http://cocoon.apache.org/2.1/userdocs/i18nTransformer.html
thank you,
helena
Helena Edelson wrote:
Helena Edelson wrote:
Hi,
I tested the i18n features of forrest-0.7-dev
- made a new
Hi,
first of all:
Our site at http://www.verit.de is already running in i18n-mode
(currently only de and en is supported) using the servlet approach and
dynamic language detection using forrest 0.7.
I think from your description you are almost there:
- Setting project.i18n=true in forrest.p
With things as they are now in my
test, if my browser is on language n, the document (lang n) is served
but I haven't gotten it to also to tabs and menues yet I see on other
forrest sites it is working so I think I'm missing one thing.
In my initial test I used the file naming conv index.es.xm
Helena Edelson wrote:
With things as they are now in my test, if my browser is on language n,
the document (lang n) is served but I haven't gotten it to also to tabs
and menues yet I see on other forrest sites it is working so I think I'm
missing one thing.
looking at your post again - it i
I have tabs_(lang-code).xml and
menu_(lang-code).xml
for each language, yet still the index.(lang-code).xml is the only one
returned.
Could my issue lie perhaps in the translations/langcode.xml file?
I added de,fr,no to what is in the distribution yet even with my
browser in de, still no luck w
Helena Edelson wrote:
I have tabs_(lang-code).xml and menu_(lang-code).xml for each language,
yet still the index.(lang-code).xml is the only one returned.
Could my issue lie perhaps in the translations/langcode.xml file?
I don't think so, nothing unusual over here.
I added de,fr,no to what
Torsten Stolpmann wrote:
- In contradiction to the documentation try naming your web pages
index.es.xml instead of index_es.xml. We got that from studying the
error logs closely and suspect the documentation is plain wrong here.
Can someone from the dev team comment on this? We also renamed our
Helena Edelson wrote:
I have tabs_(lang-code).xml and menu_(lang-code).xml for each language,
yet still the index.(lang-code).xml is the only one returned.
Could my issue lie perhaps in the translations/langcode.xml file?
I added de,fr,no to what is in the distribution yet even with my browser
Helena Edelson wrote:
embarrasing question: Is it the case that if we want multiple languages
to be supported, we have to supply the
translations per document page? Nothing will automatically translate for
the app like how the online
translation engines do it? Would be great to plug something li
11 matches
Mail list logo
