[wp-hackers] Re: no-code-duplication i18n for WordPress

kingler kingler at 72pines.com
Mon Mar 3 23:48:19 GMT 2008

Hi, Lionel

You should probably also post this on the polyglots maillist, as that
is where discussion about internationalization happens.

>From what you are proposing here, you would like to add comments to
the directly hard-coded English texts in the WP source codes, right?
That will not affect any functionalities, but will help the automatic
build process in the Debian packaging. This sounds like a great idea.

One comment here: in WP2.5, TinyMCE strings will all be translated
using gettext, so that is one less thing to worry about.

kingler from 72pines

On Mon, Mar 3, 2008 at 2:01 AM, Lionel Elie Mamane <lionel at mamane.lu> wrote:
> On Mon, Mar 03, 2008 at 09:00:36AM +0100, Lionel Elie Mamane wrote:
>  > I implemented a script to do this build stage; the patch (against
>  > trunk as of yesterday) is at
>  > http://people.debian.org/~lmamane/wordpress/no-code-dup-i18n-poc.patch
>  > It adds a "i18n-tools" directory to the wordpress source tree, but
>  > we can also put it elsewhere (the code is location-independent), no
>  > problem.
>  By "elsewhere" I meant it can also be out of the WP source tree
>  altogether, e.g. in http://svn.automattic.com/wordpress-i18n/tools/
>  > The patch also tags two strings in the code (those that are in the
>  > fr.po), for tests and such. For now, they are only tagged as-is,
>  > (..._ they should be converted to sprintf (as the README says, like
> > for gettext-translated strings); I'll do it soon,
>  That is now done; results in
>   http://people.debian.org/~lmamane/wordpress/no-code-dup-i18n-poc-v2.patch
>  and
>   http://people.debian.org/~lmamane/wordpress/fr.v2.po
>  --
>  Lionel
>  _______________________________________________
>  wp-hackers mailing list
>  wp-hackers at lists.automattic.com
>  http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list