I've been using Drupal 4.6.3 with several modules, and doing a custom Greek translation. Here's what happened:
I exported a .po file. While translating, I made a mess by replacing parts of some English strings with Greek strings. I didn't notice, I imported it back, and everythings seemed to work ok...
Later on, I exported the .po again to make some corrections to the translation of the gsitemap module. What I found was that translating the correct English strings had no effect. I had to keep translating the garbled ones!
Now, the situation is this:
- When the site is displayed in English everything is ok (it seems that the English strings used are not the ones called "original" in the localization page).
- When the site is displayed in Greek everything is also ok.
- Whenever I want to edit a translated string I have to find and translate not the correct English sting, but the garbled one, which appears as "original" in the localization page.
(BTW, I also noticed that my Greek taxonomy terms also appear as "original" ones in the localization page, and I am offered the option to "translate" them to Greek.)
I can't find the garbled strings in the database because they are blobs. Any pointers to a doc explaining how the locale works with the database? Any other way out of this? What if I empty the "locales_target" table and import the .po again without the garbled strings? Will it work?