I've installed a standard drupal core (6.20), set up a default english site, then added a language (Swedish) and set it to default, and finally installed and run the Localization update module. However the human readable names of the default content types (page and article) and menus (primary links, secondary links and navigation) as well as their descriptions don't get translated.

Has it been deemed too adventurous for this module to modify these strings in the database (tables node_type and menu_custom?

As it seems using this module for setting up localized sites is now the recommended method over downloading legacy translation packages directly into the core directory, this should be addressed somehow. The idea of using the localization installation profile seems like a bad idea as I seems it is not possible to use more than one installation profile.

Feel free to move this question to wherever it might belong.

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Title: Default menu names, descriptions, node types not updated » Move translation import to an earlier stage, at least for core
Project: Localization update » Localized Drupal Distribution
Version: 6.x-1.x-dev » 7.x-1.x-dev
Component: Documentation » Code
Category: support » task

The localized install profile is just a standard install profile with localization baked in. So if you'd use Drupal's built-in install profile, you should just use the localized profile instead. Also, maybe that profile runs .po file imports too late as well, but generally once those node types, etc. are in the database, they are considered user generated content, so no localization import will change them (regardless if you use the built-in Drupal interface or the localization update module).

The trick for installing Drupal localized as much as possible is to get the .po files imported early in the process. The localized Drupal profile should be modified to import Drupal core files as early as possible. It currently does the import a bit late in the install cycle. But generally, for existing installs where you put on Localization update module, the answer is what's outside the locale tables is already considered user provided data and will not be modified.

magnus’s picture

magnus commented

Related issue: #987534: Default installed vocabulary name, tags, date types, block region names, timezone locations, tabs and menus not translatable