Hey everyone,
I am currently working on a localization workflow for a regional utility portal project and running into a weird string parsing bug that I hope someone here might have seen before. While attempting to extract dynamic text components and pull right-to-left UI strings from this website for translation mapping, the parser fails to properly identify specific dynamic content blocks and keeps stripping localized punctuation tags. I initially thought it was a basic encoding mismatch, so I tried forcing UTF-8 encoding across the translation pipeline, updating regex selectors, and cleaning up space characters, but the translation manager still drops dynamic placeholders during export. Has anyone experienced similar issues where dynamic RTL strings break string key extraction during file syncs, or is there a recommended configuration in the platform settings to better preserve right-to-left layout directionality when importing web content? Any suggestions or technical workarounds would be very appreciated.
Thank you for reaching out and for the detailed description.This kind of issue can have a few different root causes depending on your setup, so before suggesting a specific fix, it would help to know a bit more about your configuration:
• What type of Transifex project are you using? For example, a file-based project, Transifex Live, or a GitHub/API integration?
• What file format are you working with? PO, XLIFF, JSON, or something else?
• Could you share the URL of your Transifex project? This will help us look into the configuration.
• Could you share a sample of a string that is failing, including what the parser outputs versus what you would expect?
• Are the dynamic placeholders following a specific format or convention, such as {variable}, %s, or ICU syntax?
With that context we will be able to point you in the right direction and provide a more accurate solution. Looking forward to your response
Best regards,
Carlos, Transifex TAM