Hi everybody! I’m a translator and beginner developer from México, and I’m coming here to learn the best practices about translating the WordPress Codex.
-
potbot
Reply
Unresolved »
Showing 1-7 of 7 unresolved posts
7Recent comments
GlotPress Trac- Changeset [762]: Add missings images for #181
- Changeset [761]: Add missing tablesorter plugin. See #181.
- Changeset [760]: Make HTML/CSS changes to have it correctly done. See #239
- Ticket #240 (Change Translation Text Direction fro RTL Languages) closed
- Ticket #240 (Change Translation Text Direction fro RTL Languages) created
- Changeset [759]: Make project view 100% width unless there are subprojects. Fixes #239
- Ticket #239 (Project overview should be 100% width) closed
- Changeset [758]: Make translation sets sortable through the interface. Also fixed ...
- Ticket #100 (Notifications for certain actions) reopened
- Ticket #158 (translated strings must be shown right-to-left for right-to-left languages) closed
- Core i18n Tickets
- #24183: MediaElement.js i18n issues
- #23907: Scandinavian ligatures transcribed wrong in remove_accents()
- #23794: load_plugin_textdomain fails if plugin is loaded from mu-plugins
- #23758: Add hook after loading WordPress locale object
- #23721: Better control of textdomains.
- #23503: Post Formats: i18n issues
- #23433: Custom background select needs a contextualized label
- #23341: Spell checker in the editor shows languages not supported by google spellchecker like hebrew
- #23311: Enable internationalization in PHPMailer
- #23056: date_i18n() does not localize dateformat 'r'
Zé 11:33 pm on June 9, 2012 Permalink |
Did you take a look at http://codex.wordpress.org/Multilingual_Codex ? It’s probably also a good idea to talk to the Spanish team, you may want to join efforts.