Translate content into Simplified Chinese

[tunetheweb]

These are the core templates - without which we cannot release any translated chapters. They are in the language specific templates directory:

• base.html - @chengxicn
• base_chapter.html- @chengxicn
• error.html- @chengxicn

2022

• base.html -
• contributors.html -
• index.html -
• table_of_contents.html -

2021

• base.html -
• base.html - foreword
• contributors.html -
• index.html -
• table_of_contents.html -

2020

• base.html - @chengxicn
• base.html - foreword added later
• contributors.html - @chengxicn
• index.html - @chengxicn
• table_of_contents.html - @chengxicn

2019

• base.html - @chengxicn
• contributors.html - @chengxicn
• index.html - @chengxicn
• table_of_contents.html - @chengxicn

These are the chapters to be translated, in rough order of popularity. They exist in the content directory:

2022

• css -
• javascript -
• markup -
• structured-data -
• fonts -
• media -
• webassembly - @luckybai - Simplified Chinese - WebAssembly Chapter 2022 #3237
• third-parties -
• interoperability -
• seo -
• accessibility -
• performance -
• privacy -
• security - @Levix - feat: add security chapter to 2022/zh-CN directory #3278
• mobile-web -
• capabilities -
• pwa - @ibelem - Translate 2022 PWA chapter for Simplified Chinese #3192
• cms -
• jamstack -
• sustainability -
• page-weight -
• cdn -
• http -

2021

• css -
• javascript -
• markup -
• structured-data -
• media -
• webassembly -
• third-parties -
• seo -
• accessibility -
• performance -
• privacy -
• security -
• mobile-web -
• capabilities -
• pwa -
• cms -
• ecommerce -
• jamstack -
• page-weight -
• compression -
• caching -
• cdn -
• resource-hints -
• http -

2020

• css -
• javascript - @Zuckjet
• seo - @Zuckjet
• markup -
• accessibility -@Zuckjet
• cms -
• performance- @Zuckjet
• security -
• jamstack -
• fonts -
• mobile-web -
• pwa -
• http2- @chengxicn
• capabilities- @chengxicn
• third-parties -
• page-weight -
• caching -
• resource-hints -
• privacy -
• compression -
• ecommerce -
• media -

2019

• javascript -
• css -
• seo -
• performance - @chengxicn
• http2 -
• markup -
• third-parties -
• fonts -
• accessibility - @chengxicn
• pwa - @limhenry: Google Docs
• cms -
• security -
• media -
• mobile-web -
• cdn - @chengxicn
• ecommerce -
• page-weight -
• caching -
• compression -
• resource-hints -

Additionally the following pages need translated too in the language specific templates directory, but less important than core templates and chapters:

• 2021/methodology.html -
• accessibility_statement.html - @chengxicn
• accessibility_statement.html additional update -
• base_ebook.html- @chengxicn
• 2019/methodology.html - @chengxicn
• 2020/methodology.html - @tunetheweb / @chengxicn - Add 2020 Methodology in Simplified Chinese #1422

Please include "Makes progress on #1067" in all pull requests so a link is created from the PR to this issue.

There is no need to translate the chapters HTML pages in src/templates/en/2019/chapters/ nor the src/templates/en/2019/ebook.html file as they are generated off the markdown combined with the above templates.

---

Common notes for writing consistency are here: https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Translators'-Guide. Feel free to edit that and/or add Chinese-specific extras by editing this comment.

Chinese specific extra advice:

[chengxicn]

start translating language specific templates directory.

[tunetheweb]

We found it best to put your name besides the parts you are doing on the first comment to tell others not to look at that one. I’ve done that with base.html as an example. Feel free to remove it from there and/or add your name to others you are working on so @AppleTsai knows to work on other ones.

[AbbyTsai]

Thanks your warm markers and tips.

[chengxicn]

Submitted first PR,but there are some errors(from 311) in accessibility.md check https://github.com/HTTPArchive/almanac.httparchive.org/pull/1072/checks , but I only translated front content，not sure why there are hard tabs can't pass the check yet. So have to delete accessibility.md and submitted a new PR again.

[rviscomi]

@chengxicn @AbbyTsai I'd like to post something from the HTTP Archive Twitter account to promote this translation effort and hopefully find more translators to help with it. Could someone translate this text for the tweet?

Do you speak Chinese? Help us translate the Web Almanac as part of our effort to make it globally accessible to the web community!

Thanks for your help!

[AbbyTsai]

嗨你喜歡英文嗎？歡迎加入Web Almanac網絡社群.讓我們攜手共遊無邊際的翻譯世界.
@chengxicn it's open to your comment.
I'll try to leave the message to network, hoping to pull more helper in translation.

[chengxicn]

@chengxicn @AbbyTsai I'd like to post something from the HTTP Archive Twitter account to promote this translation effort and hopefully find more translators to help with it. Could someone translate this text for the tweet?

Do you speak Chinese? Help us translate the Web Almanac as part of our effort to make it globally accessible to the web community!

