Plugin Support
Alex
(@alexcozmoslabs)
Hi,
Any change of the original string will invalidate the front-end translation as they are directional. This is how our plugin works because we save each translation in the database. Every string has a corresponding translation. If you change the original string, basically, you create a new string that will need to be translated.
To facilitate translation retrieval we implemented the Translation Memory* feature.
For example, if you have a string in your default language that is translated and you go in and modify that string, the translations for it won’t appear anymore at the front-end level but will continue to exist in wp_trp_… tables from your database. After, if you go to the translation interface and select that string, the Translation Memory feature will show you translation suggestions for that string (based on other strings that you have translated, even the ones which don’t appear anymore in the front-end; so most likely, you will see the older translation as the first suggestion).
*The translation memory is approximate, based on what strings are in the database. It’s possible sometimes that doesn’t work 100%.
Put simply, every two seconds I HAVE to rewrite all the text in Italian because you don’t have an option to prevent the text from becoming in English? I have a plugin that adds links, so the translation should NOT change, but have the link for the Italian page.
If I understand correctly, do I have to change the multilingual plugin?
Just learning about TranslatePress and this is also raising some worries to me. Even though when you manually make some modifications (replace a word, fix a typo, etc.) it seems it’ll invalidate the entire translation string/block.
As the support said, this is how the plugin works obviously. While I think it’s a good idea instead of having duplicate pages for every single translation (other plugins), it shows the huge drawbacks quite soon unfortunately.
I am completely new to the plugin, but as this post is very new, I would like to use it give quick feedback to the support / plugin author.
1. do not delete any translation strings when new content is added to the source post/page
2. warn the user when the source string is changed that this will invalidate (delete) the translation
3. show an overview of all invalidated translations, so that at least its easier to fix it
Please excuse if not all suggestions make sense / I didn’t test everything just yet
Yes, invalidating the translation such as adding a script, for example, is quite nerve-wracking. We have to do more work. The text does not change, apart from the script. The worst part is when I have thousands of articles and it will take us months to fix a feature that should be automatic.
I am interested whether there is any improvement to this and hope someone from support will reply again. I thought about purchasing, but that turned me off for now.
I am not even talking about automatic changes by a script, but even the manual changes should not invalidate the current translation. I see the memory translation function is a first approach to tackle that, but I can’t imagine how someone can keep all the translations up to date
At the moment I am struggling to renew the hosting, but I also have doubts whether to buy the pro version in the future, precisely because the translations are forgotten.
Plugin Support
Alex
(@alexcozmoslabs)
Hi,
Thank you for your feedback, guys.
Our team is already considering part of these matters and will try in the future to improve the process of retrieving translations when the original source string is changed. for the moment we do not have an estimated time, but we want to improve the way we handle string changes.
For the moment the only way can prevent a string no to lose its translation is if is a paragraph and you know what word/link/striptt from this will be changed in the future to insert/separate it from he rest of the paragraph using <span></span> tags or translation-block approach. You basically make that isolated text/link/script a new string, different from the big one wich is the paragraph.
-
This reply was modified 3 years, 8 months ago by
Alex.
