3.4 update: Localizing quotes and apostrophes that go through wptexturize(). More
-
Andrew Nacin
Reply
Unresolved »
Showing 1-10 of 10 unresolved posts
10Recent comments
GlotPress Trac- Changeset [763]: Change test case for changed parity factory function. See #181
- 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
- Ticket #239 (Project overview should be 100% width) closed
- Changeset [759]: Make project view 100% width unless there are subprojects. Fixes #239
- Changeset [758]: Make translation sets sortable through the interface. Also fixed ...
- Ticket #100 (Notifications for certain actions) reopened
- 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'
Xavier 12:25 am on February 8, 2012 Permalink |
It seems the right place and time to comment about curly quotes.
I made a quick update to my trunk install’s MO files, just enough to be able to check my curly quote break post. Still no cigar.
This has long been a personal quest for me (I wrote some tests at the time), and has been pushed over and over, through many tickets with varying degrees of relevancy to the issue (AFAICT). Since there’s a lot of effort on i18n during this cycle, I would love it 3.4 could put an end to that issue.
I can open a brand new ticket if need be.
Andrew Nacin 12:57 am on February 8, 2012 Permalink |
The bugs there are not i18n-related. They were nearly fixed in #4539 (for which the other ticket was closed as a duplicate), but the tests were not comprehensive enough and quite a few things broke, so it was backed out of trunk.
So, no new ticket needed. Just look at #4539 and see if there is anything that can be done.
Xavier 7:52 am on February 8, 2012 Permalink |
Will do. Thanks.