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

Scope effort to externalize Puppet report strings for translation

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Normal
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:
    • Acceptance Criteria:
      Hide

      A plan for externalizing report strings in Puppet has been proposed.

      Show
      A plan for externalizing report strings in Puppet has been proposed.
    • Team:
      Agent
    • Story Points:
      3
    • Sprint:
      AP 2016-12-14, AP 2017-01-11
    • QA Risk Assessment:
      No Action
    • QA Risk Assessment Reason:
      [Bulk update] Testing, infrastructure, research tickets do not require risk assessment

      Description

      The internationalization effort for Puppet has been broken up into phases, in order to prioritize translating the most important user-facing strings earlier. The first of these priorities for Puppet Core is puppet report strings. We need to analyze how information is put into the report and design a way either to automate marking these strings for externalization, or to change the report generating code to externalize and translate strings that pass through it (see Facter's logging mechanisms)

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support