I would like to share my understanding and the background of the revert.
IIUC, while we use babel to extract messages for translations, we use angular-gettext to display translated messages. A source string extraction logic in both (babel and angular-gettext) should match for angular-gettext looks for translated messages successfully. The reverted patch https://review.openstack.org/330183 changes only the babel extractor and as a result we fail to show translated message for multi-line text.
As translator perspective, it would be nice if this bug is fixed, but we need to be careful. To fix this bug, I think angular-gettext needs to support 'trimmed' option provided by Django for Django templates.
I would like to share my understanding and the background of the revert.
IIUC, while we use babel to extract messages for translations, we use angular-gettext to display translated messages. A source string extraction logic in both (babel and angular-gettext) should match for angular-gettext looks for translated messages successfully. The reverted patch https:/ /review. openstack. org/330183 changes only the babel extractor and as a result we fail to show translated message for multi-line text.
As translator perspective, it would be nice if this bug is fixed, but we need to be careful. To fix this bug, I think angular-gettext needs to support 'trimmed' option provided by Django for Django templates.