17 Jul
2007
17 Jul
'07
6:08 a.m.
Konstantin Käfer wrote:
This is a known issue.
Here is why this happens:
On installation time, the content types are created and insert into the database (starting with Drupal 5, we don't have hardcoded content types as default setting). Unfortunately, the language pack was not installed on install time, so the translation was not available.
This will change in Drupal 6.
To be precize, the behavior is very similar in Drupal 6, just that it starts off with a screen asking the user to download a language pack, if English is not the desired target language. Content type names are not translatable beyond the installer still (unfortunately).
Gabor