Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-55242

Policy: Do not translate CLI scripts

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • 3.2
    • Language, Policy
    • None
    • MOODLE_32_STABLE

      The current state of CLI scripts is sometimes people translate things, sometimes they don't. We should be consistent. And I argue we should be consistent about never translating in cli scripts.

      In MDL-55206 - I asked the question:

      Is common practice?
      Is 'demanded' by users?

      I'm not being insensitive to other languages here, it just feels like the CLI is a bit of an english dominated world. I am not sure if its better that we should just have a blanket policy of no translation in them. (There are some parallels with https://moodle.org/mod/forum/discuss.php?d=218027)

      In that issue, Jun also reported some results from the ecosystem:

      To look into this, I tried changing my Ubuntu desktop's language to Japanese and showed the help text of the following programs:
      Default linux commands such as ls, mv, cp, etc - Translated to Japanese
      PHP (php -h) - Only in English
      Python (python -h) - Only in English
      Java (java -h) - Translated to Japanese
      Behat (vendor/bin/behat -h) - Only in English
      PHPUnit (vendor/bin/phpunit -h) - Only in English
      Git (git --help) - Only in English

            Votes:
            11 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.