Skip to content

Stop marking exception messages for translation #2

@abadger

Description

@abadger

Talked with Shaiton and decided marking exception messages for translation is not a great idea:

  1. When you get an exception, you'd like to be able to google for it. translations hinder that.
  2. Translators often don't know what the exception messages mean so it's difficult for them to translate them accurately.
  3. Translations of exception messages aren't very helpful to the end user either.

We will have to be careful about how the exception messages leak out into error messages that the end user does see (and might possibly be able to correct/workaround) though.

We'll need to remove the () and b() from exception messages.

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions