One of the things I've added to the xgettext parser was the inclusion
of comments. That is, any comment before a gettext function call will
be included in the POT template. So to make things easier on
translators we should start including comments about the context of
some of the more obscure strings. For a quick example, take the
string:
_e('Login to %s');
We could provide a comment to help explain the context of this string, like:
// "login to {site name}" where {site name} is the option set by the site owner
_e('Login to %s');
I'm sure that will help with some of the "printf" style strings.
--
Matt Read
http://mattread.com
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---
