Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-7042

Mark non-debug messages for externalization

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 5.0.0
    • Component/s: None
    • Labels:
    • Template:
    • Acceptance Criteria:
      Hide

      User-facing messages logged above debug level are marked for externalization

      Show
      User-facing messages logged above debug level are marked for externalization
    • Team:
      Agent
    • Story Points:
      5
    • Sprint:
      AP 2017-01-11, AP 2017-01-25, AP 2017-02-08, AP 2017-03-08
    • Release Notes:
      Not Needed
    • QA Risk Assessment:
      No Action
    • QA Risk Assessment Reason:
      Testing for this work performed separately; assessment not needed

      Description

      We have decided to adopt a tiered approach to marking strings in Puppet with gettext's _() function. Step One is to mark strings that are logged at a level higher than debug (i.e. info, warning, error, crash reports), since these will always appear in the reports and logs when running puppet with default settings.

      Helpful tool: https://github.com/Magisus/string-wrapper

      Once we think that most of the relevant strings have been marked, we should make a dummy translated PO file with "translated" messages which contain non-ASCII characters and change the values of the strings. Then we can use these files to run specs and acceptance tests, as well as generate some sample reports, to get an idea of where our tests are too brittle, and what the next steps for string extraction ought to be.

      Larissa Lane will also use the result of this marking to get an idea of budget requirements for actually translating this volume of strings.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              maggie Maggie Dreyer
              Reporter:
              maggie Maggie Dreyer
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support