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
{{ message }}
This repository has been archived by the owner on Oct 15, 2021. It is now read-only.
Please don't escape XML/HTML entities by replacing "&" with "& amp;" automatically. While it could be good for some projects, it breaks every string that contain an entity that should never be re-escaped.
For example, a string that contains "&brandShortName;" should never ever be encoded to "& amp;brandShortName;".
NOTE: I've added spaces after the ampersand characters because both are displayed the same the correct and wrong strings displayed the same. Of course, there is no spaced entities in the source files… ☺
The text was updated successfully, but these errors were encountered:
This also reproduce on other entities as well. In the screenshot below you can see an entity that contain some HTML markup, which gets destroyed after exporting the strings.
Transifex output is on the left pane, and these strings have imported and exported without being changed by human inside the Transifex site.
Please don't escape XML/HTML entities by replacing "&" with "& amp;" automatically. While it could be good for some projects, it breaks every string that contain an entity that should never be re-escaped.
For example, a string that contains "&brandShortName;" should never ever be encoded to "& amp;brandShortName;".
NOTE: I've added spaces after the ampersand characters because both are displayed the same the correct and wrong strings displayed the same. Of course, there is no spaced entities in the source files… ☺
The text was updated successfully, but these errors were encountered: