Sometimes, I get many errors like this :

Translation rejected by https://mylocalizationserver.com Reason: Source string not found on server, translation not saved.

Or

Translation rejected by https://mylocalizationserver.com Reason: Suggested translation already appears as active translation or suggestion.

The thing is you never know if the strings you're translating are going to give you an error. When you're translating large paragraphs it gets quickly annoying. Thus, I wonder if it wouldn't be possible to offer a "Activate pre check from localization server" checkbox so that you can prevent this from happening ?

Let me know your thoughts !

Comments

Well, we can reword / tone down these warnings. They are not really errors, especially the second one. It just informs you you should not look for your suggestion being posted, since it is already there attributed to somebody else. We can alternatively skip displaying these messages or provide a killswitch to turn then off/on.

Title:Pre check if translation existsLocalization server error feedback is distracting

Also retiling for what the problem is, not for the solution proposed. I don't think pre-checking available strings with the server is a good idea, it would put a lot more load on the server, since it would check for even the string you are not going to translate. And it would need to provide some kind of feedback to let you know what happened. If you are not happy about the feedback, we should work on that, not when the check actually happens IMHO.

"Error" wasn't the best word I could have used, I agree. Nevertheless if you basically consider that you're trying to submit a new translation and it hasn't been accepted by the translation server...well you are stuck anyway. Besides, I don't think you should reword theses warnings as they are perfectly understandable.

Before I filled this issue I wondered how to improve the UX when you're confronted with these warnings. I fully agree about the useless server load but I cannot figure a better way to let the translator know that he's translating something that won't be useful (except locally) in the end.

Maybe this is a total misunderstanding on my side but I don't think it's possible to know that a translation has already been suggested except on the localization website (like localize.drupal.org) ? Else I wouldn't try to submit it of course.

Whether its a duplicate suggestion, we can only check once the full text was input on the UI. At that point we'd rather actually try to submit it, no? Why would we first ask if we should submit it if submitting it takes equal resources on the client and server side? Why double the resource requirements (in terms of user time and server load)? Whether a string is on the server, I'm not sure the client user would not translate it if its not on the server. The main goal of the l10n_client is for you to fix your local translation issues and missing pieces and the remote submission is kind of an icing on the cake. So I guess you'll still want to translate it for local use. Then why would we not try to submit it again once we have your suggestion, instead of pre-checking if you can submit and then actually submit if you can... Again, we can avoid double the resource consumption by doing it when we have all the information available.

Why would we first ask if we should submit it if submitting it takes equal resources on the client and server side?

Makes sense.

The main goal of the l10n_client is for you to fix your local translation issues and missing pieces and the remote submission is kind of an icing on the cake.

Makes sense too.

At least two good reasons not to change anything I guess. Thank you.

I just installed 7.x-1.0, I even do not see where the configuration page about translation server is?

@nardberjean: Look into the language list configuration and the sharing tab there.

@Gabor Thanks!