Additional languages for website

[ricco386]

We will support EN and SK fir the website, however it would be nice to have also additional languages on the website.

This issue is long-term and not for just one person. It is call for help to make the PyCon SK 2018 better.

If you do not have any experience and want to start contributing to open source project this is the easiest way how to do so. Just follow the guide in README.rst or add your translations to any file in subirectory:

https://github.com/pyconsk/2018.pycon.sk/tree/master/translations

Currently we have pre-generated DE directory apart from SK (that is translated from EN), but if you would like to submit in any other language (HU, CZ, etc.) please just write a comment in this issue.

We will show all participating people at our website, so join us and help us make conference even better this year.

[jangondol]

In general, I do like the idea of introducing PyConSk to new audiences who may not be familiar with the languages we speak. That said, I am wondering if introducing new languages is the best way to achieve this. If this was a one-off task, I would be all for it. It seems, however, that this is something we may need to maintain over time, so there appears to be this "hidden cost". Also, we should make sure that the translation quality is nearly "perfect", so that the site looks professional. Also, when we update any given page, all the other language versions need to be updated as well or the website will "fall apart" and language versions will be "desynchronized".

Since the conference itself is in English and Slovak (languages we already support), I wonder how much added value translating the site brings... In my opinion that value is not huge but maybe I am just underestimating this?

Two thoughts:

1. Would it make sense to only offer a brief, nearly-static SUMMARY page in more languages (as opposed to translating multiple pages)? We could just mention the basic info like the following: what PyConSK is, when and where it takes place, explain that the conference is in SK/EN languages (and so is the website), and we could point to the other pages on the English website (tickets, venue,...). Also, we could include country-specific instructions (e.g. travel instructions from the Czech Republic and the links to the Czech Python community + PyConCZ, travel from Poland and links to Polish Python community / PyConPL, and so on). It seems it would be much easier to maintain this over time.

2. Would it help if (instead of translating everything manually) we would simply include links to Google Translate for the pages that have not been manually translated? I know that the result would not be perfect but at least we would avoid work of having to maintain the translated pages over time.

Of course, 1) and 2) could be combined.

What do you think?

[ricco386]

Default language is set to English. So if there is something not translated English text will be shown. This is default behaviour of Flask app. If we change a text during translation render old text is commented a nd there is new empty translation string generated (eg. new sentence is not translated). Therefore I dont think it would be a huge issue if lets say in German version of site would be part in English. We can also leave a note there about this behaviour. This way website will never "fall apart" and language versions won`t be "desynchronized". Besides we have a note there: This is community managed website, contribute at our GitHub, therefore if a German speaking person have a problem with it he can contribute.

Hidden idea apart from introducing to new audience is to motivate to contribute, and this might be a way ;) I would like to think that people would consider the conference thirs if they contribute, even as little as translate one sentence. Besides it is easy way to contirbute ot oss and started to getting to know the Flask.

Well if we are going to use Google Translate, rather than providing links I would generate the texts and just leave a note that the translations have been auto-generated and how they can be updated by human (again contribution on GitHub).

Summary pages might works, but again there is "hidden cost" in maintanance (and honestly I think it might be larger that if we left English/German page). "hidden cost" of translations really depends from page to page. For example Code of Conduct page hasn't change since 2015 we have introduce it. I will try go one by one...

Currently we have pages:

• Index - Only a sentence or two at the moment. How ever this page will most likely change most often. Minor announcements, news etc.
• COC - Not likely to change
• Sponsoring - Not likely to change (on the other hand, with introducing new audience not much of additional value)
• Venue - About Bratislava, we provide probably only minor changes if any. We will add new subsection about venue once we know more.

Future pages:

• CFP - Once written, not likely to change
• Tickets - Once written, not likely to change
• Speakers - Speakers will provide bio in one language (we might require in English), but this doesnt change
• Talks - Abstracts will be provided in one language (we might require in English), but this doesnt change
• Schedule - Most of the text is just Speakers and Talks and minor texts like day names, times, room names etc. Reordering of schedule might happen regularly but this does not affect translations.
• Sponsors - About them text will be provided in one language (we might require in English), but this doesnt change

[pawel-lewtak]

I could start with Polish translation and hopefuly someone will join and help on the way. What to you think?