Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols Epic Status: To Do Done 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-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Maggie Dreyer commented on PUP-6715 Re: End-to-end POC for string externalization in Puppet The unfinished work which used to live in this epic has moved to PA-1024. 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-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols Team: Agent & Platform Epic Status: To Do Epic Name: End-to-end POC for string externalization in Puppet Status: Accepted Designing Workflow: Scrum Teams Engineering Epic Workflow Issue Type: Task Epic Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols Team/s: Agent & Platform 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-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols h5. In scope:* Wrap one simple string* in the puppet repo with the _() gettext function * Create a CI job that uses the gettext-setup gem tooling to generate a POT file, and a PO file for Japanese* Add the puppet repo to the Transifex integration and test that the PO file is automatically pulled into Transifex when updates are made to it (Larissa)* When the PO file reaches 100% translated and reviewed in Transifex, it is automatically updated in the puppet repo (Larissa)* Add a setting to check the user's locale and display supported languages or default to English* Test on an OS that has the environment set to Japanese* Consider stripping the line numbers out of the POT file to reduce churn*Simple string means a string that isn't composed or concatenated* Talk to [~libby] about the CI jobs she is creating for Clojure and _javascript_h5. Out of scope* An opt-out option to turn off localized strings, but this should be considered for another ticket. * Add a setting to check the user's locale and display supported languages or default to English 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
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols h5. In scope: * Wrap one simple string* in the puppet repo with the _() gettext function * Create a CI job that uses the gettext-setup gem tooling to generate a POT file, and a PO file for Japanese* Add the puppet repo to the Transifex integration and test that the PO file is automatically pulled into Transifex when updates are made to it (Larissa)* When the PO file reaches 100% translated and reviewed in Transifex, it is automatically updated in the puppet repo (Larissa)* Add a setting to check the user's locale and display supported languages or default to English* Test on an OS that has the environment set to Japanese* Consider stripping the line numbers out of the POT file to reduce churn*Simple string means a string that isn't composed or concatenated* Talk to [~libby] about the CI jobs she is creating for Clojure and _javascript_ * h5. Out of scope is an * An opt-out option to turn off localized strings, but this should be considered for another ticket. 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
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols * Wrap one simple string* in the puppet repo with the _() gettext function * Create a CI job that uses the gettext-setup gem tooling to generate a POT file, and a PO file for Japanese * Add the puppet repo to the Transifex integration and test that the PO file is automatically pulled into Transifex when updates are made to it (Larissa) * When the PO file reaches 100% translated and reviewed in Transifex, it is automatically updated in the puppet repo (Larissa) * Add a setting to check the user's locale and display supported languages or default to English * Test on an OS that has the environment set to Japanese * Consider stripping the line numbers out of the POT file to reduce churn*Simple string means a string that isn't composed or concatenated * Talk to [~libby] about the CI jobs she is creating for Clojure and _javascript_ * Out of scope is an opt-out option to turn off localized strings, but this should be considered for another ticket. 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
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols Sprint: AP Grooming Top 11-20 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-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols Sprint: i18n 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-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Larissa Lane updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Larissa Lane Labels: i18n 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-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Larissa Lane created an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Issue Type: Task Assignee: Unassigned Created: 2016/09/19 4:57 PM Priority: Normal Reporter: Larissa Lane Wrap one simple string* in the puppet repo with the _() gettext function Create a CI job that uses the gettext-setup gem tooling to generate a POT file, and a PO file for Japanese Add the puppet repo to the Transifex integration and test that the PO file is automatically pulled into Transifex when updates are made to it (Larissa) When the PO file reaches 100% translated and reviewed in Transifex, it is automatically updated in the puppet repo (Larissa) Add a setting to check the user's locale and display supported languages or default to English Test on an OS that has the environment set to Japanese Consider stripping the line numbers out of the POT file to reduce churn *Simple string means a string that isn't composed or concatenated Talk to Libby Molina about the CI jobs she is creating for Clojure and _javascript_ Out of scope is an opt-out option to turn off localized strings, but this should be considered for another ticket. Add Comment
