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 | ||
Chris Leonard
L10n, and more particularly, i18n deserves it's own component in the bug tracker.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
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.
Chris Leonard
(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
Alexey Proskuryakov
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.