Problems with the Create Content item list translations

By jackdaw on 23 Jan 2007 at 20:15 UTC

I have imported a homebrew (Faroese) translation on two different Drupal 5.0 sites, and notice that content type names and descriptions are not translated on the 'node/add' page'. But the funny thing is, that they are not the same names and description that are missing (or not) on both sites.

Site 1 translates 'Book page', 'Forum topic' and 'Poll' but not 'Blog Entry', 'Story' and 'Page'
Site 2 translates 'Blog Entry' and 'Forum topic' but not 'Book page', 'Poll', 'Story' and 'Page'

The sites are brand new, and set up pretty much in the same way. Maybe I enabled the modules in different order, or waited with enabling some module until after importing the .po files. But all in all, they are very similar, and I imported the same .po files to both sites.

The missing translations did not show when I used the '/admin/settings/locale/string/search' page. I tried importing the .po files again, but that didn't help.

So my fast fix was to translate them again via the '/admin/content/types' page. But that broke the English localization: When I switch back to English, the content type names and descriptions that I translated manually are now shown in Faroese.

Also, now my Faroese strings show up as untranslated English strings when using the '/admin/settings/locale/string/search' page.

What am I doing wrong? And more importantly, how do I clean up this mess? Is there a way that I can get back to scratch (having a clean English only version) without having to reinstall Drupal?

Comments

3rd attempt went slightly better

jackdaw commented 23 January 2007 at 22:02

I tried installing Drupal 5.0 again, on a subdomain, enabled all modules except legacy and then imported the translation files.

This time, all content type names and descriptions are translated except concerning 'Story' and 'Page'.

I imported the system-install.po once more (since that is where the Story and Page names and descriptions are mentioned), without luck.

The content type names and descriptions look identical to me, when comparing the relevant strings in the system-install.po-file with the descriptions found via the 'admin/content/types' page, and in the 'note_type' table using phpMyAdmin.

4th attempt

jackdaw commented 24 January 2007 at 11:38

I have now tried to install Drupal 5.0, enable only the Locale module, import my .po-files, and then swith to the new language. Again, 'Story' and 'Page' names and descriptions are not translated on the 'node/add' page'.

I then tried to enable all other modules except Legacy, and as in 3rd attempt, everything gets translated except the 'Story' and 'Page' names and descriptions.

Following these guidelines: http://drupal.org/node/53863 ("Some strings are not translated"), I can rule out at least cause 1 and 2.

The imported translation is not complete [yes it is, if I'm right that they are translated in system-install.po]
You might need to update the PO file from a fresh POT file [ok, didn't help]
There are end-of-line inconsistencies between the actual source strings and the source strings from the PO file [ehh, I don't now, doesn't seem to be any end-of-line code in these particular strings]

I think that I can now rule out, that it has got anything to do with modules being enabled or not (since I deliberately tried to do things differently in this 4th attempt). Still, different strings are also not translated in first two attempts.

Maybe it has something to do with the modules having been used, before translation?

Original locale replaced ?

jackdaw commented 4 February 2007 at 23:51

Ehh, it wasn't quite as simple as mentioned in 3rd and 4th attempt. I didn't realize until today that, yes, 'story' and 'page' do not get translated to Faroese when I choose Faroese language, but also 'blog entry', 'book page' and 'poll' do get translated to Faroese when I choose English :-/

But ok, I think that I have found a solution for half of the problem ...

Surfing the MySQL tables with phpMyAdmin, I realized that the names and descriptions (plus title_labels and body_labels) in the 'node_type' table had been replaced by Faroese versions, in all cases except the above mentioned non-translating 'page' and 'story' node types.

If I replaced these with the original English versions, the 'node/add' page now shows English names and descriptions when English locale is selected, but unfortunately also in when Faroese locale is selected. Except concerning 'Forum topic', which now shows perfect English in English and Faroese in Faroese.

Again looking in the 'node_type' table, I see that all records except the 'Forum topic' record are set to be 1 in 'modified. If I change this to 0 (zero), everything works fine except 'page' and 'story', which are still shown in English when using the Faroese locale.

Not only Faroese

jackdaw commented 27 January 2007 at 15:53

I imported the Swedish translation files, just to see if there was something special wrong with my Faroese translation files. But no, I get the same error with Swedish, with 'Story' and 'Page' names and descriptions not being translated on the 'node/add' page.

You found a bug

Gerhard Killesreiter commented 29 January 2007 at 00:14

http://drupal.org/node/113652

Same with Spanish translation

metabits commented 2 February 2007 at 23:05

Hi,

I have the same problem with the Spanish translation. Although in the es.po the strings for 'Create content' 'Page' and 'Story' are translated, they don't show translated when I switch to Spanish, they are still in English.

How can I fix it?

(I am newbie! very, very newbie... indeed)

Same with French translation

mediameriquat commented 22 March 2007 at 21:54

Yeah, this is exactly what happens with the French translation as well. Quite annoying. This didn't happen with the 4.7 version.

What that means is Drupal is not quite useable for government jobs where strict language guidelines must be followed.

Dutch trans has the same problem

Sebastiaan Brozius commented 15 April 2007 at 09:38

The Dutch-translation has the same problem as the other languages named in this thread...

:-(

Any chance for a fix??

I have the same problem

BuDDy commented 30 April 2007 at 10:56

It seems CCK module will not work in harmony with Local module. I can reproduce this problem as soon as I enable another language in localization settings. Image and Forum items however, can be translated without problem.

Hope this thread will bring some attentions of these core module developers.

Same thing with Finnish

eneva commented 19 July 2007 at 05:04

Just ran into the same issue here myself... too bad, these are strings that a user is going to meet very early on...

Same with Chinese

JordanD commented 23 July 2007 at 07:11

...ain't it a shame? I'm going to be forced to alienate a sizable portion of my user base because of this. What are the chances a new version will be written to handle CCK?

It's not a bug, it's a feature :-)

zirvap commented 26 July 2007 at 15:48

I had the same problem, and found that it's a known issue: "Story" & "Page" Translation Problems. If I understand the reply there correctly, this isn't a bug, it's a feature :-) Or at least, the problem can't be solved by an easy bugfix.

Since I'm happy with a monolingual non-English interface, I solved the problem by going to administer > content types > story and administer > content types > page and changed the names and descriptions there. If you need to be able to switch between two different languages, I suppose you'll need to do as suggested in the reply to the issue, and install i18n or localizer module.