Closed 0xeb closed 4 months ago
Let me propose this workflow:
Like this, we both get commit credits (open source spirit), and also, it will be faster since you know the language.
We are dealing with 15k comments and it is more efficient if you directly start editing instead of commenting.
How does that sound?
I should probably start by reviewing and closing the existing pull requests. This is a manual translation, using GPT-4 combined with DeepL. Unfortunately, I am not able to focus on this this week and next week, because I need to finish work for Fine.
1)
Manual GPT-4 is not going to be sustainable, not for anyone and not in any reasonable amount of time. I think it is fast to start off with the stuff I did, and just review / edit on the fly. It should take you (as a native speaker) no more than 10 minutes per file and we have around 170. So that's reasonable.
2) What is DeepL?
3) Please edit this PR at least per the workflow I suggested. They are 3 tiny files.
I need to start focusing on Unicode/UTF-16 support.
Note the first and last lines in this screenshot. I can quickly write a script to update the translation based on the original text's first word if upper case or not. I will update that through and generate new translation files for new files (not these 3 files).
Please @janrysavy , let's get this moving fast.