Seems there’s a need to create an investigation task for my team, no quick solution, unfortunately.
I’d like to ask you to open a page with the query parameter “disable_jipt” in the URL to disable the rendering of the jipt and see if Angular has normally replaced the constant inside the string.
Some basic assumptions:
If everything was replayed fine, then the problem is in the work of the jipt.
If not, then the problem is in how Angular works with our placeholders.
Sorry for not having the best news, but yes, the task is not done yet and is unlikely to be done anytime soon.
Due to only one request regarding this issue and the difficulty of its testing and subsequent implementation of a fix, more priority tasks were selected for development.
We added some improvements to Angular localization workflow, for example, this application:
We haven’t received any new requests since my last message in this thread, except yours, so for now the situation remains the same. Still, in case there will be additional changes or improvements in the future - we will notify you!
Found this topic, while having the same problem. This is what Crowdin support recommended for us:
Replace all { and } with [% and %] accordingly inside <target/> tags in your .xlf file. You will have something like: <target>crwdns927293:0[%[% title %]%]crwdne927293:0</target>
Add new handler to _jipt during initialization _jipt.push(['before_dom_insert', function(text, node, attribute) { return text.replace(/\\[%/g, '{').replace(/%\\]/g, '}'); }]);