Hello,
Strings for the new default theme named Twenty Eleven are inserted into core WordPress language file for 3.2. Should they be in a separate file or this is some future method of managing translations?
-
Kenan Dervišević
Reply
Recent comments
GlotPress Trac- An error has occurred; the feed is probably down. Try again later.
- Core i18n Tickets
- #7098: Multiple entity codes in POT file for the same character
- #11740: Sorting tags and towns does not work well for utf-8
- #12477: Search with special characters and similar terms
- #14981: Provide a context for post statuses
- #20739: Improve Excerpt generation for non-english locales
- #22225: WordPress does not localize ordinal suffixes in dates
- #22812: Tweak the media modal styles for longer strings in ru_RU
- #23311: Enable internationalization in PHPMailer
- #23794: load_plugin_textdomain fails if plugin is loaded from mu-plugins
- #25585: Arabic stopwords comparison
Zé, 
Kenan, 
WP Polyglots 
Andrew Nacin 9:38 am on April 23rd, 2011 Permalink |
They should have their own textdomain and own pot. Any that don’t, we can correct that. (Create a ticket.)
Peter Westwood 10:58 am on April 23rd, 2011 Permalink |
We need to update the makepot.php script that potbot uses to know about twentyeleven.
Kenan 10:29 am on April 29th, 2011 Permalink |
Is it possible to do this anytime soon? Strings are constantly added to the wrong place and it will just create a confusion when the release is ready. If I am correct, only line 146 in the code of makepot.php needs to be changed to include ‘wp-content/themes/twentyeleven/.*’ beside continents-cities and twentyten.
Zé 12:37 pm on April 29th, 2011 Permalink |
makepot.php has to be changed *too*, but it is not the main place. (makepot.php is a *generic* tool to parse php code and create a .po from the gettexted strings, and is aware of continents-cities and twentyten/twentyeleven, for special treatment)