Bug 82024

Summary:	Need bug tracker component of L10n / i18n
Product:	WebKit	Reporter:	Chris Leonard <cjlhomeaddress>
Component:	Tools / Tests	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED INVALID
Severity:	Normal	CC:	ap
Priority:	P2
Version:	528+ (Nightly build)
Hardware:	Unspecified
OS:	Unspecified

Description Chris Leonard 2012-03-22 23:29:35 PDT

L10n, and more particularly, i18n deserves it's own component in the bug tracker.

Comment 1 Alexey Proskuryakov 2012-03-23 12:09:39 PDT

I don't see how an internationalization component would be helpful. Can you please provide some examples?

An i18n bug in JavaScriptCore is still a JavaScriptCore bug, and a bug in forms is still a Forms bug. We don't have one group of engineers who make things work for US-ASCII, and another group that rewrites their code to be world aware.

Comment 2 Chris Leonard 2012-03-23 13:13:15 PDT

(In reply to comment #1)
> I don't see how an internationalization component would be helpful. Can you please provide some examples?
> 
> An i18n bug in JavaScriptCore is still a JavaScriptCore bug, and a bug in forms is still a Forms bug. We don't have one group of engineers who make things work for US-ASCII, and another group that rewrites their code to be world aware.

No need to be rude. Just how are localizers to know which module the string is from?

https://bugs.webkit.org/show_bug.cgi?id=82018

https://bugs.webkit.org/show_bug.cgi?id=82025

Comment 3 Alexey Proskuryakov 2012-03-23 14:15:17 PDT

Thank you for the examples. These bugs are neither i18n nor l10n. Bugs in WebKit Gtk API (including spelling nits in explanation texts for translators) should go to WebKit Gtk component.