Skip to Content

Translating using POedit

Sat, 06/06/2009 - 10:50 — Deslack

I would like to continue work on the MS translation project, but for ease of translation, I prefer doing it using POedit.

Is there anyway I could do that? (like downloading the POs, uploading my changes, eventually merged into base?)

‹ Suggestions, when are those going to be approved? Chinese translation ›

I made the german

translationmen - 07/14/2009 - 12:10

I made the german translation.Please send me the details on my mail and I will help you with your translation.
German Translation

you can post your german

khalemi@drupal.my - 07/16/2009 - 03:41

you can post your german translation at drupal.org.

Thanks

Thanks,
M.Khalemi (MCP,MCTS,Certified Acquia Partner)
www.hostwaves.com

Installing ms-5.x-1.0-beta2.tar.gz

umarzuki - 06/14/2009 - 15:06

after extracting ms-5.x-1.0-beta2.tar.gz in /opt/lampp/sites/all/modules, i still couldn't find ms localization module, how do i enable it?

You don't install it as a

ckng - 06/15/2009 - 10:08

You don't install it as a module.
- Install i18n module
- Add ms language at admin/settings/language/add
- Extract the file ms-5.x-1.0-beta2.tar.gz and import the ms.po in /admin/build/translate/import

The only problem I foresee is

ckng - 06/06/2009 - 11:56

The only problem I foresee is that there is no way to filter out existing translation before import as it does not detect existing or same translation thus causing duplicate on the server side. This will create additional work of approving previously approved translation.

AFAIK, the only way is to manually editing the PO file and remove those already translated before starting to work on translation. My recommendation is to use 'Drupal 6 package format' export so you can have smaller PO, easier to remove existing translation. And can get the translation in, in smaller pieces.

Best is still using the translation server interface as it is capture directly, someone could have translated it =)

Tedious

Deslack - 06/06/2009 - 12:37

If that is so, it could be tedious work, removing the already translated pieces first.

Go ahead with PO

ckng - 06/23/2009 - 14:37

Deslack, I just recheck the l10n server, it does filter the import properly. So go ahead and translate using PO file.

Note that it is best to export the lastest version so there is no duplication of already translated text, as different translation will ended up as suggestion which need to filter on server 1 by 1.

Email me if you have any, including contrib modules.

Thats why we have the

khalemi@drupal.my - 06/07/2009 - 10:16

Thats why we have the Translation server, now.

Thanks,
M.Khalemi (MCP,MCTS,Certified Acquia Partner)
www.hostwaves.com

That cannot be helped. If not

ckng - 06/07/2009 - 04:18

That cannot be helped. If not it will just 'pollute' the server copy and it is >2x works to remove them at server side.

I did check in a translation

Deslack - 06/09/2009 - 10:22

I did check in a translation of Drupal 6.12's user module. It did detect unchanged translation strings, as well as the newly translated ones. How does it show on your side?

I'm referring to the import

ckng - 06/09/2009 - 15:50

I'm referring to the import into translation server (i10n server), not translation interface.



Theme by Dr. Radut.