@mjturn:
I guess that you mean to reuse strings like 'Edit', 'Delete', 'File not found' ?
If so, I thought the same, but gettext comes with a new paradigm:
The modularity goes to the translations too, each extension with it's own translation catalog and that's why reuse of other strings is not recommended. I was reluctant at the beginning, I wanted to reuse the 'Edit', 'Meta data', and all those common and widely used strings; I had some discussions with the core-devs about it and I realized the easiness of maintain each translation separated.
So, the core will be not attached to any string because it's used by third party devs, nor conflicts with its translations because a string can be used in different contexts... and even technically:
We have a Bash script to convert the pnML functions and plugin calls to gt, as the first step of the conversion. And a second one to extract the catalog (POT file). That one, parses the extension code, and give you the catalog with
all the strings, it can't discard the ones that you used from another gettext domain... so, better to have them separated from many points of view, and to translate those few common words with poEdit is not hard at all
Greetz
--
-
Mateo T. -
Mis principios... son mis fines