codeshop

Hi @iarinadasdi , thank you for your answer.

I think it should be handled by TranslatePress and that others have the same problem, that is why I am writing.

There is nothing really special about my shop in terms of strings (except the above mentioned hotfix I applied). I created products via a totally standard workflow (not doing any & or ä manually) and translated them with TranslatePress, yet some of them are not translated in the standard cart.

I believe it is because:

• WordPress stores the data created/edited in the Backend in HTML encoded format.
  • TranslatePress sees the encoded strings during its runtime.
• Dynamic content (the JS based cart) is rendered and then handled by TP.
  • TP sees the decoded version of the same string.

It’s not viable to translate the same string twice, right?
It’s also better not to apply some magic tricks to force it to work, which you might forget to apply consistently.

I see no problem on the end user side. If you believe so too, please reconsider fixing it in TranslatePress. I will keep my patched version for now.

Kind regards

• This reply was modified 8 months ago by codeshop.