Download & Extend
Localization server » Issues

Make export work with any filter combination

Posted by KayL on October 5, 2009 at 5:34pm
Project:Localization server
Version:6.x-1.x-dev
Component:User interface
Category:feature request
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

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.

Login or register to post comments

Comments

#1

Posted by Gábor Hojtsy on October 6, 2009 at 6:09am

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.

#2

Posted by KayL on October 8, 2009 at 9:20am

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

#3

Posted by Gábor Hojtsy on October 8, 2009 at 9:43am

@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.

#4

Posted by podarok on October 12, 2009 at 11:19am

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

#5

Posted by Gábor Hojtsy on January 20, 2010 at 12:30pm
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.

#6

Posted by Gábor Hojtsy on March 12, 2010 at 10:42am
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 .

#7

Posted by ahwebd on December 31, 2010 at 5:58pm

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