Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Translate Japanese, Spanish, and Russian #38
If anyone would like to sign up to review/assist translations for any of the three languages, let me know.
Renaming this issue to unblock the launch on translation. I think it's an overly optimistic target, given that most of the content is still unfinished. It'd be a lot to ask our @HTTPArchive/translators to finish translating 20 chapters plus the methodology/home/chapter/outline pages in a matter of weeks. Does this sound ok?
I cloned the latest repository and tried to verify the
Then, the past verification project disappeared and 500 error occurred during registration.
If the problem persists, you may need a pull request based translation .
Other chapters are changing slightly as we approach launch day on Monday. After that we should be in a more stable place to start translating other content.
One worry I have is that after launch with so many eyes on the chapters, people will point out typos we missed, so the content would actually be churning frequently, making it hard for translation to keep up. Generally, we do need a process for ensuring that every content change propagates to all of the translations.
I'm sorry, I was proceeding with the integration of gitlocalize, but I understood that it can only be integrated by the repository owner.
Can @rviscomi do gitlocalize integration?
I also start pull request translation.
@HTTPArchive/translators I've been thinking about how we can effectively translate the content and keep it in sync with all of the other web dev and editing work that's happening simultaneously.
Most of the editing is done, per #218. There are still a few chapters that are in flux. My goal is to wrap that up this week.
There is still a lot of development work being done. My worry is that it will become a nightmare to keep
I think the highest priority is to translate the contents of the chapters. Rather than blocking the launch of a new language on the entire website being translated, let's roll out chapter-specific translations as they're completed. We'll need a chapter-specific widget to toggle between languages.
And now that we're already launched, I'd say that all languages are equally important. I don't think we should limit ourselves to "P0 languages" like Japanese, Spanish, and Russian. If translators have the bandwidth to work on Italian, let's roll that out when ready.
Even though the chapter contents are mostly finalized, there will still be occasional issues discovered and fixed. We'll need a process for marking that as requiring a new translation. I'll think about this, but open to ideas.
How does all this sound?
I'll think we that there is something to gain from the others translation project I have seen.
In my experience, a successful translation is a clone of the repository.
Even if html is included, it seems to absorb changes.
I also feel the possibility of cloning the repository from a long-term perspective, but I like to see only the changes as it is because the project has the basics of translation.
I am working on this. By taking the git hash and comparing the differences as follows, I can extract only the differences that have changed since translation. (This idea was received from https://github.com/nrwl/nx).
// Japanese git diff `git log --pretty=format:"%h" -1 --no-patch ./src/content/ja/2019/markup.md` `git rev-parse HEAD` ./src/content/en/2019/markup.md // Spanish git diff `git log --pretty=format:"%h" -1 --no-patch ./src/content/es/2019/markup.md` `git rev-parse HEAD` ./src/content/en/2019/markup.md
Note: This idea is just a hash difference of the file from the previous time, so it is necessary to complete the translation of one file every time.
This content is so wonderful that I would like many people to read it.