[translations] renaming "potx"
Gábor Hojtsy
gabor at hojtsy.hu
Tue Oct 26 12:46:34 UTC 2010
Hi,
I decided it is time to rename potx. Some reasons:
1. It is a cryptic name :)
2. It is not anymore about .pot extraction per say... the primary
output from a users point of view is not a translation template
anymore.
3. It integrates with l10n_server extracting strings from source code
to database (no pot templates involved in the process)
4. It does coder integration to find localization API issues in your code
5. It plans to do real translation status reporting (finding all
source strings and showing you where you actually stand vs. the
built-in source string finder)
6. It plans to do translation optimization (finding source strings
only for enabled modules and themes and letting you delete extraneous
strings)
Point 6 is ever more important now that we move to one .po file per
project on localize.drupal.org. All-in-all, I'd like to make this a
more friendly and "accessible" tool and recognize it is not anymore
about translation templates. I'm thinking of a few names, but not sure
what's best long term. I'd like to use the l10n_* prefix that we
established with l10n_client, l10n_update, l10n_pconfig, l10n_update,
l10n_install, l10n_server etc.
Some ideas that come to mind: l10n_extractor, l10n_parser,
l10n_code_analyzer, l10n_api_extractor, etc. I hope to set up the
module for "the long term" with this new name, so tips in choosing the
best name would be good :)
Thanks,
Gábor
More information about the translations
mailing list