Hi,
If there is no language in the URL, a search engine can't crowl
all the versions of the website.
That's why I used the solution #1 in http://www.euromapping.com
Traductions are made in smarty configurations files and a custom
translation system for technical messages (like "wrong email" for
example).
Greetings,
Philippe
--
Philippe Le Van
mail : [EMAIL PROTECTED]
web : http://www.kitpages.fr
Thomas Weidner wrote:
Well...
Our multilingual application has the language of the user within the
session...
There would be no need to have a directory structure like
/de/controller/action
/en/controller/action
a
/controller/action
would also work.
The only question you have to know yourself is, if a user should
always see which language he has from the URL displayed...
Btw:
Having identical views, one for each language is no good solution.
If you change the layout or the content you have always to change the
other languages exact the same way... unnecessary.
Greetings
Thomas
I18N Team Leader
----- Original Message ----- From: "Kevin McArthur" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, February 28, 2007 12:51 AM
Subject: [fw-general] Internationalization and the Zend Framework
I'm wondering if anyone has done a multi-lingual site using the ZF yet
and is willing to share their setup.
I'm currently developing a site for both English and Canadian French,
both output and text-input. I'm fairly well versed on the input side,
but how are you guys developing the templating side.
I'm thinking a url-based approach to en/fr content following a new
default route like ':lang/:controller/:action', then splitting the
views into two identical structures, but translated.
However, others have pointed out the xml:lang attribute, and suggested
http://www.w3.org/TR/REC-xml/#sec-lang-tag style
multiple-languages-in-a-single-file approach. Has anyone had success
at this?
Anyone want to share their setup?
Kevin McArthur
