Open MaxHillebrand opened 1 year ago
This is the start of a big project as it will set the direction for the localization efforts of the software itself. Would it be reasonable to have a person responsible for localizations for the whole project eventually and that this person does an analysis of different kind of approaches before doing anything? Like traditional hiring of translators, crowdsourcing translations, using online translator APIs, building our own custom translations with GPT-4 and whatnot.
For all webpages (main website, docs & blog), it should be fairly easy if we decide to use Google Translate API. This would have the same translations as if you enter a URL in google translate. AFAICT these translations are near perfect.
For the website, the UX would look something like this:
Screencast from 10-08-2023 12:07:55.webm
Possibility to translate into 104 languages.
Google doesn't offer this for free. They have several plans, the basic plan would be sufficient for us (HTML text translation).
The price is per character sent to the API, I think we would fall in the category of 500,000 to 1 billion characters per month, which is billed as $20 per million characters.
Some browsers already offer instantaneous translations (I read Chrome can do this?), I suspect that behavior like this will continue to be more widespread, so eventually working on this might be obsolete (not sure what time frame though).
Not sure about FOSS options, I'd have to check.
Don't be dependent on someone else's API, but this will require a lot more effort (manual translations?)
Thanks, do we store the translated text in github? Or is this done "on the fly" every time a user clicks it?
Or is this done "on the fly" every time a user clicks it?
This
AFAICT these translations are near perfect.
Did fast check for Latvian, and it's clearly not. And I looked at it only for few seconds. Same could be for other smaller languages.
"Open-source, non-custodial Bitcoin Wallet for desktop" is translated as "Atvērtā koda, ar brīvības atņemšanu nesaistīts Bitcoin maks darbvirsmai". Google translates "non-custodial" to "ar brīvības atņemšanu nesaistīts", but that phrase in Latvian is used as "ar brīvības atņemšanu nesaistīts drošības līdzeklis" which translates to "a non-custodial measure of security", which is term used during criminal cases (it means, they don't put you in the jail during investigation, instead there is home arrest or you are forbidden to leave country, etc). :)
In Hungarian it's acceptable. There are strange things, but better than nothing? A close call though 😄 @CAnorbo ?
This is a bit strange:
This one is pretty good:
This is almost perfect:
LoL Terrible Hungarian translation. 😅
LoL Terrible Hungarian translation. 😅
Is it at least something funny?
My favourite is "nem örizetbe vett" 🤣🤣
"nulla tudású szoftver" is a pretty dope expression though. I'm going to start using it now :D
My favourite is "nem örizetbe vett" 🤣🤣
This means "not arrested" and the "nulla tudású szoftver" means that this software knows nothing, like no functionality.
Another alternative is to add a thin band on top of the website that says "This website was auto-translated by an AI robot slave to Hungarian. Click here to switch to English..." and then wait a decade until the technology catches up. AI auto-translation is clearly the future and we don't want to get stuck in a cave with rocks and stones.
Btw, I think this too techical content is not even translatable to our Alien language properly.
Tried Tilde MT, which is local product, kinda best for Latvian, Lithuanian and Estonian languages. It translates "Open-source, non-custodial Bitcoin Wallet for desktop" to "Atvērtā koda Bitcoin seifs galddatoram, kas nav piemērots apcietināšanai", which means "Open source Bitcoin safe for desktop computer, that is not suited for arrest". :)
This is the start of a big project as it will set the direction for the localization efforts of the software itself. Would it be reasonable to have a person responsible for localizations for the whole project eventually and that this person does an analysis of different kind of approaches before doing anything?
I completely agree with this. And do not forget to figure out the customer support side as well.
AFAICT these translations are near perfect.
https://github.com/zkSNACKs/WasabiWalletWebSite/assets/93143998/53a96059-7974-4170-ad50-ac7b0a8ed797
at least for Dutch it's pretty good :D
FWIW, the Google translate API doesn't work for onion service
English is not enough, the website should be readable in all languages.
After we figure out an automated process for this website, do the same with the documentation and the software.