Missing FR translation in User Management Grid in PIM 1.0.1 about pim-community-dev HOT 9 CLOSED

Hello Sylvain,

You can download a fresh language pack here https://crowdin.net/download/project/akeneo.zip then extract and copy the Fr folder content in our app/Resources (you can remove all app/Resources/Oro*Bundle).

Then 'php app/console --env=dev --task=assets --force' and 'php app/console cache:clear --env=dev' (if in prod mode, change the env option to prod and restart the apache to be sure to clear the APC cache).

Thank you to let me know if it's ok after that.

from pim-community-dev.

hmm, pity, no way. I followed your instruction except the command 'php app/console --env=dev --task=assets --force' which has no effect or seems thats something is missing. Are you sure about the command?

In fact it's even worse, all strings show keys instead to have the FR translations. Maybe I did something wrong cause of the command. I tried other command like 'pim:installer:assets' and 'assets:install'

You will see below the structure of the resource folder and the consequences. FYI, in the FR crowdin package there is no Oro*Bundle translation

Your demo on akeneo.com has the same translation issue than the first post reported.

from pim-community-dev.

I forgot. I revert the changes by getting the Oro_Bundle and Pim_Bundle into the Resource folder, clear the cache and I got back all the things except the issue reported at first.

from pim-community-dev.

Ok sorry my apologies.. I have badly understood the story about the FR folder content. I expected just to drag and drop the folder FR into resources folder. I just took the bundle folders and it worked.

As I want to have multiple languages support to show the product, I expected that I do not need to copy one by one locale to a bundle.... Do you have a trick to automatize it?

Thanks

from pim-community-dev.

My bad for the command, it's php app/console pim:install --env=dev --task=assets --force :)

The demo uses the 1.0 with the embeded translations, so the same missing translations than you.

By downloading on Crowdin, you get the very last ones (1.0 compliant), BTW, we re-organized the translation package to fix this issue, that's why there is no more Oro*Bundle in the package.

from pim-community-dev.

No pb, it's not very well documented for now.

Language pack is only used to translate the UI (menu items, buttons, etc).

As the product data is dynamic (you can add new attributes, groups, families, etc) this localization is a bit different, you have to enable some locales on a channel (for instance fr_FR, de_DE, en_US on ecommerce channel), then these locales will be available to define labels of attributes, families, groups, etc (in theirs respective forms).

Don't hesitate if you need any extra information

from pim-community-dev.

Sorry, misunderstood, in this sentence "As I want to have multiple languages support to show the product" I meant show Akeneo (as a product) in multi language as I work in Switzerland I do the demo in german and french.
So I wanted to know how do you handle the install of multiple language pack on your side?

from pim-community-dev.

For now, for projects based on 1.0, to update the translations, we copy / paste for each language as you did for french.

For each PIM version, we embed the "fresh" translation pack, so, I think we'll dont have this "missing translations key" issue for the 1.1 (for languages that are 100% translated / validated when we'll release).

FYI, we have some stories in our product backlog to ease this process and also to be able to choose a different UI language per user (not doable right now), for your demo, you can update both pack and change the system > config to switch from one to another.

from pim-community-dev.

Thank you Nicolas for your feedbacks. It was interesting.

Bonne fin de journée :-)

from pim-community-dev.