Nice work!

Perhaps we should tell them this to make sure we have one single place where everyone can see ongoing translations :

Don't forget to open an issue on github if you start working on a language, so that others can review your ongoing work and help improving it :
https://github.com/bitcoin/bitcoin.org/issues?page=1&state=open

Ho, we are already on TV, through a old IE8 browser filmed with a cheap cell camera : http://www.youtube.com/watch?v=aaOsM3RUNG8&feature=youtu.be&t=1m

But hey, here is a big incentive on improving the main page!!

Because this pull request is.. 4 days old.

I asked on this pull request why the PGP key was removed in the first place. I think it's a good question to answer before everything.

There is no "one master". Any change that is controversial or non-trivial must get at least one ACK from developers. Sometime more depending on the importance of the change.

Just like most of open-source project that use git, you can "fork" the repository (which basically means create your own copy of our code), improve it, and later ask to merge your changes into our code by pressing the "pull request" button. Of course, you need to learn a bit how git works. But if you are not afraid of command lines, that is overall pretty easy to learn.

Also before doing a pull request, it might be good to ask for feedback and provide screenshots to see what people think of it, perhaps on this topic :
https://bitcointalk.org/index.php?topic=148712.0

Awesome

That is why I suggest people to show their work y opening an issue, or update existing issues so that people can work in team on their own branches. Not duplicating efforts.

But if that happens, people can simply compare their work, select one branch and include what they think is better from the other branch. Or we can ask contributors which branch to merge, and later get another pull request from the owner of branch #2 that would contains only improvements.

I'm new to the community. My fullname is Saïvann Carignan. I'm also a recent member of the foundation. And I am the one who did the multilanguage version of weusecoins and the new bitcoin.org website with the help and feedback from the community and developers. I am a french Canadian.

Sure. That sounds great.

However, I didn't find a way to make this approach concretely work with something with as much long texts like a website, without being problematic in some cases. A single language file is usually used for small dialogs in unified application with "english" fallback. I don't think that makes sense in our case to work this way because each translation must be "structure independant".

- English version might have pages other sections don't have (news, version history).
- We might need special styles or content adaptation for some languages.
- We should be able to create new pages, and translate them later without this page appearing in english in all translated version. This would give a very poor user experience.
- Outdated translation should not prevents us to update other languages.

There are also a few things that might work poorly with this approach or just be impossible / very hard to do with jekyll, like translating filenames (urls) and keeping links between translated pages, and generating a structured sitemap with alternate hreflang as we do now.

But if someone comes up with something better that is both easier for translator while being still functionnal for integration and collaboration, feel free to work on it and make a pull request so that it can be discussed!

And just the general idea to have at least some good popular bitcoin websites in each language can help it to develop in as much jurisdiction as possible. This is also a very important form of decentralization. Both legal and economic decentralization.

Spanish translation for bitcoin.org is ongoing there if you want to help : https://github.com/ernestova/bitcoin.org

I think that weusecoins and bitcoin.org are now ready to call for translations.

Here is the thread : https://bitcointalk.org/index.php?topic=159129.0

I think that weusecoins and bitcoin.org are now ready to call for translations.

Here is the thread : https://bitcointalk.org/index.php?topic=159129.0

There has been serious work done to make both bitcoin.org and weusecoins translatable. This previous goal is now a reality!

It is now time to go with phase 2, both websites are ready to be translated in as much languages as you can.

You can find the instructions and the guidelines in the README of both website github repositories :

https://github.com/weusecoins/weusecoins
https://github.com/bitcoin/bitcoin.org

Please provide high quality translations
The meaning of many texts is sensitive. Providing accurate and clear translations is very important. As much as possible, and especially for bitcoin.org, it is highly recommended that each translation is reviewed by other native speakers for your languages.

Working in team
Working in team always lead to the best possible results. If you are working on a translation, you can show your ongoing work by opening an issue on the github repository so that you can receive feedback and help. And so that we don't uselessly duplicate efforts and end up with two seperate translations.

If you don't understand command line, git or HTML
You can very well translate human-readable texts in each file and ask for someone else to integrate your work and make a pull request for you. Don't hesitate to ask help of others on this thread.

Proposing changes in the meaning for bitcoin.org
If you feel some texts require improvements on bitcoin.org, please prepare a good replacement for the original english version and create a seperate pull request so that your changes can be discussed. This way, each translation will keep up-to-date with each other, based on a text that gets the best consensus.

Keeping translations up-to-date
The history of all changes in the english files can be easily seen on github.

Building a translation team?
If enough people participate to this project, perhaps could we create a bitcoin-translator group? Our mission being to make bitcoin accessible everywhere on this planet.

Sounds awesome to me so far!

I have the previous mailing list email, as it's one of the rare things I didn't keep because I intended to ask what to do about it. So if it's actually used, we can put it back and it would be very appropriate.

I think that we should think twice before removing the "Enthusiasts" page because it's pretty unique, in the sense that this is the only page that really focuses on the ground-breaking world changing nature of Bitcoin. Other ones are more "use-related". But that doesn't mean it cannot be merged with medias, that depends on what it actually looks in the end. Space is not an issue, as we have enough space to add it as a seperate link if needed.

I will see if I can contribute some ideas others than the actual list (which is pretty good). At the very least, I can help integrating this in the website.

Just.. awesome!

This indeed looks good. But in practise, I fear this will end up being harder to work with as bitcoin.org is not a unified webapp, but a website with changing and extensive texts. I wouldn't want a out-of-date translated version to half show english content. And using variables when the files are already almost pure easy-to-translate texts sounds more complicate to me (and might be a nightmare to build with jekyll at a first glance), while giving us less flexibility to adapt the website for specific language needs.

I think I can provide something that will be easy enough to work with for anyone, while being technically efficient.

I will definitively work on most of these points in the next days.

I will give instructions soon. A few technical improvements are still required from my side, and it should not take long.

We can't control Bitcoin growth, and we shouldn't. We can however avoid contributing to potential failures, and help preventing them.
Which means, giving as much accurate informations to the user and help sustainable economies to develop.