Almanac.httparchive.org: Translate content to Japanese

[bazzadp]

These are the chapters to be translated, and they exist in the content directory:

2020

• [ ] capabilities - @ksakae1216

2019

• [x] accessibility - @MSakamaki
• [x] caching - @ksakae1216
• [x] cdn - @ksakae1216
• [x] cms - @ksakae1216 (requires review)
• [x] compression - @ksakae1216 (requires review)
• [x] css - @ksakae1216 (requires review)
• [x] ecommerce - @ksakae1216 (requires review)
• [x] fonts - @ksakae1216 (requires review)
• [x] http2 - @ksakae1216 - #661
• [x] javascript - @ksakae1216 (requires review)
• [x] markup - @MSakamaki
• [x] media - @ksakae1216 (requires review)
• [x] mobile-web - @ksakae1216 (requires review)
• [x] page-weight- @ksakae1216 (requires review)
• [x] performance - @MSakamaki
• [x] pwa - @ksakae1216 (requires review)
• [x] resource-hints - @ksakae1216 (requires review)
• [x] security - @ksakae1216 (requires review)
• [x] seo - @MSakamaki
• [x] third-parties - @ksakae1216 (requires review)

Additionally the following pages need translated too in the language specific templates directory:

• [x] base.html - @ksakae1216 (requires review)
• [x] base_chapter.html - @ksakae1216 (requires review)
• [x] contributors.html - @ksakae1216 (requires review)
• [x] error.html
• [x] index.html - @ksakae1216 (requires review)
• [x] featured_chapters.html - @ksakae1216 (requires review)
• [x] methodology.html - @ksakae1216 (requires review)
• [x] table_of_contents.html - @ksakae1216 (requires review)
• [x] accessibility_statement.html - @ksakae1216 (requires review)

There is no need to translate the chapters HTML pages are 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 Japanese-specific extras by editing this comment.

Japanese specific extra advice:

• Nayori of foreign words
  https://www.jtca.org/standardization/katakana_guide_3_20171222.pdf
  https://www.bunka.go.jp/kokugo_nihongo/sisaku/joho/joho/kijun/naikaku/gairai/index.html
• English, katakana, hiragana, and kanji should be carefully selected throughout the content.
• Use these textlint settings: https://gist.github.com/MSakamaki/a3b7cbf57231b6287a19be28534cb50d

[bazzadp]

@ksakae1216 has expressed an interest in helping out.

@ksakae1216, for a start it would be great if you could review @MSakamaki 's work so far in https://github.com/HTTPArchive/almanac.httparchive.org/tree/master/src/content/ja/2019 and see if you spot any issues with the translations?

After that I've sent you an invite to the team and when you accept that, you should be able edit the first comment in this issue and put your name beside a chapter,

To do the translations, clone the repo, grab the markdown from the /src/templates/en/ folder and copy it to the /src/templates/ja/ folder and edit it, then submit a pull request with the translation and @MSakamaki can review for language and I (or someone else) will also review it from a non-language perspective and then we'll merge it into master.

Let me know if there are any questions!

[ksakae1216]

@bazzadp, Thank you.

I have a question.
What should I review first?
I looked at the link but didn't know what to review.

[bazzadp]

@ksakae1216 , ideally we'd have a second person reviewing all translations before we merge them to master. It's amazing what a second pair of eyes can spot. So anything you translate, @MSakamaki will review, and similarly anything he translates you can review. And if we get a third (or fourth!) Japanese translator then we can spread the load.

However when @MSakamaki translated those first three chapters (Markup, Performance and SEO), we didn't have a second Japanese translator so we just merged them without that review. We were hoping someone would join before we launched them so we could do that review - and now you're here! 😀

So it would be great if you could read those three translations now, and if you spot any issues then open a PR with suggested fixes. @MSakamaki can then review and he agrees approve the PR and we'll merge it in. If you're happy with the translations as they are and see no need for any changes then just add a comment to let us know.

One thing the French translation team did, that I really liked, was come up with a set of conventions for the French team to use. I copied those to the bottom of the first comment, but they are things like don't translation certain terms, which gender to use, and to use French versions of MDN documents whether they exist... etc. I don't know if those ones are exactly relevant to Japanese so feel free to discard them, but I'm sure there are similar conventions you and @MSakamaki should agree on. So as you read @MSakamaki 's translations I think it would be good to come up with some of these Japanese conventions too, so there's some consistency to the translations no matter who translated it. And actually documenting them in this issue will ensure these conventions are clear and help if another translator joins the team in future, or if someone queries any translations after go live.

