Put the Language button fixed floating for easy changing

GF-Huang commented 5 years ago

Because most of the time it is through Google search to jump to the document page, sometimes Chinese, sometimes English, but most of the Chinese machine translation is difficult to read, but there are some exceptions.

So I basically decide whether to jump to an English page depending on the quality of translation, but every time I must scroll to the bottom of the page to click Language button or modify the URL from en-us to zh-cn.

So I hope to be able to put the button at the top of the page or to fixed in a certain position floating like the sidebar. Thanks.

ryanmajidi commented 5 years ago

@SonjaSaltzman Can you please take a look at this issue?

SonjaSaltzman commented 5 years ago

@bodhigautam could you please follow up?

bodhigautam commented 5 years ago

@shirgoldbird Here is the feedback from the customer to put the language picker tab on the top for easy switching between the languages. I remember we discussed this before and it cannot be done as it doesn't comply with Microsoft Standard. Are we flexible to take this into consideration ?

firdacz commented 5 years ago

Why was the switch removed? There used to be a switch on the top whenever any article was machine-translated. Now, there is only the useless notice (which you have to cross-away), awful translation (Czech Language in my case) and no switch on top. Is there any way to change that bad decision to remove the switch? Whom to write, where to vote?

Is there any other way to make the switch back to English easier? I know I can scroll to the bottom (Ctrl+End) and switch the language, but why is it at the end of the page for gods sake?! Why isn't there easy button for english right next to Czech (or whatever the target language happens to be), especially when the article is (very poorly) machine-translated?

BTW: Czech Language is hard (and many other as well), so I get it the machine-translation is hard and the result poor. Just admit it and stop creating obstacles (whoever made the choice to remove the switch - I can imagine some CEO can reason: it has to work, we do not need the switch, remove it to make the team work harder on the translation... but the reality is obviously different). Cheers!

SonjaSaltzman commented 5 years ago

Hello Firdacz, the toggle "read in English" should still be there... could you please send us a URL where it was removed, so we can check what is going on? For example, this topic has it: https://docs.microsoft.com/cs-cz/azure/guides/developer/azure-developer-guide We are continuously working on improvements and hope the quality will increase, even for machine translated content (we rolled out a neural MT engine late summer, which improves fluency and accuracy, and hope users will note this over time). We also continue to work on features, such as allowing users to set their preferred language (e.g. English), and no matter if a search engine returns a link with another language (e.g. Czech), the site will provide you the preferred language. This feature is not yet developed, but it's on our to-do-list.

firdacz commented 5 years ago

@SonjaSaltzman E.g. https://docs.microsoft.com/cs-cz/dotnet/api/system.threading.thread.volatileread?view=netframework-4.8

obrazek

But I can confirm it is there for the Azure: obrazek

GF-Huang commented 5 years ago

I add that even putting the switch on the top does not bring the best experience.

Suppose you are reading a translated page. Most of the previous translation quality looks good, but when you read the middle of the page, you see a bad translation, you can't understand it, you need to switch back to English, but you have to scroll to the top of the page, click the switch, and scroll to the previous position.

Why not keep the switch fixed floating like the sidebar ?

SonjaSaltzman commented 5 years ago

Thank you for the fast response with sample URL @firdacz and good design idea from @GreatFireWall. Will try to address both:

the URL with missing toggle is for reference content (api documentation); the toggle switch does not work properly on this content type, and thus was disabled by our engineering team. @bodhigautam is working on future features to address this problem, but it may be a longer-term fix.
@bodhigautam, can you please take the "floating toggle" design idea back to the design team? This would help the user to not have to first scroll up, and then scroll down again.

bodhigautam commented 5 years ago

Thank you so much @firdacz @GreatFireWall for your ideas. We have taken your suggestion for the floating toggle. We will surely discuss it with the Design team. The toggle feature is targeted for March 2020 across docs. We will keep you posted with any changes/updates to the timeline. cc @SonjaSaltzman

srvbpigh commented 4 years ago

Hello, @GF-Huang

Thank you for your feedback.

We are actively reviewing your comments and will get back to you soon.

Kind regards, Microsoft DOCS International Team

CeciAc commented 4 years ago

Removing myself from the assignees since this is not a loc issue

MicrosoftDocs / feedback

Put the Language button fixed floating for easy changing #1715