Jira (PUP-6976) Scope effort to externalize Puppet report strings for translation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6976 Scope effort to externalize Puppet report strings for translation Change By: Geoff Nichols Sprint: AP 2016-12-14, AP 2016 2017 - 12 01 - 28 11 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6976) Scope effort to externalize Puppet report strings for translation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6976 Scope effort to externalize Puppet report strings for translation Change By: Geoff Nichols Sprint: AP 2016-12-14 , AP 2016-12-28 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6976) Scope effort to externalize Puppet report strings for translation
Title: Message Title Kurt Wall updated an issue Puppet / PUP-6976 Scope effort to externalize Puppet report strings for translation Change By: Kurt Wall QA Risk Assessment Reason: [Bulk update] Testing, infrastructure, research tickets do not require risk assessment QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6976) Scope effort to externalize Puppet report strings for translation
Title: Message Title Maggie Dreyer commented on PUP-6976 Re: Scope effort to externalize Puppet report strings for translation The next step is to identify which areas of the code base we should focus on in order to catch strings that are going to wind up in the report. I will use this doc to assemble the answer: https://docs.google.com/a/puppet.com/document/d/1aFtTMFp4tyvHMwVqG-3_33XgzTHtxOO1pVTBrJ4FFcg/edit?usp=sharing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6976) Scope effort to externalize Puppet report strings for translation
Title: Message Title Maggie Dreyer commented on PUP-6976 Re: Scope effort to externalize Puppet report strings for translation It looks like we may be able to use this Ruby AST parser/rewriter to automate wrapping translatable strings in Puppet: https://github.com/whitequark/parser. I wrote a script using it that seems to work on an example test case: https://github.com/magisus/rxstrings. This seems more robust than attempting to just treat the files as text, though doubtless there are many more special cases and exceptions that would need to be added as we try it on more complicated files. We will also need to better define what counts as a "translatable string", so we can add more heuristics. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6976) Scope effort to externalize Puppet report strings for translation
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Puppet / PUP-6976 Scope effort to externalize Puppet report strings for translation Change By: Maggie Dreyer Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6976) Scope effort to externalize Puppet report strings for translation
Title: Message Title Maggie Dreyer created an issue Puppet / PUP-6976 Scope effort to externalize Puppet report strings for translation Issue Type: Task Assignee: Unassigned Created: 2016/12/05 3:37 PM Priority: Normal Reporter: Maggie Dreyer 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) Add Comment
