Patch (to be ported)
Project:
TMGMT Translator Google
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Major
Category:
Bug report
Assigned:
Reporter:
Created:
27 Aug 2012 at 08:21 UTC
Updated:
15 Mar 2016 at 14:37 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
zhuber commentedI don't think this needs to be fixed actually.
I've tested this out on my own and found out that it only maintains the html encoding when the apostrophe cannot be translated.
For example:
"John's node example" translates to "Ejemplo nodo John"
The issue happens when google cannot translate the apostrophe, with something like this:
"John has a node!'." translates to "John tiene un nodo! '."
This could be potentially fixed, but for now it's best practice to provide translatable content. Beyond that, you can and should manually edit the translated content if it isn't translated the way that you want.
Comment #2
berdirRight, it's fine if it's stays there. But it shouldn't be html encoded because that results in double encoding?
Comment #3
zhuber commentedI think I've fixed it, although I don't know if this will have implications with users who try to translate chunks of html (from WYSIWYGs or open html fields).
Comment #4
berdirTestbot bump. A test would be good to have here...
Comment #5
berdirPromoting, this is still a problem.
Comment #6
thenchev commentedStart looking into this.
Comment #7
thenchev commentedFor me, and mbovan tested it also, the google translator returns the correct result. The problem i see is in the revisions.
Comment #8
thenchev commentedSorry, looks like the title is affected. Missed that
Comment #9
thenchev commentedi suppose this should be reflected on the microsoft translator?
Comment #11
berdirYes, this works well now. Committed, back to 7.x