pootle icon indicating copy to clipboard operation
pootle copied to clipboard

[RFC] localise CLI text

Open phlax opened this issue 8 years ago • 5 comments

not sure what the right thing to do here is but we dont currently, and im not really sure why not so opened this ticket to address.

phlax avatar May 04 '16 13:05 phlax

@dwaynebailey any thoughts on this

phlax avatar May 04 '16 13:05 phlax

As I said on the channel:

To me it seems strange to do. Not only because we will display localized messages to admins who would surely understand English, but because we might get bizarre bug reports. Also this will increase the strings to translate.

unho avatar May 04 '16 13:05 unho

I prefer not to have any admin-facing CLI/API output localized. In addition to what @unho said, it makes it much harder for end users (admins) to get help from the community if the message they get is localized.

iafan avatar May 04 '16 15:05 iafan

I have two positions:

  1. The critical part to localise is the UI for translators.
  2. Some admins want/need localisation on the cli but most don't.

If we make cli localisable the content to localise increases dramatically for very very limited audience.

If we do decide to localise, at the very least the cli should be translated apart from the ui so that everything does not need to be localised.

My gut feeling. It's not important atm.

dwaynebailey avatar May 04 '16 16:05 dwaynebailey

This familiarizes localizers with the CLI, making more useful admins out of them, and it is useful to have admins that have done some translation. Also, it improves the quality of the CLI strings, as more eyeballs are on them, by people likely to know something about how they should be fixed, preserving some consistency with the other strings.

Admins can change the language, and there can be a link to the English source for errors.

comradekingu avatar Apr 16 '18 17:04 comradekingu