Once you've read the three already translated chapters and have a sense of how to translate chapters, feel free to grab your own chapter by putting your name beside an unassigned chapter in the first comment and away you go!

Let me know if that all makes sense? However, these are all just suggestions. I've never done any translations and speak no Japanese, so you and @MSakamaki are the ones who can drive this issue through to completion - if you have better ways of working then go for it! Some of the translations teams are using one GitLocalise repo for all the translations, some have chat rooms (there's a Slack Channel for the Almanac - let me know if you can't access and need an invite), or you can message each other on Twitter or any other messaging platform, or just use this issue to comment back and forth. Up to you two!

[bazzadp]

Oh just realised I gave the wrong link! That's probably why you're confused. Try this one: https://github.com/HTTPArchive/almanac.httparchive.org/tree/master/src/content/ja/2019 (and edited above comment).

[ksakae1216]

@bazzadp , Thank you proposal.

I check three translated chapters.

Next, I will discuss to @MSakamaki whether rules should be created like the French team.

[MSakamaki]

Hello @ksakae1216 !

As for the translation rules for Japanese, I am currently working on the following rules:

Nayori of foreign words
https://www.jtca.org/standardization/katakana_guide_3_20171222.pdf
https://www.bunka.go.jp/kokugo_nihongo/sisaku/joho/joho/kijun/naikaku/gairai/index.html

Japanese proofreading (automation recommended, I useing Tool)
I am currently using 校正くん and moving to textlint.

There are other free OSSs, such as 校正くん and textlint and Redpen. If you have something you want to use, please let me know.

The other point is that English, katakana, hiragana, and kanji should be carefully selected throughout the content.

Feel free to talk about any other rules that might be needed.

[ksakae1216]

Hi @MSakamaki

Thanks advice.

I see.

[MSakamaki]

@ksakae1216
After translating accessibility, I tried to change Japanese proofreading to textlint.
Using this, I would like to match the sentences as much as possible.

Your settings can be made as shown in the following link.
https://gist.github.com/MSakamaki/a3b7cbf57231b6287a19be28534cb50d

Do you have any opinions?

[ksakae1216]

@MSakamaki

No problem.

I try add vscode plugin.

[ksakae1216]

@bazzadp

I have a question.

"Figure 4." of the following document has no png file. Is it OK?
https://github.com/HTTPArchive/almanac.httparchive.org/blob/master/src/content/en/2019/seo.md

[bazzadp]

"Figure 4." of the following document has no png file. Is it OK?
https://github.com/HTTPArchive/almanac.httparchive.org/blob/master/src/content/en/2019/seo.md

This is not really a figure but more highlighting of a particular state (often called a pull quote):

We have basically 4 types of "figures":

1. Tables of stats we have gathered, like Figure 11 in the SEO chapter. It could be argued these are "tables" rather than "figures" but we've called them "figures" in the Almanac when they are reporting stats we have gathered.
2. Graphics like Figure 1 in the SEO chapter. Stats. Note these have a PNG and also have data- attributes that allow us to create an interactive embed of the Google Sheets graph with a bit of JavaScript.
3. Pull quotes like you have noted in Figure 4 in the SEO chapter. It could be argued these are just quotes rather than figures, but we've decided to call them figures.
4. External images we have imported from other sources. Like Figure 2 in the Markup chapter.

Hope that makes sense but let us know if you've any other questions!

[ksakae1216]

@bazzadp
Thanks, Explanation figures.

[bazzadp]

@ksakae1216 , @MSakamaki would either of you have some time to look at the templates in src/templates/en/2019 and translate to src/templates/jp/2019?

We're looking to launch the chapters that are already translated in #671 but to do that, and let others benefit from your hard work so far, we need the core templates translated.

I've made this a good bit easier in #673 so the templates should mostly be lots of place holders like this:

{% block description %}The Web Almanac is an annual state of the web report combining the expertise of the web community with the data and trends of the HTTP Archive.{% endblock %}

You just need to translate all the parts between the {% block XXX %} and {% endblock %} and then the chapter generation script will automatically use these phrases as appropriate.

