-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spanish version #17
Comments
This sounds like a great idea, however my only concern is something like this http://kotaku.com/5880007/racial-epithet-shows-up-on-minecraft-menu-developer-apologizes?tag=minecraft |
I understand, and I can assure you, as native spanish, that I'll take care that everything sounds right and is politically correct. A way to do this, as this project uses HTML directly without PHP/Ruby/Python/Node or something in the backend, is create a folder for every translation (Main: simplecpu.com, spanish: simplecpu.com/es, etc...), those folders would be clones of the english version but with resources in his respective language, and after, release only the translations that we are sure that are correct and safe, labeled with stable or something like that. The translations versions labeled as "safe", can be in a url like simplecpu.com/beta/... with "unstable" releases, with a link to the Issues section in this repository to report wrong translations. |
Ok, this sounds like a good system. |
There are a few methods: Automatically in the backend: When the server receives a request, there are some ways to get the user's default language. I think the best way is combine the third method (manually in the frontend) with this: <html lang="es" dir="ltr"> In each page, specify the "lang" attribute with the language code, this will help Google to give to the user the page with the right language (anyway Google can get it using the Google Translator's algorythm to recognize languages) |
This is a cool project. I can translate this to Chinese. |
The 'es' directory with all the relevant files has been added, feel free to fork it and translate. |
If there are po files I might be able to translate this to Bulgarian(will be cool) |
I've been translating LearnGitBranching, and Peter found a way to auto-translate the site. Surely you can get inspired by that. I'll try to translate this project to Spanish soon :) |
That's awesome, thanks @mgarciaisaia |
Maybe tonight I finish it :) @r0nk, do you know how you'll deploy this? I'm currently testing this by symlinking |
Fixes r0nk#17 I decided not to translate the cpu.js file so it's not _that_ difficult to maintain. There are a few words which could have been translated ('address', 'value'), but I think it's not worth it.
What I'm going to do next with the translation I haven't figured out yet. Ways to deploy is is something I'm going to research soon (currently I'm recovering from my first attempts to tinker with the linux kernel, so I have to re-setup everything.) The patch and general interest is awesome though, so as soon as everythings not on fire I should be able to craft a good system for this. |
Hey, great. Not for this weekend, but I'll see if I am able to understand how LGB works I'll probably never do that, really - my attention span sucks - but I'd If any time in the future I get inspired and do anything better, I'll let What I'm going to do next with the translation I haven't figured out yet. — |
I could translate this to spanish, this is a so useful resource that would help some spanish students a lot when they start to learn the basics of computer science.
The text was updated successfully, but these errors were encountered: