I think this is supposed to be localized, right? You can see this in action on tetris.js:284
<rdar://problem/18405527>
It is debatable if they should be localized. We don't localize things that match language keywords or names. (For example the padding, margin, etc. labels in the Style Metrics pane are not localized.)
I think Joe and I spoke about this in a previous bug or over IRC. I think it should be localized because many JavaScript programmers will be familiar with String, Null, etc, just by programming in JavaScript, even though they may not understand the English meaning of these words. But I don't think non-English speaking programmers will immediately understand "many".
I guess an argument against my previous point is: It might be weird from a user experience perspective to have all type tokens be in English except the "many" token.
Created attachment 238423 [details] patch
(In reply to comment #4) > I guess an argument against my previous point is: > > It might be weird from a user experience perspective to have > all type tokens be in English except the "many" token. My inclination would be to put it in parens: (many) or call it multiple. From reading Japanese + code, it's not going to be a big shocker. But this discussion is mostly hypothetical until we get some localizers in the loop. For now, I think this should land as-is so we can start getting feedback and get rid of LOCALIZED STRING NOT FOUND.
Created attachment 238444 [details] patch Including parenthesis in localizable string.
Comment on attachment 238444 [details] patch Clearing flags on attachment: 238444 Committed r173803: <http://trac.webkit.org/changeset/173803>
All reviewed patches have been landed. Closing bug.