I'm having a problem with translating. Everything works just fine, but not when you move in to an empty section and have the option to "Start one?" or "Upload now" and similar.
See the attached images to understand.
This should be easy, but I simply can't find the problem.
Any ideas?
It is possible that the values are overridden. Please check other dictionaries and make sure that there are no occurrences of the same phrase that are not translated.
Thanks. but thats not likely the problem. I have looked trough each and every dictionary thats been translated, and there are no empty fields where the words involved are not translated.
So I figure it might be some sort of php "lang" issue on those pages involved. But I'm not a php professional so I don't want to mess around with wild guesses.
And it seems to be the same problem when using other translations. I have installed French, but it's the same problem.
For example when there is no existing page under page section, "Create a new page now" is displayed even though French is the choosen language.
We can't can't solve this translation issue.
Does anyone have an idea what the problem could be or have the same problem.
The reason we think it's caused by AC and not the translation is that the same problem exists in other languages.
See attached images, french and german language.
We imported these languages as xml, and they have the same problem.
It's possible that the problem is with dictionary builder tool that we use to extract list of phrases from templates and other files. We'll check it out and see to have it fixed in the upcoming bug fix release.
Hi Lilja, I think I also have the same problem but I want to make sure that Im not missing out some actions regarding the localization.
First, in the administration > Languages > English > (Translation Files) Pages > edit.
All the dictionary word/sentence, have corresponding values and replaces the 'Page' to 'Brief'. I clear my cache & compile folder, clear my browser's cache as well but the 'Page' word didn't changed.
Did I miss out here? Or is this a bug in the Localization? Thank you!
Do you have all the other modules localized, especially system, resources and milestones? Can you please outline places in the interface where Page was not properly localized?
Suggestion:
If you are sure to have all fields translated, export it as XML and import the same file in your system.
For some reason some words that wasn't translated earlier now showed correctly.
We didn't look in to why, but it worked.
But the problems I stated earleir we can't solve, regardless of this.
We'll wait for 3.0.
See the attached images to understand.
This should be easy, but I simply can't find the problem.
Any ideas?