i18n on developer.wordpress.org

[ramiy]

Fixing the theme i18n.

See the attached patch.

[extendwings]

Duplicate of #658?

[ramiy]

Not duplicate but related.

This ticket is about internationalizing the "developer" site theme (see the attached patch).

#658 is about internationalizing the "developer" site content (parsed documentation from the WordPress source code).

[coffee2code]

In 2779:

developer.wordpress.org: Make more strings translatable.

Props ramiy.
Fixes #1627.

[ramiy]

@coffee2code,

In my patch I fixed two files (content-reference.php and content-wp-parser-hook.php),
in your changeset you fixed only one file (content-reference.php).

Basically, it's the same change for both files.
I think you should consider updating the second file too.

[DrewAPicture]

Replying to ramiy:

In my patch I fixed two files (content-reference.php and content-wp-parser-hook.php),
in your changeset you fixed only one file (content-reference.php).

Basically, it's the same change for both files.
I think you should consider updating the second file too.

If I remember correctly, we don't actually use content-wp-parser-hook.php anymore for simplicity. The get_template_part() calls toggle for content-{$post_type} only for non-parsed post types since [1675].

I would guess that's why @coffee2code didn't update it with your changes, as it's likely to be removed in the future.

[coffee2code]

@ramiy: @DrewAPicture is correct. The content-wp-parser-hook.php template is no longer in use and its removal is one of my pending commits for the next day or two.