Update gettext 3.4.3 → 3.4.9 (patch)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ gettext (3.4.3 → 3.4.9) · Repo · Changelog

Release Notes

3.4.9

Improvements

• rmsgcat, rmsgmerge, rxgettext: Added
  --use-one-line-per-reference option.

3.4.8

Fixes

• doc: Fixed a wrong description for interpolation.

  • GH-102
  • Patch by Ilmari Karonen

• po: Fixed a parser bug that flags aren't parsed correctly. If a
  normal comment has "fuzzy", the entry is also treated as a fuzzy
  entry.

• po: Fixed an output bug that flags aren't formatted correctly.

  • GH-105
  • Patch by Yoshikazu Nojima

Thanks

• Ilmari Karonen

• Yoshikazu Nojima

3.4.7

Fixes

• po: Fixed a parser bug that it may add a fuzzy flag to non-fuzzy
  entry with ignore_fuzzy: true.

  Example PO:

  #, fuzzy
  #: file.rb:10
  msgid "hello"
  msgstr "bonjour"
  msgid "non-fuzzy"
  
  msgstr "non-fuzzy string"

  hello entry is ignored because ignore_fuzzy is true. The
  fuzzy flag in the hello entry is added to non-fuzzy entry.

3.4.6

Fixes

• po: Fixed a bug that parsed msgid/msgstr/msgctxt in .po
  may be too much unescaped.

3.4.5

Improvements

• po: Added support for escaping \r in msgid/msgstr.

3.4.4

Improvements

• Added racc to runtime dependencies because Ruby 3.3 doesn't
  include racc/parser.

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 31 commits:

• po: remove garbage new line
• Add 3.4.9 entry
• Add --use-one-line-per-reference option
• Bump version
• Add 3.4.8 entry
• Fix po entry flag text representation (#105)
• po parser: fix a bug that flags aren't parsed correctly
• Fix "Interpolating translations" section in README.md (#103)
• ci: add Ruby 2.5, 2.6 and 2.7 (#101)
• Bump version
• Add 3.4.7 entry
• po-parser: fix a bug that fuzzy flags may be added to unrelated entry
• Fix ' position
• Bump version
• Add 3.4.6 entry
• Bump version
• po parser: fix a too much unescape bug
• po parser: fix a too much unescape bug
• Siplify
• Bump version
• Add 3.4.5 entry
• po: add missing \r escape on output
• sample: update po
• Regenerate PO parser with Racc 1.7.0
• Add 3.4.4 entry
• ci release: add
• Change racc as a runtime dependency
• ci: use head
• test: update expected
• ci: update
• Bump version

↗️ forwardable (indirect, 1.3.2 → 1.3.3) · Repo

Release Notes

1.3.3

What's Changed

• CI: Quote "3.0" in YAML by @olleolleolle in #20
• gemspec: Explicitly empty the executables list by @olleolleolle in #19
• s/RubyVM::JIT/RubyVM::MJIT/g by @k0kubun in #22
• Update actions by @hsbt in #23
• Added dependabot.yml for actions by @hsbt in #24
• Update Ruby versions on GHA with ci_versions/all.json by @hsbt in #25
• Improve Ractor-compliance by @rm155 in #21

New Contributors

• @olleolleolle made their first contribution in #20
• @k0kubun made their first contribution in #22
• @rm155 made their first contribution in #21

Full Changelog: v1.3.2...v1.3.3

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 22 commits:

• Bump version to 1.3.3
• Merge pull request #21 from rm155/master
• Freeze VERSION and FORWARDABLE_VERSION to improve Ractor-compliance
• Merge pull request #25 from ruby/ci-versions
• added 2.5 and 2.6
• Update Ruby versions on GHA with ci_versions/all.json
• Merge pull request #24 from ruby/add-dependabot
• Added dependabot
• Merge pull request #23 from ruby/update-actions
• Use bundler-cache on setup-ruby
• Use actions/checkout@v3
• Added 3.1
• Move `:stopdoc:` directive
• Merge pull request #22 from k0kubun/rubyvm-mjit
• s/RubyVM::JIT/RubyVM::MJIT/g
• Bump up the latest version of CoreAssertions
• Prefer qualified names under Thread
• Merge pull request #19 from olleolleolle/patch-1
• Merge pull request #20 from olleolleolle/patch-2
• CI: Quote "3.0" in YAML
• gemspec: Explicitly empty the executables list
• Unify OS environments for GitHub Actions

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #492.