-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add banner to localized pages #3588
Comments
@schalkneethling Could you take this one? |
I think we could ask each of the respective localization communities within the active locales on https://github.com/mdn/content to provide translations of the text we've selected for the active locales, and I'm thinking we can find others to help us with translations for the text for the inactive locales (e.g., @Gregoor for |
If I may be of any help :) (I was just wandering across the repos)
could be translated in French by
|
@schalkneethling Exciting! Looks good so far! 🎉 |
Hey @schalkneethling, in case you still need deutsch, here's my attempt at speaking die Sprache:
could be translated to
Tastes may vary (it feels a little wordy, but that's german for ya) |
Vielen Dank, Gregor! I shall use it. |
I was just wandering across the repos too.
could be translated in Korean by
@chrisdavidmills I hope it helped a little. :) |
Nice, thank you so much @hochan222. |
Moves notecards into Yari. Add localized content notes for active and inactive translated content. Fix #3588
* fix: localized content notes Moves notecards into Yari. Add localized content notes for active and inactive translated content. Fix #3588 * changes based on review feedback * update string for inactive locale note content for en-US * changes based on review feedback * Update client/src/document/molecules/localized-content-note/index.tsx Co-authored-by: Peter Bengtsson <peterbe@mozilla.com> * Update client/src/document/molecules/localized-content-note/index.tsx Co-authored-by: Peter Bengtsson <peterbe@mozilla.com> * prettier Co-authored-by: Peter Bengtsson <peterbe@mozilla.com>
* fix: localized content notes Moves notecards into Yari. Add localized content notes for active and inactive translated content. Fix mdn#3588 * changes based on review feedback * update string for inactive locale note content for en-US * changes based on review feedback * Update client/src/document/molecules/localized-content-note/index.tsx Co-authored-by: Peter Bengtsson <peterbe@mozilla.com> * Update client/src/document/molecules/localized-content-note/index.tsx Co-authored-by: Peter Bengtsson <peterbe@mozilla.com> * prettier Co-authored-by: Peter Bengtsson <peterbe@mozilla.com>
I think the "커뮤니티에서 영어로 번역되었습니다" part seems bit awkward, because it means "translated to English" isn't it?
With some more explanation in it, would be:
What do you think? @hochan222 |
@gidongkwon Since then, I have corrected it in another PR. If you go to the Korean page, the modified text will appear at the top. https://github.com/mdn/yari/pull/3733/files
|
Looks good. Thanks |
Intro
Let's add a banner to all localized pages for the 10 supported non-English locales. The banner has to account for two cases:
ru
,ko
,fr
,ja
,zh-CN
, andzh-TW
de
,es
,pl
, andpt-BR
Location and look
Let's go with @dalexsy's second mockup:
Text
Let's hard code the translations of the English text into the banner for each locale.
Active locales
Let's go with translations of @ddbeck's text for the 6 active locales (text below shown for French as an example):
Where the language community links for each language would be as follows:
zh-CN
andzh-TW
): https://developer.mozilla.org/en-US/docs/MDN/Contribute/Localize#chinese_zh-cn_zh-twfr
): https://developer.mozilla.org/en-US/docs/MDN/Contribute/Localize#french_frja
): https://developer.mozilla.org/en-US/docs/MDN/Contribute/Localize#japanese_jaru
): https://developer.mozilla.org/en-US/docs/MDN/Contribute/Localize#russian_ruko
): TBD (@chrisdavidmills can provide this when it's ready)Inactive locales
Let's go with translations of @chrisdavidmills' text for the 4 inactive locales:
The text was updated successfully, but these errors were encountered: