Hi,
On 23/01/16 11:51, Stefan Fuhrmann wrote:
> The topic has been brought up on IRC yesterday
> but I've found wondering myself the same thing
> in the past: What error messages should be
> marked for localization?
>
> In particular, most of the back-end libraries create
> "stuff is horribly broken" error messages whose
> specific contents is only meaningful to experts but
> not to ordinary admins or client users. We are quite
> inconsistent about the usage of _() in those libs and
> I myself wasn't consistent about it either.
>
> I suggest as a policy (in case that isn't already in
> place) that error messages shall not be localized
> id the user / admin cannot reasonable act on them.
> Specifically, I suggest that all "data corrupted" error
> messages become non-localized. If there is something
> that a user can do about it (transient network failure),
> higher levels should wrap the error appropriately.
I brought this up while updating translations. I do not really have
anything to add to what you wrote other than proposing the guidelines
that localisation should be on the UI, not on the internal implementation.
Andreas
Received on 2016-01-24 21:23:47 CET