You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running l10n_tools/compile.sh produces many "fatal errors" with the below format:
messages.po:249: 'msgid' and 'msgstr' entries do not both begin with '\n'
messages.po:284: 'msgid' and 'msgstr' entries do not both begin with '\n'
messages.po:321: 'msgid' and 'msgstr' entries do not both begin with '\n'
messages.po:352: 'msgid' and 'msgstr' entries do not both begin with '\n'
messages.po:362: 'msgid' and 'msgstr' entries do not both begin with '\n'
messages.po:381: 'msgid' and 'msgstr' entries do not both begin with '\n'
It's not clear if these are really fatal or not They don't seem to be really fatal, but we should investigate. I suspect something like localizers removing \n's when they shouldn't, or Pontoon messing up the formatting. Perhaps we can remove \n's from the beginning of strings since it's unlikely they do anything in HTML content.
The text was updated successfully, but these errors were encountered:
From modifying problem line in a locale.po file locally, and compiling again I can confirm that this isn't fatal. What's probably happening is jinja2 isn't stripping newlines when using block tags. Shouldn't be too hard to fix by either removing the new line like:
{% trans %}
Thunderbird is great!
And this is sample text!!
{% endtracks %}
to
{% trans %}Thunderbird is great!
And this is sample text!!
{% endtrans %}
or there may be a setting in jinja that auto strips this out.
Running
l10n_tools/compile.sh
produces many "fatal errors" with the below format:It's not clear if these are really fatal or notThey don't seem to be really fatal, but we should investigate. I suspect something like localizers removing \n's when they shouldn't, or Pontoon messing up the formatting. Perhaps we can remove \n's from the beginning of strings since it's unlikely they do anything in HTML content.The text was updated successfully, but these errors were encountered: