localize and internationalize

[mikelmaron]

For localization / internationalization -- this is definitely possible. Starting point would be to create a directory with the two letter code for the language, copy all the content files and directory structure from the main page of the site there, and then translate. There's a little bit of work to enable switching language, but won't be hard after.

We should probably wait for the content to settle a bit, before going into translations though.

[althio]

What is the exact plan, the roadmap here?

1. initial content in English
2. opening to OSMF members for feedback
3. new content in English
4. localize and internationalize (how?)
5. opening to OSM community for translations
6. on-hold for translations (how long?)
7. official/public announcement

Starting point would be to create a directory with the two letter code for the language, copy all the content files and directory structure from the main page of the site there, and then translate.

You mean translators would contribute by git/Github?

[woodpeck]

In my opinion, localization and internationalization should be an optional extra and not hold back the main, English-language site.

Don't forget, the "welcome mat" is not a general presentation of OSM to the public, it is aimed at organisations approaching OSM from various angles. Every single case in the past where I thought "I wish we already had the welcome mat" was a case where the organisation in question was using English to communicate. The larger and more influential the organisation, the more important it is they know how OSM works - but the more likely it is that they can digest English documents, too.

So, I'd say the roadmap is publish the English document after incorporating feedback, have it mature for a while, and then encourage community members to contribute translations, and make a translation public once the relevant community is happy with it.

Let's also be mindful of the fact that local chapters might have similar documents of their own; if, say, a good OSM primer for organisations already existed on openstreetmap.fr, there would be not reason for them to fall in line behind the Welcome Mat, they could just continue using what they have.

I fact, I would very much like to limit the centrally-published Welcome Mat to a small number of languages widely used in OSM, and discourage translations that we cannot realistically keep up to date.

[mikelmaron]

Would love to have translations asap, but will move forward with what we have now too.

We're planning to announce more widely on the blog this week, gather more feedback through SotM. Following that, need to put on a more permanent url (welcome.osmfoundation.org perhaps), and then from appropriate places on osm.org and osmf.org

[althio]

@woodpeck In my opinion, localization and internationalization should be an optional extra and not hold back the main, English-language site.

That is the recipe for not doing any localization and internationalization. Language diversity is important for a worldwide project. OSMF should aim to support all people, all organisations, in all possible countries, all possible languages. In my opinion OSMF should be concerned about translations of all its contents.

Every single case in the past where I thought "I wish we already had the welcome mat" was a case where the organisation in question was using English to communicate.

Since OSMF is only in English, people are using English. Most likely if they can't use English, they don't read you, they don't contact you. To me, that just sounds like massive selection bias. My experience is very different. I have several cases where people would rather not use English.

The larger and more influential the organisation, the more important it is they know how OSM works - but the more likely it is that they can digest English documents, too.

This is not helping the local communities and the small-to-medium companies, and even big companies in their regional markets. This is effectively a great barrier for OSM activities in areas where the predominant language is either: Arabic, Bengali, Chinese, French, Hindi, Japanese, Malay, Portuguese, Punjabi, Russian, Spanish...

Let's also be mindful of the fact that local chapters might have similar documents of their own; if, say, a good OSM primer for organisations already existed on openstreetmap.fr, there would be not reason for them to fall in line behind the Welcome Mat, they could just continue using what they have.

They could, just give them a choice. Anyway, openstreetmap.fr is for France, there are other countries using French but little English: maybe they would prefer the "official" OSMF Welcome Mat with community translations rather than whatever exists in France.

I fact, I would very much like to limit the centrally-published Welcome Mat to a small number of languages widely used in OSM, and discourage translations that we cannot realistically keep up to date.

That is maybe practical from your point of view but I don't see how you select a small number of languages or why you expect translations to go out of date.

More importantly, how do you expect to develop OSM if you keep it to languages already widely used in OSM? To me, that is a serious case of vicious circle.

To conclude, I would just give my wishes:

• start localization as soon as possible
• start enabling community translations and make them as easy as possible
• start thinking how to translate as many languages as possible (looking for outside help, pro bono or paying)

I think this is in line with the OSMF objectives of "support, enable, help" the project and its communities "but not control".

Maybe this is not the right place to discuss. If you want me to move the discussion to osmf-talk, let me know.

[mikelmaron]

@althio you're right, this level of discussion about localization in OSMF generally is beyond scope of the ticket. @woodpeck has his opinions, but it's not the official stance of OSMF or this particular project.

What I can say -- we want to internationalize and localize the welcome mat. What can you do to help implement that right now?

[kamicut]

We should probably wait for the content to settle a bit, before going into translations though.

@mikelmaron I'm interested in localizing for a language, do we think the content is settled?

[mikelmaron]

@kamicut yes we're stable. One thing we need to bring in is internationalization. Do you want to take a look at how it was done in https://github.com/mapbox/mapping/tree/mb-pages (which was the starting point for this site) and see about adding internationalization, and the localize?

[Andygol]

I'd like to introduce a reworked Welcome Mat featuring internationalization support and a day/night mode, all built using Material for MkDocs.

You can check out the project here: https://github.com/Andygol/welcome-mat-osmf

Please feel free to explore and utilize it for your needs.

PS Additionally, you can integrate Transifex to facilitate translations into various languages and ensure a global reach.