Jira (PUP-7939) I18N japanese translation does not contain leading spaces

[Eric Delaney (JIRA)]

Title: Message Title

Eric Delaney commented on PUP-7939   Re: I18N japanese translation does not contain leading spaces Erwin Hom Yes, I believe the spaces were original included in the string to enable readability of the messages. Originally most of them where just HERE doc's like this: description <<-'EOT' Updates values in the `puppet.conf` configuration file. EOT Some, but not all have been switched over to multiple lines like this: def multiline message = [] message << _("Could not %{action} module '%{module_name}' (%{version})") % { action: @action, module_name: @requested_name, version: vstring } message << _(" No version of '%{module_name}' can satisfy all dependencies") % { module_name: @requested_name } #TRANSLATORS `puppet module %{action} --ignore-dependencies` is a command line and should not be translated message << _(" Use `puppet module %{action} --ignore-dependencies` to %{action} only this module") % { action: @action } message.join("\n") end As you can see the spaces are included in the message string currently. If we where going to try and get ride of leading spaces it might be interesting to create a robocop that complains about leading spaces in decorated strings. That would give you an idea of how many you have and if its ever cleaned up be able to enforce not adding them again. Add Comment   This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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.