Synereo in Spanish, French and Mandarin

[lapin7]

I think we have to go multi-lingual. What architecture of the site makes this possible?

[eeik]

HJ,

Localization is a non-trivial addition to a website and requires a good deal of work under the covers to make the text string swap outs smoothly within the same code-base. The quickest approach might be to simply have a sub-folder within the site structure under each localized language we support. Starting with "Spanish" would look something like --> http://www.synereo.com/es/ ... or, sub-domain approach for same effect --> http://es.synereo.com/.

I don't actually know however how (or if) this might be supported on the GitHub hosting and it will definitely require some monkeying.

Either way, the translation itself is one part and a vital one, but the implementation may be a bit tricky.

How many translators do you have in your orbit and what languages are you looking to immediately target? There should be a solid reason why we go this route so soon given the state of the product development itself since if we localize the marketing page, there may be an assumption that we localize the social network product in the same timeframe which I can assure you will not be the case at the moment.

Eric

On Tue, Mar 1, 2016 at 11:44 PM, HJ Hilbolling notifications@github.com wrote:

I think we have to go multi-lingual. What architecture of the site makes this possible?

— Reply to this email directly or view it on GitHub https://github.com/synereo/blog.synereo.com/issues/12.

[lapin7]

It started with @bhokor joining Slack. He is translating messages from English into Spanish in order to post them into ESP bitcointalk groups. Then he started translating some pages of the Web Site.

The reason is to get Spanish speaking people on board. I agree that it is an impulsive action. Not very well thought off as we don't have a real product to show. I know that creating a lot of noise without having things in order is very dangerous and probably doomed to fail. Managing expectations is therefore crucial. Maybe a successful approach is to say that the people are going to build their own network. But then again we have a huge organisational problem.

I'm currently looking for a French translator and a Mandarin translator.

Let's discuss this on the HOA today. Maybe it's wise to put translation on a low priority and to focus on a first version of the product.

HJ

[CMsynereo]

@Bhokor suggested that the Spanish summary of http://blog.synereo.com/2016/03/24/Synereo-Update/ should go under http://es.blog.synereo.com Every time the principal blog were updated we could upload the Spanish version translated to the es.blog

Is this a good idea???

[CMsynereo]

ES for Spanish DE for German FR for French CN for Mandarin ID for Indonesian KR for Korea

[CMsynereo]

When we make the blog mulitlingual it's probably best to add a dropdown menu at the heading of the blog. Like this the main site stays untouched right now and only the blog will have a different language option.

[bhok]

I support CMsynereo´s idea, all integrated in the main blog with a dropdown menu and you can choose the flag of your language

[delawwer]

I agree =)

[MalthusJohn]

sounds good - whatever works the easiest

[CMsynereo]

@bhokor We're still interested in the translation of the blog.synereo.com but we first have to decide about the structure. For example: es.blog.synereo.com de.blog.synereo.com id.blog.synereo.com We have to talk that over with @drbloom and @dor I don't know how to publish that with https://github.com/synereo/blog.synereo.com It probably needs a directory structure under _posts and _drafts like _posts/es/ _drafts/es/ Discussion has also moved under https://github.com/synereo/blog.synereo.com/issues/12

[bhok]

i dont know about which would be the better structure, but probably would be nice to talk with the web creator about what he think is the better option

[ian-bloom]

I have a few ideas about hosting translations without making many changes to the original sites. Lets bring together the available Synereo members who know some GitHub and Jekyll to discuss the options.

[delawwer]

tell us when you want =)

[Meladon]

(troisel77) i have no github skills but am willing to learn, also i started to translate the website (currently with exception of the blog entries) and the ann from bitcointalk. About the structure: i edit directly into the html file of the website, whereas the blog entries are located in seperated files (*.md), which can be easily edited. If i don't should do the task - stop me ;) best regards.

[ian-bloom]

Multilanguage: Anybody can clone this repo and do some testing :) There is an official Jekyll Plugin for Multi-Language here: https://github.com/vwochnik/jekyll-language-plugin And another Jekyll example without using a plugin: https://github.com/sylvaindurand/sylvaindurand.org

Play around and see how hard or easy it may be to enable for this blog. Before making a big effort, report back here or in #multilingual (https://synereonet.slack.com/messages/multilingual/). There is no bounty for this work (yet). Let's see what Synereo thinks it is worth?

[jcmelati]

I can make it portuguese. (PT-br)