Posted by manveru on July 9, 2008 at 4:18pm
Jump to:
| Project: | Localizer |
| Version: | 5.x-3.6 |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
When I turned the contact module on after localizer module there is no way to translate "Contact" term from menu to word in other language. But when I do it manually in the database - it starts working. Problem with that is probably localizer does not have sanity checking of what from menu is translated and what is not.
I put this as a bug because I see it as a missing feature in "Localizer strings translation" panel, where should be administrative section added with button "Find strings to translate".
Anyway you've don great job with localizer. I get 5.7 Drupal for new project only because there is no localizer for Drupal 6 (yes, yes... I know the story, but maybe you create module functionally similar for 6?).
Comments
#1
This may be connected with #234985: Problem with Localizer strings translation.
#2
I have the same problem in my site. All the menu items seem to be translatable except for the "Contact" item. Could you explain how you did it manually in the database to work?
Thanks in advance.
#3
Methinks this is rather a known issue of the Contact.module, not only limited to Localizer, as it also fails to translate with any i18n modules still in D6.
There are two solutions for Drupal 6 that I could find, the former is more complete than the latter:
A) Install the tcontact module. This will give you translatability for not only the menu item, but also the text on the page (discussed here [#83514].
B) Disable the default contact menu item provided by the contact.module, and create your own (either one for each language or use i18n menu translations to translate a single one from the default lang to all the others).
I hesitate to move this to the drupal issue queue, because i dont know that either of these solutions actually 'fix' the issue for the Localizer or not (since i don't use that module or D5). I just found this thread, and am offering suggestions on how you might get around it.