SOLVED Multilingual website with J2.5 and RT template
-
-
- Quenda
- Hero Rocketeer
- Posts: 477
- Thanks: 4
- Audio-video-web freelancer. Apple hardware/software tech. support_
-
Hallo!
I'm asking advice about a strategy for a new multilingual website (Italian and English) with J 2.5.x and a RT Template (probably Hadron...).
My experience with the Rosetta component in a J2.5 website with a RT Template was so-and-so....
The component works as expected but I've spent a lot of time in the learning process and in the end the workflow is very similar to the multilingual Joomla core: in other words you must duplicate almost everything.
I've read some good reviews about Falang and now JoomFish is compatible with Joomla 2.5.x.
In my opinion the very good Igor's tutorial on multilingual websites confirm that the Joomla-core-Multilingual-system it's a very time consuming process and for this reason I consider this my last option.
Thank-you for your advice.
ettore
-
-
-
- MrT
- Preeminent Rocketeer
- Posts: 101084
- Thanks: 13484
- Web Designer/Developer
-
I don't think there is anything wrong with the standard joomla way of doing a multi-lingual site (that's what I always use). In my opinion it's much better to translate the articles/module and menu content yourself rather than having it done automatically (falang, joomfish, rosetta) and in this way you can be absolutely sure your content is correctly translated. Also, usually you do actually want to have different content for each language and again using standard joomla makes this easy and clear to set-up.
The tutorial you mentioned is not time-consuming in the set-up itself, but yes - you do have to set-up the content for each of your languages.
For the benefit of other members the tutorial you are referring too is http://www.rockettheme.com/forum/joomla-template-fracture-tutorials-and-guides/176550-multilingual-site-using-fracture-or-any-other-rt-template?start=0#869005
Regards, Mark. - Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
-
Time to create page: 0.070 seconds