However there are still many mistranslations (e.g. “Good” → “良い”) because I translated them using AI tools etc., so I don’t think there is much need to link from the official Anki manual yet. (In short, these are more like a personal blog than official manuals for now.)
If you are interested in the translation, you can easily report issues to me anonymously via Google Forms. (No problem to report to this thread, but this thread will auto close in about a month if there are no replies.)
AnkiManual is already a bit old because I forked it half a year ago. (Otherwise it is new)
The translation does not match the actual wording used in Anki. (I think I’ll make a glossary later.)
English images are not translated into Japanese.
Some of the links are incorrect.
It may be better to use custom IDs for markdowns.
Existing translations :
These are not my translations but translations of already existing Anki manuals. The “Anki日本語マニュアルWiki (jp-Anki-Manual-Wiki)” is out of date but the translations are very accurate so I will refer to it later.
The existing “Anki日本語マニュアルWiki (jp-Anki-Manual-Wiki)” can be updated without Github, so if native Japanese edit the Wiki it is better suited than my translations.
However there are these problems :
This wiki is updated only about once a year.
Foreign Anki users learning Japanese are blocked.
It still uses Anki 2.0 info and images so it needs a big correction.
The page is difficult to read compared to markdown.
So it would be more reasonable to add to this if there are few corrections, but there are no volunteers so it is easier and more updatable for me to completely recreate it.
I think it should be possible to provide the AI model with the list of glossary for a page to get more accurate translations. Although, eventually it’ll need to be manually corrected by people.
Apart from the ones you mentioned, I’ve been also told by @snowtimeglass that the wikis are owned by the company. If later we were to reuse these elsewhere (tooltips) you could need permission from wikiwiki.jp owners.
It will be wasted effort, and I’d rather hope any person willing to contribute is directed to your repo instead. If we can get the essential pages done (deck options/getting started/studying/troubleshooting/etc.), after that it can be linked from the main manual.
The existing manual translation is significantly out of date at this point, and at this point I wonder whether we’d be better off with an AI-generated alternative. A glossary provided to the AI may well address some of the wording issues, if it won’t break the budget regenerating it again. We could also add an “(AI generated)” warning to the listing.
I guess it would be desirable for these pages and files to be eventually on the official site. I imagine a repository like “ankitects/anki-docs-ja”. Administrator or authorized person could merge PRs in it, as in ankidroid/ankidriddocs
Is it possible and supposed to be fulfiled in the future?
I’m thinking if we can have AI translated versions of Manual in other languages too. There’s the Portuguese manual which is only barely translated. Perhaps, for a person not proficient in English, an AI translated version might be better than the English one.
It’s also easier for a person to edit a AI translated Manual than to start everything from scratch.
In my opinion there is no need for that, e.g., WikiWiki has anime wikis and images and texts are used, it is clear that WikiWiki does not have the copyright to them, so perhaps the English version of the Anki manual or the translator has the copyright.
Thank you!
In my opinion it is appropriate to update WikiWiki.jp at Anki Japanese Manual Wiki. Japanese general users cannot edit GitHub, Github does not have a Japanese version, and the most common purpose for Japanese to use Anki is to learn English, so they cannot read or query English, and even if they are native English speakers very few users report on Github.
WikiWiki is already widely used by Japanese, which means that native Japanese speakers who are not developers or translators can edit it, so I plan to eventually update WikiWiki.jp.
I can only translate Japanese manuals, the AI translation I said does not mean batch processing. The AI causes hallucinations, breaks markdown code, and improperly omits sentences, all of which are simply manual checks and corrections, the current manual contains mistranslations because I do not know the terminology, e.g., “Leech” translates to “無駄なカード” in Japanese, but I do not know if that is the latest Leech translation (I use the English UI), so I have left it as “Leech”.
But volunteers didn’t keep that page updated there. In the long run, it is only a few highly interested people who will make most of the contributions. Does wikiwiki.jp increases the chances of getting highly interested volunteers?
For the English version, we didn’t have a issue tracker until recently and most PRs came from dae, cqg and Rumo. It wasn’t a problem that not a lot of people contributed. Only a few are needed. I don’t believe throwing many people at a problem is always good.
I also think wikiwiki.jp doesn’t make a very good impression with all it’s ads, etc. and your website will have a much better experience.
Do you mind telling us what you used and how? It will be useful to know.
I don’t know about that, but the manual is open source so I think there is no problem with duplication, e.g.
WikiWiki → for native Japanese speakers
ankitects/anki-docs-ja → for programmers and foreign residents
My manuals → I edit and customize freely
This benefit is that it is easy to make big changes and custmize, e.g. I planning to change all the markdown links in bulk, the official Anki manual markdown probably doesn’t support it, and if it’s not convenient I would like to restore it.
I use VS Code Insiders (source code editor) and Github Copilot Chat (paid, $10/month), basically it is almost the same as manually sending the English text to ChatGPT for translation.
Roughly like this:
Translation:
Prepare the markdown text.
VS Code sends English text to Copilot.
Translate the English text with prompts.
Replace the English text with the translated text.
Read and check the English text and the translated Japanese text.
Others:
Fix any problems in the code (E.g. avoid ``` because Copilot can’t translate it.)
Check markdown links using VS code extension.
Use shortcut keys to simplify frequently used tasks.
Use multi-button mouse to simplify commonly used tasks.
Update URLs to connect to other translation manuals.
Notes:
I think the recommended code editor for Anki development is PyCharm, VS Code may not be used much.
Copilot Chat is not superior for translation, I used it for add-on development so I just used it, the advantage is that it can be used inside the code editor and the reply is a bit faster.
I guess the permission is needed. Those anime images and its texts are maybe legitimate citations and their copyrights are owned by the original creators, but the rights of the anime wiki’s main texts probably belong to WIKIWIKI and each volunteer writer.
Article 8.1 of the Terms of Use
All intellectual property rights related to our website and the Service belong to us or to the licensors who have licensed them to us, and the permission to use the Service under these Terms of Use does not mean a license to use the intellectual property rights of us or the licensors who have licensed them to us related to our website or the Service.
In my understanding, WIKIWIKI is automatically granted licenses (to use volunteers’ writings) from each volunteer writer, whereas each volunteer writer is not granted license to use the content (e.g. Anki manual’s text) outside WIKIWKI. The content can’t be reused freely. So, WIKIWIKI might not very useful for the purpose here.
I agree. It could give the impression of being unofficial and less reliable.
Supportive and Helpful: すごいですね！(Sugoi desu ne!) This is great! I’d love to help with reporting issues or testing the translations. Let me know how I can contribute.
Thank you!
I have not yet created any guidelines for translation or a repository for collaboration, so if you find any strange translations feel free to contact me and I will correct them.
I have updated the “Getting Started” and corrected some terms.
