gplana
asked on
language configuration on Joomla
Dear Expert:
I would like to create a multi-lingual Joomla web-site, so I will use Joomfish.
The problem is: I think Joomfish choose language based on the browser language, but we want to choose language based on the domain, that is, if you enter from www.ourdomain.com we want english, if you enter from www.ourdomain.fr we want french, if you enter from www.ourdomain.es we want spanish, and so on.
Is this configuration possible ?
I would like to create a multi-lingual Joomla web-site, so I will use Joomfish.
The problem is: I think Joomfish choose language based on the browser language, but we want to choose language based on the domain, that is, if you enter from www.ourdomain.com we want english, if you enter from www.ourdomain.fr we want french, if you enter from www.ourdomain.es we want spanish, and so on.
Is this configuration possible ?
ASKER
Thank you for your answer, but my question is: when a user access to main domain (something like www.freeworldfoundation.org), I think Joomla redirect to the more appropiate language based on the browser language. I would like to know if Joomla can be configured to show language based on domain instead of based on browser language.
The structure would be the same for all language. Just the text would be different translations of the same content.
The structure would be the same for all language. Just the text would be different translations of the same content.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If not, then you could set up permanent redirects from domain.fr to domain/fr to achieve easily what you say you want.
To me the issue is how you will control your content translation process. JoomFish facilitates this dynamically - when a new or changed original language content item is published then this highlights as needing translation work for the other languages. This works when all the content (including translations) is in the one content database - easier if this is on the one master domain. Having separate language domains would make more intuitive sense if the structure and content of the domains was intended to differ by language - but would probably need a different workflow process and tool.