Translate content to Japanese #586
Comments
|
@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! |
|
@tunetheweb , Thank you. I have a question. |
|
@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! |
|
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). |
|
@tunetheweb , Thank you proposal. I check three translated chapters. Next, I will discuss to @MSakamaki whether rules should be created like the French team. |
|
Hello @ksakae1216 ! As for the translation rules for Japanese, I am currently working on the following rules: Nayori of foreign words Japanese proofreading (automation recommended, I useing Tool) 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. |
|
Hi @MSakamaki Thanks advice. I see. |
|
@ksakae1216 Your settings can be made as shown in the following link. Do you have any opinions? |
|
No problem. I try add vscode plugin. |
|
I have a question. "Figure 4." of the following document has no png file. Is it OK? |
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":
Hope that makes sense but let us know if you've any other questions! |
|
@tunetheweb |
|
@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: You just need to translate all the parts between the |
|
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. |
|
@tunetheweb I have a question I found Is ../2019/compression#identifying-compression-opportunities? |
|
Good spot! Too much copying and pasting from the previous years chapter last year 😁 Could you change this link in the 2020 text to this instead?: There isn't a heading near it in 2020 so let's link to the figure directly instead. |
|
Thanks your response. |
|
@tunetheweb I want to help for me.
|
|
You did a fetch and merge. So your Notice this:
So yes you are not behind - but you're actually ahead now! Try not to make any changes to your To be honest I force reset my In fact I even have a couple of helpful aliases I've created to make this easier: So my workflow when I want to work on new work, is:
I can reset my |
|
@tunetheweb Thanks, I understanded well for your careful explanation. |
|
Hey @ksakae1216 are you planning on translating the 2021 foreword and the 2021 Methodology (a lot of this is similar to 2020)? If so that would allow us to print a copy of 2021 edition in Japanese and send you a copy. Also we have some 2022 chapters available if interested? |
|
Hi @tunetheweb |
These are the core templates - without which we cannot release any translated chapters. They are in the language specific templates directory:
2022
2021
2020
2019
These are the chapters to be translated, and they exist in the content directory:
2022
2021
2020
@hi-toshi@ksakae12162019
Additionally the following pages need translated too in the language specific templates directory:
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:
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
The text was updated successfully, but these errors were encountered: