It would be VERY helpful if it is possible to extract into a specific language aside of the language independed one and the correct "Plural-Forms" are automatically added. This is something that would help many beginners...

Aside it saves my time a little bit... every new file i need to open an older one and cut and paste this possibly complex string - i cannot remember after 20+ times - why ever :-).

Comments

hass’s picture

And some other fields like the country, language and encoding should be added, too.

ray007’s picture

Extracting po-files for a module with the strings that currently exist is a worthwhile goal. I already did try to do this (check cvs history), but it's not that easy ...

And for the record: I'm against letting the user choose an encoding, drupal works fine with utf-8 everywhere and chances are pretty good to screw things up if we make it easy for the user to leave that path.

hass’s picture

i'm not talking about a user choice for encoding... :-) i'm only talking about the extracted file should have some pre-settings that we know for sure - and that are a MUST. The Plurals and utf-8 is really a must, isn't it!?

I only likes not wasting my time with trivial, but error prone settings inside poEdit, where the Plurals-Forms are very critical for file integrity... i have already lost a translation on this way and i wasn't able to open the file with poEdit after some popup's "there is a error in the file" - after i edited a plurals value without the plurals string configured... Additional - on my first steps on translation i haven't heard anything about "Plurals" and this was why the file crashed on the end of the day...

gábor hojtsy’s picture

The good old extractor.php script already included the utf-8 encoding in the output at all times. Now potx does the same. So this should not be an issue for you. The Plural formulas and possibly previous translations are a valid use case though.

gábor hojtsy’s picture

Status: Active » Fixed

I just committed an update which includes the possibility to export templates with a header prefilled for one specific language. Also digged into implementing translation exports with proper plural form handling, which is also done now. Please test, so we can release a stable version and take on Drupal 6 porting :)

Anonymous’s picture

Status: Fixed » Closed (fixed)