Unwanted box is seen near 'CREATE BLOG' link on blogger.com after translation.
Reported by
db...@etouch.net,
Sep 15 2017
|
||||||||||
Issue descriptionChrome Version: 63.0.3216.0 Revision c3592928ad6753206a00d98787a578cda6153570-refs/heads/master@{#502108} OS : Windows (7,8,10), Linux(14.04), Mac(10.11.6, 10.12.3, 10.12.5) What steps will reproduce the problem? (1) Launch chrome, navigate to https://www.blogger.com/about/?hl=pl and click on 'Translate' button. (2) Scroll down the page slightly,observe near 'CREATE BLOG' link. Actual: Unwanted box is seen near 'CREATE BLOG' link. Expected: No such box should seen. This is a non-regression issue, seen from 'M-45'
,
Sep 19 2017
Able to reproduce this issue on Windows-7, Ubuntu 14.04 and Mac OS 10.12.6 using chrome latest stable 61.0.3163.91 and canary 63.0.3218.0. This is a Non-regression issue which is observed from M50 chrome builds. Hence marking this as 'Untriaged'. Thanks
,
Sep 20 2017
I was able to reproduce. It happens when translating to any language that is different from the original (so not only to English).
,
Sep 21 2017
Playing around with more repro cases, this issue is more visible when translating from EN to JP (screenshot attached). Ultimately this is a segmentation problem, with the rules which attempt to join adjacent text nodes in order to provide better overall translation context. E.g. some words in the middle of a sentence are tagged as a link, and we want the entire sentence to be translated to preserve its intent. In this case, the "Sign in" and "Create your blog" text nodes are wrapped in neighboring link tags - which is considered by the segmentation to be part of the same context/sentence. That these are styled to look like buttons is not considered by the dom parsing and segmentation, so sees it like a single sentence. The translation result of these 2 text segments for EN->JP are 5 text strings (with the last one being empty - which may be a separate bug). These are each added and are subsequently styled like menu buttons. Unfortunately there's no simple tweak to the segmentation rules that will fix this bug without undoing the benefits of clustering text segments into sentences for general prose. Filed an internal bug for the translate backends, as this is not specific to Chrome. Dropping to P3 as it is not immediately actionable.
,
Sep 26 2017
,
Mar 7 2018
|
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by msrchandra@chromium.org
, Sep 15 2017