[wp-trac] [WordPress Trac] #33073: Some strings need "no HTML entities" translator comments

[WordPress Trac]

#33073: Some strings need "no HTML entities" translator comments
----------------------------------------------------+---------------------
 Reporter:  xibe                                    |       Owner:  (none)
     Type:  enhancement                             |      Status:  new
 Priority:  normal                                  |   Milestone:  6.6
Component:  I18N                                    |     Version:
 Severity:  normal                                  |  Resolution:
 Keywords:  good-first-bug has-patch needs-refresh  |     Focuses:
----------------------------------------------------+---------------------
Changes (by swissspidy):

 * keywords:  good-first-bug has-patch => good-first-bug has-patch needs-
     refresh
 * milestone:  6.5 => 6.6


Comment:

 > Asking translators to check the context may still lead to human error.
 [https://core.trac.wordpress.org/ticket/33073#comment:13 comment:13]
 points to `html_entity_decode()` as a viable code-based solution. I
 believe `needs-patch` is correct because the previous patch's approach no
 longer seems to be the preferred one, and a new patch is needed.

 IMHO we need both:

 1. Translator comments so that translators do not use HTML entities
 (documentation)
 2. Usage of `html_entity_decode` to fix any remaining HTML entities
 (hardening)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/33073#comment:34>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform