Closed Bug 1346376 Opened 7 years ago Closed 7 years ago

Localize WebExtension error/warning messages

Categories

(WebExtensions :: General, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mattw, Unassigned)

References

(Depends on 1 open bug)

Details

User Story

As a non-English speaking add-on developer, I'd really like the error messages I see when developing a WebExtension to appear in my native language so I can quickly make the fixes I need to get my WebExtension up and running.
Currently none of our error messages are localized, so any non-English speaker developing a WebExtension may have trouble understanding the help we try to provide when their extension contains errors. It would be great if we could get error and warning messages localized before the big 57 release.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
I think we should still provide error messages even if we have error codes. Shouldn't this depend on that bug instead of being a duplicate of it?
Status: RESOLVED → REOPENED
Depends on: 1291039
Resolution: DUPLICATE → ---
Speaking as a non-native English speaker, I'm *against* localized error messages.  They make googling for solutions much harder, and in general, it is virtually impossible to be a developer without knowing/learning english.

(Or more practically, we are unlikely to have the resources to localize all the developer-facing messages, so adding error codes solves two problems at once:  1) handling errors in code,  and  2) ability to localize the messages in an optional/external way, like on MDN)
Flags: needinfo?(mwein)
Thanks for your input -- this is really helpful -- and what you said in 2) makes me feel more comfortable with resolving this bug and focusing instead on adding support for error codes.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → WONTFIX
Flags: needinfo?(mwein)
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.