[bazzadp]

Btw it’s base.html and base_chapter.html that are most important to be able to release the chapters you’ve translated already. These are also quite short so should be easy to translate. The rest (the home page, the table of content pages... etc.) will take longer and can be added at a later time.

[ksakae1216]

@bazzadp , Sorry delay response.

I looked base.html and base_chapter.html.
Maybe don't need translate?

Is my understanding correct?

[bazzadp]

I cobbled together something and merged it. Would be good if you could review and translate text I couldn't?

[ksakae1216]

I intended to ask if I needed to do any of the following:

@ksakae1216 , @MSakamaki would either of you have some time to look at the templates in src/templates/en/2019 and translate to src/templates/jp/2019?

But you don't have to work because it's done, right?
https://github.com/HTTPArchive/almanac.httparchive.org/pull/690

[bazzadp]

Yes but I only partially did them in #690 .

If you look at the contents of those files they are mostly still English. But I did find a few Japanese translations from the other files so not 100% English but definitely not 100% Japanese either 😀So if you want to finish the translations of those files to also translate the phrases I didn't, then that would be good.

But think with #690 we have enough to launch if you don't have time for that right now.

[ksakae1216]

I see.
I will translate the untranslated files little by little.

[bazzadp]

@ksakae1216 I added you to the Contributors page in https://github.com/HTTPArchive/almanac.httparchive.org/commit/42c710325f4cf6568ad220b69dd4b0cc13d4bd3f. Hope that’s OK and feel free to submit a PR to correct or add any more details.

[bazzadp]

@ksakae1216 do you fancy tackling these three next in the templates directory?

• base.html - partially done to allow us to launch Japanese chapters
• base_chapter.html - partially done to allow us to launch Japanese chapters
• index.html - partially done to allow us to launch Japanese chapters

Think it would look better for our Japanese readers if the home page and all the core text was translated. Can then return to the remaining chapters after that?

[ksakae1216]

@bazzadp, Yes, I will translate 3 html file.

[bazzadp]

Thanks @ksakae1216 , just pushed the updated index and fonts chapters to live:
https://almanac.httparchive.org/ja/2019/
https://almanac.httparchive.org/ja/2019/fonts

Looks much better now the Japanese home page is actually in Japanese! 😀

[ksakae1216]

@bazzadp, @MSakamaki.
I translate resource-hints.

[bazzadp]

@bazzadp, @MSakamaki.
I translate resource-hints.

@ksakae1216 please be aware I made a small tweak to the Resource Hints chapter in https://github.com/HTTPArchive/almanac.httparchive.org/pull/731 to move some long code snippets to their own lines. Just merged there now so make sure you do same in your translation.

Barry

[ksakae1216]

@bazzadp, @MSakamaki.
I will translate media next.

[ksakae1216]

@bazzadp, @MSakamaki .

I will translate contributors.html, featured_chapters.html, methodology.html.

[ksakae1216]

@bazzadp.

if @MSakamaki finish to translate javascript, Do we finish?

[bazzadp]

Looks like! Excellent work.

However @MSakamaki hasn't been contributing in a while so not sure if he's making any progress on the JavaScript chapter. Maybe you could have a go and can compare if @MSakamaki does come back to the project?

[ksakae1216]

@bazzadp, @MSakamaki

OK, I will translate javascript chapter tomorrow.

[ksakae1216]

@bazzadp , We finished translate.
Thank you so much for reviewing it.

[bazzadp]

Thank YOU so much for all the hard work! Well done on being the first fully translated language!

The last chapter is now live: https://almanac.httparchive.org/ja/2019/javascript

Ideally we'll get @MSakamaki (or another Japanese speaker) to review your translations at some point but will close this ticket in the meantime. We can reopen if if we need to.

[bazzadp]

Reopening for 2020 chapters. Probably should be a separate issue but as Japanese is only language that made the finish line with all the 2019 content, I've added the 2020 chapters to their issues so it's easier to be consistent.

[ksakae1216]

I will start translate on sataday or sunday(11/28 or 11/29)

[ksakae1216]

@bazzadp I report to you about capabilities.md.

1. I found not enough 'js' 204, 232 row.
2. What is "pf" of "pf page loads" 290 row?

[rviscomi]

@ksakae1216 thanks for pointing those out! I've fixed those typos in #1591.