Currently AngularGettextHTMLParser parses translations of form
{$ 'content' | translate $}. However, there is another form in
projects' html files: {$ ::'content' | translate $}.
This commit fine-tunes the filter_regex and related handle_xxx
functions to extract both forms of translations.
Closes-Bug: #1824644
Change-Id: I7129a13d046b699328b77267ae4936d31af8144c
(cherry picked from commit 5de40b3f397f812d5236a274b22515b18118015c)
Reviewed: https:/ /review. opendev. org/651547 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=6407c81be00 1b6ddeb788645f0 a087b40ff67986
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 6407c81be001b6d deb788645f0a087 b40ff67986
Author: francotseng <email address hidden>
Date: Wed Apr 3 14:17:37 2019 +0800
Complete angular translation extract pattern
Currently AngularGettextH TMLParser parses translations of form
{$ 'content' | translate $}. However, there is another form in
projects' html files: {$ ::'content' | translate $}.
This commit fine-tunes the filter_regex and related handle_xxx
functions to extract both forms of translations.
Closes-Bug: #1824644 9328b77267ae493 6d31af8144c d5236a274b22515 b18118015c)
Change-Id: I7129a13d046b69
(cherry picked from commit 5de40b3f397f812