[wp-trac] [WordPress Trac] #15887: Capital letters for writing the word "Error"

WordPress Trac wp-trac at lists.automattic.com
Tue Apr 12 09:19:15 UTC 2011

#15887: Capital letters for writing the word "Error"
 Reporter:  doktorbro         |       Owner:  markjaquith
     Type:  enhancement       |      Status:  reopened
 Priority:  normal            |   Milestone:  Future Release
Component:  Warnings/Notices  |     Version:  3.1
 Severity:  minor             |  Resolution:
 Keywords:  i18n has-patch    |

Comment (by dd32):

 The !WordPress files are in (US) English, This means all strings inside
 WordPress will be in a US English format.

 Translations can do whatever they please with these strings.

 A Translation can already convert '`<strong>ERROR:</strong> something`'
 into '`something <em>(error)</em>`' if thats how their locale treats
 messages with that tone.

 I see no reason for anything other than standardising the way error's are
 referred to in strings that needs to be done here to support other

 If the problem is that translations are being incorrectly done due to
 translators not understanding how to translate English text into whatever
 language they're translating it to.. then ''they need'' education..
 Monkey, ape, or super-human being..

 > For now, if I use <strong> in some msgid's, wordpress displays the CSS-
 Tags itself inside the warning
 HTML Tags may be striped, or displayed inline in some locations, it will
 all come down to the particular string, and where'd being used; In
 general, you can include HTML in translated strings, however, if it's
 being output as part of a error message (for example in XML-RPC) the
 client may not support HTML.

 We may also be over-escaping data in some locations, We do this for
 security reasons most of the time, So if something is being escaped that
 shouldn't be, '''You need to raise a bug about the exact string and where
 it's occuring''' to allow us to modify the code in question to allow
 translations to happen properly.

 I'm sorry that I'm completely against your suggestions here, my only
 reason is that I believe that there is a better way to achieve it in this
 case than modifying the current practices...

Ticket URL: <http://core.trac.wordpress.org/ticket/15887#comment:14>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list