Thanks for your help!

您会说中文吗? 来帮助我们翻译Web Almanac 网络年鉴吧！让我们一起努力消除障碍，让全球Web社区自由访问！

@rviscomi As I described before #1073 (comment) , mine and @AbbyTsai 's Chinese are very different systems, I'm working on Simplified Chinese and @AbbyTsai is working on Traditional Chinese, So we may need 2 groups of translators.

[rviscomi]

Thanks @AbbyTsai @chengxicn! I'll post two separate tweets using each dialect.

@tunetheweb it'd be good to split this issue into Simplified and Traditional so we can disambiguate for translators. I've renamed #1073 to clarify the dialect. For that PR I'd recommend completing the English translations into Simplified Chinese and waiting for a Simplified Chinese speaker to review it, or merge the PR if we can't find anyone soon. @AbbyTsai would you be able to work on a Traditional Chinese translation in parallel?

With two separate issues I'll be able to link the tweets to their respective dialects.

[tunetheweb]

That's done - #1106

Only question remains is do we use the zh folder and URL structure for one or the other?
Or have zh-cn and zh-hk? In which case @chengxicn can you update your PR?

[chengxicn]

I'm not sure if the folders have to comply with the ISO standard? could I name them 'cn-simp' and 'cn-trad' ?

[tunetheweb]

Technically they don't but would prefer to use something that's not completely unusal!

According to this https://stackoverflow.com/a/4894634/2144578 zh_CN and zh_TW seem to be the most common. Don't love introducing case into URLs though but can always revert to lowercase if it causes problems.

But willing to take your steer @chengxicn and @AbbyTsai since I'm sure you browser a lot more Chinese internet sites than me! 😀

[chengxicn]

Updated to zh_CN.

[AbbyTsai]

@rviscomi @tunetheweb I wish I could have triple hands to deal with both role of analyst and parallel translation, however, things don't go the way. After that schedule, I'll love to do translating in 2020 version. Thanks.
@chengxicn Happy to co-work together. Hoping to partner in the next project.

[Zuckjet]

I can help with chinese translation of 2020, especially about pwa and web security, since I have done these things in my work project this year

[tunetheweb]

Excellent! Edit the first post to stick your name beside a chapter and away you go!

Original english is in src/content/en/2020/ and should be translated and pull requested into src/content/zh-CN/2020.

Any questions feel free to ask!

[Zuckjet]

@tunetheweb I just edit the first comment under this issue like "performance- @Zuckjet". Does this mean I will take over the performance post for translation ?

[tunetheweb]

Correct. But let’s untick it until it’s actually translated and PR accepted.

[Zuckjet]

Correct. But let’s untick it until it’s actually translated and PR accepted.

Thanks for helping untick the list item, I will begin translate in these days

[tunetheweb]

One thing to note is that for accessibility reasons whenever we are leaving a phrase in the original English we like to add lang="en" attributes to that text (wrapping in a <span> tag if necessary).

Like this example in the Capabilities translation:

almanac.httparchive.org/src/content/zh-CN/2020/capabilities.md

Line 27 in 4883d30

[能力项目](https://www.chromium.org/teams/web-capabilities-fugu)，非正式的被称为<span lang="en">Project Fugu</span>，是谷歌、微软和英特尔通过跨公司的努力来弥补web和原生之间差距的工程项目。这对于保持web作为一个平台的相关性非常重要。为此，Chromium的贡献者们实现了新的API，将操作系统的能力（capability）暴露给网络，同时维护用户的安全、隐私和信任。这能力包括但不局限于:

Product names (e.g. HTTP Archive or Google Lighthouse) don't need this.

More tips in our Translators Guide

[Zuckjet]

the seo chapter of 2020 isn't be marked with unedited flag, is it ready for translate ?

[tunetheweb]

Yes it is. Updated the first comment with the latest list.

[Zuckjet]

Yes it is. Updated the first comment with the latest list.

I remember have checked performance, since have finished translation. but seems someone uncheck it again, anything should i do about that chapter?

[tunetheweb]

Sorry my fault. Got it confused with Traditional Chinese which hasn’t been merged yet. I have re-ticked it.

[tunetheweb]

We added a small note to our Accessibility Statement about colour contrast issues:

almanac.httparchive.org/src/templates/zh-CN/accessibility_statement.html

Lines 69 to 71 in 14f8512

	{# TODO - Translate this <p>
	We recognize that some of the color choices for our visualizations do not meet WCAG color contrast requirements. We make a conscious effort to use the more contrasting colors and labels to reduce the impact of this. We hope the detailed descriptions, as well as access to the underlying data itself can help with this issue. We aim to improve the accessibility of our visualization color schemes in future years.
	</p> #}

Would be great if someone could translate this (@chengxicn ?). Very small and easy!

[EryouHao]

@tunetheweb Hi, has the translation program for 2022 started yet? I'm interested in translating the simplified Chinese