Translate content into Korean

[tunetheweb]

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

• base.html -
• base_chapter.html -
• error.html -
• search.html -
• add language to src/server/language.py -

2025

• base.html -
• base.html - foreword
• contributors.html -
• index.html -
• table_of_contents.html -
• enable language in src/config/2025.json -

2024

• base.html -
• contributors.html -
• index.html -
• table_of_contents.html -
• enable language in src/config/2024.json -

2022

• base.html -
• contributors.html -
• index.html -
• table_of_contents.html -
• enable language in src/config/2022.json -

2021

• base.html -
• contributors.html -
• index.html -
• table_of_contents.html -
• enable language in src/config/2021.json -

2020

• base.html -
• contributors.html -
• index.html -
• table_of_contents.html -
• enable language in src/config/2020.json -

2019

• base.html -
• contributors.html -
• index.html -
• table_of_contents.html -
• enable language in src/config/2019.json -

These are the chapters to be translated. They exist in the content directory:

2025

• fonts -
• webassembly -
• third-parties -
• generative-ai -
• seo -
• accessibility -
• performance -
• privacy -
• security -
• capabilties -
• pwa -
• cms -
• ecommerce -
• page-weight -
• cdn -
• cookies -

2024

• javascript -
• markup -
• structured-data -
• fonts -
• media -
• third-parties -
• seo -
• accessibility -
• performance -
• privacy -
• security -
• cms -
• ecommerce -
• jamstack -
• sustainability -
• page-weight -
• cdn -
• http -
• cookies -

2022

• css -
• javascript -
• markup -
• structured-data -
• fonts -
• media -
• webassembly -
• third-parties -
• interoperability -
• seo -
• accessibility -
• performance -
• privacy -
• security -
• mobile-web -
• capabilities -
• pwa -
• 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 -
• seo -
• markup -
• accessibility -
• cms -
• performance -
• security -
• jamstack -
• fonts -
• mobile-web -
• pwa -
• http2 -
• capabilities -
• third-parties -
• page-weight -
• caching -
• resource-hints -
• privacy -
• compression -
• ecommerce -
• media -

2019

• javascript -
• css -
• seo -
• performance -
• http2 -
• markup -
• third-parties -
• fonts -
• accessibility -
• pwa -
• cms -
• security -
• media -
• mobile-web -
• cdn -
• 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:

• accessibility_statement.html -
• base_ebook.html -
• 2025/methodology.html -
• 2024/methodology.html -
• 2022/methodology.html -
• 2021/methodology.html -
• 2020/methodology.html -
• 2019/methodology.html -

There is no need to translate the chapters HTML pages are they are generated off the markdown combined with the above templates.

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

---

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 Korean-specific extras by editing this comment.

Korean specific extra advice:

[tunetheweb]

You really need these to be able to run the site in a new language so suggest you start with them first:

• base.html
• base_chapter.html
• index.html
• table_of_contents.html

They are also a lot easier to translate than the chapters themselves as a lot shorter!

then up to you whether you finish out all the templates or tackle a chapter.

[tunetheweb]

You'll also need to add Korean to here:

almanac.httparchive.org/src/language.py

Lines 28 to 33 in bc835a8

	# Currently we are only supporting languages and not regions
	class Language(object):
	JA = _Language('日本語', 'ja', 'JP')
	EN = _Language('English', 'en', 'US')
	ES = _Language('Español', 'es', 'ES')
	FR = _Language('Français', 'fr', 'FR')

and the language code (ko?) to here (but let's not commit this second one until we have at least the main templates and a chapter or two done because committing it here means it would be put live on next release):

almanac.httparchive.org/src/config/2019.json

Line 5 in bc835a8

"supported_languages": ["en","es","fr","ja"],

And while when you submit your first PR, add yourself to the contributors section of the config under your GitHub id, which means you'll show up in the 2019 Contributors page:

almanac.httparchive.org/src/config/2019.json

Lines 181 to 189 in bc835a8

	"contributors": {
	"kleinab": {
	"name": "Abigail Klein",
	"teams": [
	"authors"
	],
	"avatar_url": "https:\/\/avatars2.githubusercontent.com\/u\/1319324?v=4&s=200",
	"github": "kleinab"
	},

[rviscomi]

@techhtml 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 you translate this text for the tweet?

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

Thanks for your help!

[goleedev]

@rviscomi If you still need some help, here is the translation! 🙂

EN: Do you speak Korean? Help us translate the Web Almanac as part of our effort to make it globally accessible to the web community!
KO: 한국어를 할 줄 아시나요? 그렇다면 웹 커뮤니티를 전 세계에서 액세스할 수 있도록 Web Almanac의 번역을 도와 주세요!

[rviscomi]

Thanks @goleedev! I've just tweeted it here: https://twitter.com/HTTPArchive/status/1293965549588877314

[taechonkim]

Hi, is this issue valid now? if so, I want to contribute it! how can I contribute?

[tunetheweb]

Hey @taechonkim would love to have your help. Unfortunately we've not made much progress on this so far.

I've just sent you an invite to the team. After you accept that, you should be able to edit the first comment and put your name besides some of the files to translate to let others know you're working on that one.

Please do them in the order listed (so start base.html and finish with methodology.html). Then just fork the repo, copy the English file to a ko folder and translate it! Then submit a PR with that.

We've a Translator's Guide and also a Git Guide that are worth a read before you start!

Let me know if you have any questions.

[taechonkim]

Hey @tunetheweb I have a question.
I have forked the original repository, cloned forked repository to local, and made branch for my translation job.
I think my next job is copying src/templates/en to src/templates/ko, starting translation with base.html. is it right?

[tunetheweb]

Correct. Only copy across the templates as you translate them so you don't commit any English version ones into src/templates/ko. You can decide how many translated files to include in each pull request. base.html is quite big so maybe do one PR for that, for example. Another example the 2019 and 2020 contributor pages are obviously very similar so can submit both in the same PR. Can also do all the templates at once if you want, but smaller PRs are easier to review and merge so recommend that!

[taechonkim]

Hey @tunetheweb Thank you for quick reply.
I translating base.html now, there are details about contributors bottom part of base.html (about 114 line, starting with details of kleinnab...)
I wonder where these details comes with in Web Almanac.
And is there need to translate them?