Project

General

Profile

Actions
Copy link

Bug #36115

closed

Tracker #36116: Translation effort

Multi line translation strings are not extracted

Added by Ewoud Kohl van Wijngaarden almost 2 years ago. Updated almost 2 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Internationalization
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

The following is extracted:

_('string')

But this doesn't end up in the .pot file:

_(
  'string'
)

Related issues 1 (0 open — 1 closed)

Is duplicate of Foreman - Bug #34058: Strings with enter don't get extracted for translationClosedMaria AgaphontzevActions
Actions
Copy link
 #1

Updated by Ewoud Kohl van Wijngaarden almost 2 years ago

  • Parent task set to #36116
Actions
Copy link
 #3

Updated by Ewoud Kohl van Wijngaarden almost 2 years ago

Weird, I did not see it actually extract the message so perhaps there's another bug?

Actions
Copy link
 #4

Updated by Maria Agaphontzev almost 2 years ago

the bug is fixed but there is no rubygem, this is the same issue as this https://projects.theforeman.org/issues/34058 , right?

Actions
Copy link
 #5

Updated by Ewoud Kohl van Wijngaarden almost 2 years ago

  • Is duplicate of Bug #34058: Strings with enter don't get extracted for translation added
Actions
Copy link
 #6

Updated by Ewoud Kohl van Wijngaarden almost 2 years ago

So there was a 1.3.1 gem release which does include the fix (https://github.com/webhippie/gettext_i18n_rails_js/commit/34c682d50b842fa04a23c8ef2ea4311e6af73c2e) so perhaps the fix is incomplete or we're not matching the regex in a different way.

Actions
Copy link
 #7

Updated by Ewoud Kohl van Wijngaarden almost 2 years ago

  • Status changed from New to Duplicate

I can't reproduce the problem anymore.

Actions
Copy link

Also available in: Atom PDF