[wp-meta] [Making WordPress.org] #5621: Don't warn on numbered placeholders <=> non-numbered placeholders

[Making WordPress.org]

#5621: Don't warn on numbered placeholders <=> non-numbered placeholders
-------------------------------------------+---------------------
 Reporter:  dd32                           |       Owner:  (none)
     Type:  defect                         |      Status:  new
 Priority:  low                            |   Milestone:
Component:  Translate Site & Plugins       |  Resolution:
 Keywords:  needs-patch reporter-feedback  |
-------------------------------------------+---------------------

Comment (by dd32):

 Replying to [comment:1 ocean90]:
 > What’s the point of removing valid warnings just for translate.w.org?

 I would be happy to upstream some improvements there, but your comment
 proves that it's not always viable either, The majority of the changes I
 make to translate is to improve the usability of it, rather than be
 "strictly correct" which the software should be.

 However, I don't consider them to be valid warnings, warnings that will
 always be ignored/discarded are not warnings, they're notices at best.

 You'd be correct in thinking that most translators will just fix the
 translation (because that's their only option other than leaving them),
 but from what I can see, many with editor rights simply discard them
 instead (even warnings which should never have been dismissed).

 > The second example should definitely be a warning because it’s an
 incorrect translation.
 That's debatable IMHO, if it's being used with a `printf` library, it'll
 work just fine.

 Perhaps a middle ground of agreeing that "upgrading" `%s` to `%1$s`
 shouldn't be considered a warning, but that downgrading is?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5621#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org