0

I am using: http://www.magentocommerce.com/magento-connect/magento-core-modules-french-language-pack.html

for the translation of my website to french. But the bottom menu is in english for some reason.

enter image description here

Why? And what can I do to change this?

  • I think that comes from a static block named footer_links. – Marius Dec 1 '13 at 7:46
  • You're right for the first part but for the second part of the footer I cannot find where I can change it. – jnbdz Dec 1 '13 at 7:57
  • I am not sure but I think I need to modify the XML files for this. Here is a link that explains in detail: magento.cc/how-to-edit-the-magento-footer-area.html – jnbdz Dec 1 '13 at 8:15
  • Is there a way to modify the language of these XML file but still have the advantage of multi-language? – jnbdz Dec 1 '13 at 8:16
  • yes, extend the original block so he puts the text trough ->__() so it uses the translate function – Flyingmana Dec 23 '13 at 21:16
3

The language packages found on the magentocommerce.com website are not always complete. MOst of them are not.

The first row of footer links come from a static block called footer_links. You can edit that in Cms->Static blocks.

The second row comes from layout files. But the texts listed there should be available in the language files. You can search for a text in the files and translate it.

I can also recommend this extension for working with translations.
Here is what it does:

  • collect texts from specified modules and generates a csv file for each module.
  • identifies the texts from a specified locale that have the same translation as the key: "Customer","Customer". Note: False positives may occur.
  • generates all the locale files for the selected modules in a specific language, by collecting the texts from the module files and merging with the already existing locale files.

Just make sure you backup your language files before using the extension...just in case.

1

Every Magento update "breaks" language package, creating tons of updated strings which while being similar to old ones have different capitalization, punctuation and whatnot. reason being that third party package maintainers are often several versions behind in the release schedule.

In your case, you also overlooked static blocks.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.