Hi,
I found that many Source has similar structure. [more info: http://groups.drupal.org/node/28494]

some desktop software like poEdit has "automatically translate..." function.
if it can export by keywords that can be more quickly to translate them.

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

I agree this could be a useful feature, and maybe even replace the current export screen, since we already have a project and release picker here and we could do the format picker on a follow up screen.

KayL’s picture

KayL commented

also we may need to export "untranslated strings by project", "first 100 untranslated strings".

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

@KayL: for this later, you can just export the full project translation via the usual export screen and use any tool to filter that. Any desktop PO editor can present you with only the untranslated strings.

podarok’s picture

podarok
🇺🇦 he/him/his
Primary language Ukrainian
Location Ukraine
commented

subscribe from http://drupal.org/node/602086#comment-2140374

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Title: export Source data by keywords » Reuse translation screen filters as first step of export form
Component: Miscellaneous » User interface

Retitled to be more specific as to what we discussed above.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Title: Reuse translation screen filters as first step of export form » Make export work with any filter combination

Retitled again on the heels of #740440: Allow to export the translation of all projects .

ahwebd’s picture

ahwebd commented

Hi Gábor,

The only reason to not allow this currently is the question of server resource consumption. A fully exported language .po can be 20MB as we estimated in Paris. Now imagine people exporting 20MB files on the fly all the time.

Is it possible to implement this feature in the module while allowing restriction of its use with permissions, this will still allow low resource usage on l.d.o.

People running their own servers will benefit a lot from this feature, it will greatly ease the transfer of translations between the server and sites.

Thanks