On Sat, Apr 3, 2010 at 5:03 AM, Nicolas François wrote:
You should first define what you would expect from po4a.
The reasons I can imagine are:
* You have a nice .strings editor, and you want po4a to generate and work
with .strings files instead of PO files.
I guess this would not be the case.
* You want po4a to be able to extract the strings from a .strings and
generate a PO file, and be able to re-inject translations in the .strings
This is the functionality I had in mind.
In both cases, I'm not sure po4a is suitable. A .strings <-> PO
converter would probably be much more useful.
I agree, this is a converter functionality basically. But then, I thought one of the core features of po4a package was to ease localization on formats other than PO by extracting strings from the source format and importing them to PO (and then reexporting the translated strings).
In that case, the more formats po4a supports, the easier it will be for users to use po4a and not look for convertors elsewhere (and right now it is very difficult to find and use .strings <> po converter).
But I may have misunderstood po4a concept.
Thanks.
Aiet