Issue metadata
Sign in to add a comment
|
Chrome doesn't ask for translating the page when it's Hungarian
Reported by
er...@door2door.io,
Jan 4 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36 Steps to reproduce the problem: 1. Enter Hungarian website 2. The bar that chrome usually displays when entering a page that is in a language not featured in my "read languages" setting doesn't show up. What is the expected behavior? So far, all the other languages work. I enter the page and the translation request bar shows up normally. What went wrong? If I enter an Hungarian page, the bar doesn't show up. Hungarian is *not* on the list of "read languages" in my settings, my chrome is updated, my cache and cookies were cleaned, anonymous navigation also doesn't work. Did this work before? Yes I don't know. Chrome version: 55.0.2883.95 Channel: stable OS Version: OS X 10.11.1 Flash Version: Shockwave Flash 24.0 r0 Your twitter support mate asked me to write this. I believe Chrome is having a severe case of festivities hungover, but you mates better take a look, just in case.
,
Jan 5 2017
@erica -- Could you please provide us sample websites , that would be easy for us to triage the issue. Thanks!
,
Jan 5 2017
Sure! The website where I "found the problem" was this one: greengo.hu And then I also tried the government one: http://www.kormany.hu/hu and is also not working.
,
Jan 6 2017
,
Jan 6 2017
I'm not able to repro this on 55.0.2883.95 or 57.0.2973.0. Just to be sure, you have "Offer to translate pages that aren't in a language you read." turned on in settings?
,
Jan 9 2017
Unable to reproduce the issue on Mac 10.12.2 using 55.0.2883.95. Could you please check the settings as per above comment # 5 and let us know further on it.
,
Jan 9 2017
I have the offer turned on in settings, yes. And the only languages there are: English, Spanish, Portuguese, Japanese and French
,
Jan 13 2017
,
Jan 14 2017
Can you please: * Open the page chrome://translate-internals (you need to copy the link, this is not clickable) * Make a screenshot and attach that here * Open chrome://translate-internals/#detection-logs (please copy, again, not clickable) * Open a new tab, navigate to http://www.kormany.hu/hu * Go back to the tab with detection logs * Click the "Dump" button * Attach the resulting file to this bug. This gives us additional info that might help find out what is happening
,
Jan 23 2017
Thank you for providing more feedback. Adding requester "durga.behera@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 25 2017
[mac triage] still needs feedback. (Translate folks, if you're watching, do you have your own triage for the UI>Browser>Translate component - it would be nice to remove from Mac-specific triage - thanks!)
,
Jan 25 2017
Translate does not have a triage process. ftang@ or I can help with any translate issues, though. (And adding the translate component should automatically mail me. I *really* wish that was noted in the CC field) Either way, we'll need the info I requested in c#9 - I cannot repro this in 57.0.2985.0 or 55.0.2883.95 on OSX. A wild guess is that the user doesn't translate all hungarian pages, and the heuristic has decided to not show the offer any more, but I can't verify without the feedback. erica@ - would it be possible to get us the additional info?
,
Jan 25 2017
Sorry!! I missed the email asking for the extra info! I've attached both things you asked me. And, as I entered the http://www.kormany.hu/hu website, the hungarian translation question is showing up now. However, this one: https://www.greengo.hu/ is not showing up the question. Let me know if you need anything else and sorry again for the delay :)
,
Jan 26 2017
Hm. I'm puzzled. Especially since https://www.greengo.hu is detected as Hungarian for me. The very first time I navigated there, there was a *long* delay before it showed the identification (~1min?), so I wonder if that's what you're seeing. abakalov@: Can you think of any reason why language detection on the very first visit would take that long?
,
Jan 26 2017
Some relevant context -- M55 Stable is using the old language detector (CLD2). We are in the process of replacing it with a new model (CLD3) which is currently in M56 Beta. erica@: Can you please attach the log for www.greengo.hu as well and for www.kormany.hu/hu when the Translate bar doesn't show up? The file you attached is for www.kormany.hu/hu for the case when everything works fine. I loaded www.greengo.hu twice. CLD2 correctly predicted Hungarian, but the content language was first rendered as English, and as I reloaded -- Hungarian. The discrepancy between the prediction and content language in the former case lead to having "und" (or "undefined") as adopted language, so the Translate bar didn't show up. The same might be happening for kormany.hu/hu. Alternatively, if for some reason the page takes longer to load, then no text is passed to the language detector. As a result, the predicted language is again "und". groby@: Did you observe the delay with M55 or M56? I cannot reproduce it with either of them.
,
Jan 26 2017
In my case, the translation bar doesn't show up at all, not just with a large delay. There's the print for both logs:
,
Jan 26 2017
Thanks for this information. Does the translation bar not show up for both of the urls in this log, or just the second one, i.e., greengo.hu?
,
Jan 26 2017
Just the greengo.hu, the other one is fine.
,
Jan 26 2017
I am getting the same outcomes as the ones in the most recent log you pointed out. As mentioned earlier, the detected language (Hungarian) is different from the content language (English), and because of this discrepancy Translate doesn't trigger.
,
Jan 27 2017
[mac triage]
,
Apr 17 2017
Looks like the site in question greengo.hu updated their content-language to Hungarian so the language gets determined correctly now (see attached screenshot) although that doesn't change the fact that we need to figure out how to deal with disagreements between content-language and detected language. I'm duping this into 678398
,
Apr 27 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Jan 5 2017