Hi there,
First of all I should probably state that I'm not using the internationalization module. About a year ago when I added a Japanese translation to my site I chose to go without it for a number of reasons.
I manually set up Japanese paths to be prefixed with 'jp'.
I've just endabled the locale module in the hope of using it to translate instructions such as 'field is required' for forms. The Japanese language is installed and I've provided my own translations where required via the 'translate interface' feature.
My language negotiation is set to 'path refix', with 'jp' being the specfied prefix.
However....nothing seems to be happening. Nothing is translated at all.
Is this because I manually set the paths myself before enabling the locale module? Should I be seeing some indication of language when I edit a node?
Any help would be appreciated as currently this module seems to be providing me with no functionality whatsoever. Clearly I must be doing something wrong.
Thanks in advance, Richard
Comments
More info
I've noticed that all of my nodes except one are listed as being 'language neutral' in the content list. Interestingly one of them says 'English' but its URL has the 'jp' prefix which should surely indicate to the Locale module that it is Japanese.
Is this a hangover from having the internalization module installed about a year ago?
Am I right in thinking that given my 'path prefix' option the locale module is simply examining the path in order to determine if any system strings should be translated. If so....why is nothing happening?
Got it...
...I needed to enable multilingual support for my content types. I must have disabled it when I removed the internationalisation module.
So, it's working now, but I've realised that the source of my main problem with the internationalization module - the generation of duplicate pages, probably lies in the locale module. Very SEO unfriendly on a number of levels, but this should probably be the topic of another post.