quarkusio.github.io icon indicating copy to clipboard operation
quarkusio.github.io copied to clipboard

Published 20 hours ago • verified publisher icon quarkusio

Include language selector into navigation

Open insectengine opened this issue 3 years ago • 6 comments
trafficstars

Describe the bug The Quarkus Community are porting versions of the site into localized languages but the current navigation doesn't take into consideration how users can navigate to the various localized sites.

currently, we have japanese (https://ja.quarkus.io/) but a version in chinese is currently in the works.

Which pages All pages.

insectengine avatar May 06 '22 16:05 insectengine

@ynojima - Since you commented on the PR for the original commit. I wanted to ask you a question. For better usability, I want to change the world "Japanese" to be written in actual Japanese. So native speakers will find it easier.

A google search says I should use this 日本語

Is this correct?

insectengine avatar May 13 '22 14:05 insectengine

Yes, "日本語" is an appropriate translation for "Japanese". Thanks!

ynojima avatar May 13 '22 14:05 ynojima

Thanks!

insectengine avatar May 13 '22 14:05 insectengine

If I may ask, it would be great if the language selector link is linked to the corresponding page.

For example, when I click the language selector link in "https://quarkus.io/container-first/", it should navigate to "https://ja.quarkus.io/container-first/" instead of "https://ja.quarkus.io/".

ynojima avatar May 13 '22 15:05 ynojima

If I may ask, it would be great if the language selector link is linked to the corresponding page.

For example, when I click the language selector link in "https://quarkus.io/container-first/", it should navigate to "https://ja.quarkus.io/container-first/" instead of "https://ja.quarkus.io/".

I see a couple issues with that approach:

  1. I don't think this either of our current link locations would be the proper location for a link that functions that way. Users expect those links to take them to another page all together and not to refresh the existing page. The action you are describing would be an on-page link for "Translate Page". This way the user expects to change the page's language.

  2. As I'm aware of the current state of translations, not all pages are translated. And if a user on a translated site hits a page that wasn't translated, they get the canonical page in English. This could lead to user confusion if the user is expecting that the link to function as a page translator and tries to switch a page that doesn't have the non-English version and gets served the English version on the translated URL.

insectengine avatar May 13 '22 15:05 insectengine

Thank you for clarification. I get it!

ynojima avatar May 14 '22 06:05 ynojima