The module should use the translation which have already been done.

For example, when I use the module on captcha module I got the following page
You are here: Home » Translation Status»
captcha
(new): Adds a Captcha to various forms to help prevent spam submissions.
(new): Captcha
(new): Administer how and where Captchas are used.
(new): Captcha Points
(new): Administer in what forms Captchas are applied.
(new): Comment form
(new): User contact form
(new): Sitewide contact form
(new): Enable/Disable captcha points.
(new): Your captcha points were sucessful updated, please configure the challenge options in the other tab.
(new): Captcha points for the role @role
(new): Select what kind of challenge you want to pose to the user in each captcha point.
(new): @point
(new): The answer you entered to the captcha challenge is incorrect.
(new): Math Question: What is %problem?
(new): Please solve the math problem above and type in the result. e.g. for 1+1, type 2.
(new): Implements a captcha to registration, comment, contact and node entry forms.
(new): SPAM Control

even if a fr.po exist for that module.
This fr.po already contains all the translations of the module for french language

The module should read these .po files and use them as a base for translation

Comments

brmassa’s picture

Assigned: Unassigned » brmassa
Status: Active » Postponed

Thierry,

Extractor should not import po files.
But im planning to create a import PO feature, based on locale.module.

regards,

massa

brmassa’s picture

Title: Module doesn't use the translation already done in .po files » Import/Export PO files

Thierry,

im almost finishing this. a few days only.

regards,

massa

brmassa’s picture

Project: Localization client » Localization server

Guys,

i split the code in 2 modules.

cheers,

massa

brmassa’s picture

Title: Import/Export PO files » Import PO files
Status: Postponed » Fixed

Done on 0.30

brmassa’s picture

Status: Fixed » Closed (fixed)