Home › Support › English Support › [Resolved] Advanced Translation Editor does not accept blank translations

[Resolved] Advanced Translation Editor does not accept blank translations

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Our next available supporter will start replying to tickets in about 2.23 hours from now. Thank you for your understanding.

Tagged: 

This topic contains 4 replies, has 3 voices.

Last updated by Richard Bolton 7 months, 3 weeks ago.

Assigned support staff: Andreas W..

Author Posts
October 8, 2019 at 7:19 pm #4717847

Richard Bolton

I am trying to: Have some English sentences not translated into the French version.

Is there any way to do this with the Advanced Translation Editor?
October 9, 2019 at 12:45 pm #4723005

Sumit
Supporter

Languages: English (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hi,

Thank you for contacting the support forum.

Yes, that is true. You can save the blank string as a translation of string instead you can keep the same string in French to display the string in English.

I hope it helps.

Thanks
October 9, 2019 at 5:12 pm #4724781

Richard Bolton

When I try to save a blank translation, I receive the message:

"Translation not saved"
"The translation cannot be empty. Enter translation and try again."

It will also not let me "Finish" with blank translations. The message is:
Job not finished

"Save and complete the translation of all sentences, then finish the job"

Is there any way around this?
October 9, 2019 at 10:22 pm #4725807

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

Thank you for contacting the WPML support forum.

Please try adding a blank space or use the extended HTML character:

Try editing the field with:  

Let me know if this solved the issue.

Kind regards
Andreas
October 10, 2019 at 9:50 pm #4734217

Richard Bolton

Thanks Andreas, the extended character for "nbsp" works correctly, and I now realize that the editor strips out leading and trailing normal spaces which explains why they don't work.
Richard