Is it right, that when creating new content types, all fields/data (Name, Type, Description) must be given in the native language at first? If so, this should be mentioned somewhere on the create content type form.
Here is my current work flow for translating content type (meta data).
1. create a new content type by filling out all form fields in the native drupal language (English).
Example: I want to create a content type 'Holiday Flat'
- human-readable name: Holiday Flat
- machine-readable name: holiday_flat
- description: This content type can be used to create a page representing the information about a holiday flat.
- Title field label: Name
- Body field label: Detailed Description
2. Next I want to translate the human-readable name, the description, the title field label and the body field label to a second language (e.g. German). I go to /admin/build/translate/search to look for the strings I just entered when I created the content type. But no results are found! So I have to visit the page with the create form for the new content type at least once in the second language (/de/node/add/holiday-flat). Now I am able to supply the translations. But there are lots of places in Drupal where those translations do not work:
Here are the pages where translations are not working correctly, yet:
1. /de/admin/content/types (see screenshot attachment 1)
In the table which lists the content types, just the table headline is translated to German. The values of the existing content types for the three columns (Name, Type, Description) are not translated and still shown in English.
2. /de/node/add (see screenshot attachment 2)
On this overview page, the human-readable name is correctly shown in German, but the description is still shown in English, although there is a German translation for the description
3. /de/node/add/holiday-flat (see screenshot attachment 3)
The Title of the page is not translated. The field labels for Title and Body are not translated.
4. /de/admin/content/node (see screenshot attachment 4)
On this overview page, the content type is not translated in the table and in the filter selection box.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | contenttypes-vi.jpg | 73.03 KB | oliver huynh |
| #11 | contenttypes-en.jpg | 85.18 KB | oliver huynh |
| #8 | add-title-fix-206272-8.patch | 718 bytes | pwolanin |
| #2 | node-type-plain.patch | 579 bytes | gábor hojtsy |
| translation4.jpg | 98.17 KB | yojoe |
Comments
Comment #1
gábor hojtsyThe general mantra is that Drupal translates built-in interface text (you know when you go to the locale translation interface you searh in the 'built-in interface' group), and you know what you entered is definitely not built-in, so it should not be there. With this in mind:
1. Yes the table headlines and action links are part of the interface, what you entered is not.
2. If the content type name is translated there than *that* is a bug.
3. Expected, these are user provided data and not built-in.
4. Again, expected.
User provided data is not translated in Drupal 6, except posts with the content translation module. Menus, taxonomy, content type details, user profile field labels, etc. are not translatable.
So we have the (2) as a bug, where the node type name *is* translated. Retitling for that.
Looked into this bug and noticed that:
- node/add is hooked to node_add_page() in node.pages.inc
- node_add_page() gets the menu item and uses system_admin_menu_block() with that
- system_admin_menu_block() from system.module uses _menu_link_translate() on the links
- _menu_link_translate() calls the title callback for the menu item
- so back to node.module, which adds the menu items for all content types
- solution: node_menu() should tell the menu that no title callback should be invoked
I tried to look up nice looking examples about this in core, but could not find one.
Comment #2
gábor hojtsyActually, since this is user provided data, we should check_plain() it, as other menu item titles are check_plain()-ed. Committed this simple fix. Otherwise, as discussed this issue is 'by design'.
Comment #3
yojoe commentedIt was my big hope, that this is finally possible with Drupal 6. Are there plans to implement this for Drupal 7? Or will it be possible to translate field labels with 3rd-Party localization modules (i18n, localizer)?
Comment #4
gábor hojtsyYes, locale module is ready to support translation of these kinds of strings with a contributed module. I have seen screenshots of i18n module for Drupal 6 using the "text groups" feature to translate these kinds of strings (you know it adds more text groups additionally to the built-in interface, so you can translate these strings). Although we tried to push hard in the D6 cycle to have this in core, we did not have a compelling solution to do it, and it was better not to screw this up, but postpone instead. There is plan to include this feature in Drupal 7.
Comment #5
yojoe commentedIs there a thread I can join to post my ideas?
Comment #6
gábor hojtsySure, check out http://drupal.org/node/141461
Comment #7
pwolanin commentedthis fails on node/add/page (etc) with:
warning: Missing argument 1 for check_plain()Comment #8
pwolanin commentedoption #1 - we don't need any callback. This is fine because the page title is already set in the callback function:
http://api.drupal.org/api/function/node_add/6
Comment #9
pwolanin commenteddoh - this is actually a menu bug: http://drupal.org/node/206510
Comment #10
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #11
oliver huynh commented"Remember to remove duplicate entry at search result in Translate Interface".
I've already fixed this using no patch.
Comment #12
Ishus Media commentedI really believe all 4 are bugs and are UN-expected. Wonder why no solution is provided ^^
Comment #14
Ashraf Amayreh commentedSame problem in Drupal 7. All content type names in node/add are passing through check_plain rather than t(). How is this the correct behavior and how do you translate these menu items on the node/add page without hacking core?
Comment #15
gábor hojtsy@ominds: Drupal core does not let you translate node type names. Look into the i18n module.
Comment #16
Ashraf Amayreh commentedI'm using the i18n menu translation. I already have all menus translated. As to content type, I can't see anything in i18n that would allow me to translate content type names. But this issue might be related:
http://drupal.org/node/1340968
I just posted a follow up there to see if I'm on the right track.
Comment #17
gábor hojtsy@ominds: looking at that patch, the i18n_node module already supports node type name translation(?).
Comment #18
Ashraf Amayreh commentedAh yes. You're totally correct. "Multilingual Content" gave me the impression it had to do with content rather than structure. Some of the i18n naming system is a little confusing to me.