[wp-trac] [WordPress Trac] #14063: Twenty Ten i18n problems
WordPress Trac
wp-trac at lists.automattic.com
Fri Dec 17 09:50:32 UTC 2010
#14063: Twenty Ten i18n problems
--------------------------+----------------------------
Reporter: pavelevap | Owner: nbachiyski
Type: defect (bug) | Status: assigned
Priority: normal | Milestone: WordPress.org
Component: Themes | Version: 3.0
Severity: normal | Resolution:
Keywords: |
--------------------------+----------------------------
Comment (by pavelevap):
OK, thank you...
1) New ticket - http://core.trac.wordpress.org/ticket/15858
2) New ticket - http://core.trac.wordpress.org/ticket/15859
3) Yes, it is my another ticket -
http://core.trac.wordpress.org/ticket/13651
4) This problem is not confirmed in latest trunk.
5) So we can leave this ticket for this particular problem? There is no
bug, but sync problems. Example is also with latest WordPress. Akismet is
bundled with WordPress, but new version can be also released separately.
So, I updated to WP 3.0.2 and then to Akismet 2.5.0. But suddenly, WP
3.0.3 appeared and after update I was back with Akismet 2.4.0 (because
this version was bundled with WP). Not very user friendly.
And another problem is that Akismet is translated together with WordPress.
But when there will be Akismet 2.6 (and no WordPress update), many strings
can be untranslated. I am not sure about right solution, but Akismet
should be removed from main WP translation and synced with specific plugin
translation (and the same system should be applied for Twenty Ten). This
should also avoid following problem - new Twenty Ten version released in
Theme repository but no new WordPress version.
You can see discussion and proposal here:
http://wppolyglots.wordpress.com/2010/12/10/proposal-for-plugins-
localization-system/
--
Ticket URL: <http://core.trac.wordpress.org/ticket/14063#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list