I've a clean Drupal 6.0-beta3 install, and I'm creating spanish translation from scratch. I'm using both, Localization client and gettext po files.
When I try to translate the administer content, all moule or task description string are generated in the po file and are available in localization client, but translated content is not used. It always use the original harcoded version. It also happens at least in content type description (page and story).
I'm not sure, but could be more related error. I'll report them if i found it.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | screenshot3.png | 65.33 KB | RicardoJBarrios |
| #2 | screenshot1.png | 85.88 KB | RicardoJBarrios |
| #2 | screenshot2.png | 68.92 KB | RicardoJBarrios |
Comments
Comment #1
gábor hojtsySo does the original string gets displayed with the page and story descriptions or also elsewhere? Content types descriptions and names are user defined data, so they are not translated. So this is not a bug, but a missing feature. What else is not translated properly?
Comment #2
RicardoJBarrios commentedWhen you go to Administer, all descriptions are not translated, even when the po file contains it and are translated.
And yes, content description are user defined data, but names are translated, so, why not the descriptions if they're recognized by the translation system. If they cannot be translated, they should not appear in the po files.
I'll attach two screenshots. All english strings are in the po file, generated by Drupal and translated.
Comment #3
gábor hojtsyscreenshot2.png: this seems to be expected behavior. The type names and descriptions are only translated if these translations are available in install time. The fact that they are in whatever PO file does not mean they are translated runtime. There are PO files which are used in install time, and the strings translated with them are not passed through translation anymore.
screenshot1.png: this is quite interesting. Can you try clearing your menu cache? (In beta3 disable a module and enable it again). Then check whether this is still the case.
Comment #4
RicardoJBarrios commentedOk, if it's the expected behavior for content no problem... i'll send a feature request ;)
And for admin, I've clearing the cache. I've disabled Taxonomy and enabled it again, and it the problem persist. I've attached another screenshot.
Comment #5
gábor hojtsyHave not seen reported from elsewhere, so assume it was a beta glitch and got fixed later.