Hi,
There is an issue with quote escaping.
Some language strings may contain quotes which should be escaped by a translator.
I am using this construction:
<a href=\"https://
But when I download the file from Transifex, I see such construction:
<a href=\\"_QQ_"https://
\" is being converted into \\"_QQ_"
and the translation falls.
Please check it out.
I have the same issue.
Quotes, newlines, and dots are wrongly encoded.
{
"service_mail\\.banner\\.html_msg": { // <-- dots
"character_limit": null,
"context": "service",
"developer_comment": "",
"string": "<p>Follow the link: <a href=\\\"{1}\\\">{1}</a></p>" // <-- quotes
},
"service_mail\\.template\\.text_msg": {
"character_limit": null,
"context": "service",
"developer_comment": "",
"string": "{1}\\n\\n ---------------------------------------------------------------------\\n\\n {0}\\n" // <-- new lines
}
}
How do I get the same format as i used in the upload?
Hello ,
Thank you for contacting Transifex.
We have opened a ticket to our dev team and they will look into this so that our parser does not escape in this way these situations. we do not have an exact date that this will be resolved yet.
We will of course post an update when we have news.
Kind regards
Christos
I solved the issue by using parameter “data.attributes.mode” = “default” instead of “json”.
The “json” mode was causing the double escaping of characters.
Hello dear Michael ,
I am very glad we managed to sort this out .
I have also forwarded this observation to our devs for further investigation.
Kind regards
Christos
We have this issues too – @michael-wirth: where can I find this parameter settings?
This can be related to the mode (file type in the newest API version) they use when downloading the HTML resource via the API. When using this endpoint to fetch translations from a resource, you can select the desired file format for the output:
You can attempt to obtain your translation file in a different format and let me know if this resolves the issue. Please inform me if this clarifies the situation or if you need further information.
Thank you for your anwser.
Is it possible to change it for the download via web interface too?
Also there escaped quotation marks are converted into "_QQ_"
Hi @hekla
My name is Carlos from Transifex support, for the UI the only option to download translations is the
Except from the third option the rest will download the translations in the original format that the file was uploaded
I’m attendant to your comments
Best regards,
Hello Carlos,
I’m working on the same project as @hekla (JEM event management for Joomla) and asking this question on his behalf:
We are using the tx client for downloading all translations. Does the tx client allow fetching the translations in various modes (Default, XLIFF, JSON)?
Or is there a project setting that defines the mode in which translations will be downloaded? (I didn’t find it when browsing our project page).
Thanks in advance for your assistance!
Hello @ernst67,
I am Antonis from the Customer Success team. I hope you’re well.
The options you mentioned (default, xliff, json) are indeed available through the CLI by using their corresponding flags --xliffand --json. You can find this information and additional details in our CLI documentation. These modes should be available for all file-based projects.
Please let me know if this helps!
Hello Mylon,
That’s great and it should help us out. I set up and tested but got…:
“Your plan does not support advanced API features”
Alas, I guess we need to find another solution.
Oh, that was when I used the --xliff flag. I just tried the --json flag and that worked.
My team member will test it.
Hello @ernst67,
Yes, this is expected. Converting a file from its original format to XLIFF is available from our Growth plan and up, as mentioned in our documentation.
Converting to JSON doesn’t have that limitation, so if either format works for you, you can use JSON, which is included in your organization’s plan.
I hope this helps!
I’m afraid we’re a little bit stuck here.
For our project we need .ini files (it’s a Joomla translation) but when using the .tx client all double quotes are converted into QQ in the downloads.
I understand that downloading as JSON does eniminate the issue but it renders us with useless files. Is there any other way to download the files via the .tx client without the contents of the files being altered (" into QQ)?
Hello @ernst67,
Thanks for reaching out about the double quotes converting to “QQ” in your .ini files when using the Transifex client.
This happens because Joomla .ini files have specific ways of handling double quotes in translation strings. The “QQ” you’re seeing is actually related to an escape sequence (“QQ”) that Joomla used to represent double quotes within translation strings.
Different Joomla versions handle this differently - newer versions use backslash escaping while older versions used the QQ method.
Could you please let us know which version of Joomla you’re working with? This would help us recommend the most appropriate solution for your situation.
For now, you might consider a simple post-processing script to convert the QQ back to proper double quotes after download or just using the find and replace function with a text editor.
Best regards
Hello Mylon,
Thanks for the response.
The JEM component is currently for Joomla 4 and 5. Joomla now handles " where as our old versions (for Joomla 2 and 3) neede QQ indeed.
Replacing the double QQ by quotes is quite a task because we have multiple files and more than 30 translations. We should have to automate that task.
But if there is a better solution we would be happy to know.
Thanks
Hello @ernst67,
Thanks for the additional context about your JEM component for Joomla 4 and 5.
Regarding the double quotes converting to QQ in your .ini files: From my research, Joomla 4 and 5 should maintain compatibility with the QQ format for double quotes, even though the newer standard is to use backslash-escaped quotes. This backward compatibility means your files should continue to work properly despite the conversion.
While it’s recommended to use the newer standard for future development, your current translated files with QQ should function correctly in Joomla 4 and 5.
I’ll share this feedback with our team so we can look into updating our Joomla parsing to align with the most recent standards.
As for replacing the QQ with double quotes, please double check first if backwards compatibility is maintained with your versions. If it isn’t, it sound like creating a script and doing a one time conversion when you get all your files from Transifex would be the best approach until we update the file parsing for Joomla .ini files on our end.
Best regards
OK Mylon, thanks again.
We kept the Joomla 2 and 3 translation files as current because we don’t maintain that version of our component any more. Both of those Joomla versions are obsolete.
The feedback I’m getting is that the double QQ keeps appearing in the trnslations, so we might be doing something wrong in the language strings itself.
We do hope your developers can work something out. There must be more Joomla translations hosted on Transifex facing the same issue.
Thanks again
Hello @ernst67,
Thank you for getting back to me.
I have updated the related ticket. Once we have any news we will update this thread.
Best regards
