If you think something is missing or should be added to this list, contact Michał
Being a SUMO locale leader is a fun and rewarding task. You help coordinate with your community the work around SUMO, motivate contributors, review articles, onboard new localizers and help contributors grow. You don't have to do all of this - just translating and reviewing is already great - but building a healthy and fun community around you will help you get the work done faster and will bring you the joy of collaboration and perhaps new friends.
So, what do you need to know?
The most important bit of information is: please sign up to our global Locale Leaders mailing list here! :-)
If you started your locale at SUMO, you have technically been a Locale Leader with your very first contribution. Not everyone is interested in being a Locale Leader from the start, though - this page should help you decide whether you can (and want to) become one.
Above all, being a Locale Leader is a great exercise in organization, leadership, and communication.
As a Locale Leader, you are encouraged to keep localizing and contributing new revisions to the KB. This way, you will learn from your own work and the work of others.
As a Locale Leader, you will have a chance to:
It's important that you know how your locale is doing. Your best friend in finding out quickly is the dashboard, where you see the localization coverage, the articles needing translation and review. You can find your dashboard from the "contributors tools" menu on the top, or you can visit our list of locales.
From the Dashboard you can find some very useful links on the left side:
You should also use the Community Hub to get a quick insight into the situation in your locale. It allows you to filter by date, product, and activity levels - and to send PMs to multiple users at once - all from the same place.
Take a look at the milestones listed here for all locales. They are listed in an order you can easily follow to localize SUMO for those who speak your language.
If you "hit a milestone", you can update the list in the spreadsheet with a smiley. Don't forget to contact Michał about it, too - thanks!
If you have questions about the priorities for your locale, please contact Michał.
A style guide is a set of standards for the writing and design of documents, either for general use or for a specific publication, organization, or field. A style guide establishes and enforces to improve communication. To do that, it ensures and enforces best practice in usage and in language composition, visual composition, orthography, and typography. (wikipedia) (example/template)
A SUMO style guide is a document that gathers all linguistic standards for a SUMO locale, created and accepted by the Locale Leaders and Reviewers. It is a set of guidelines and tips for all localizers - new and experienced - in the context of the type of content that SUMO presents in its many available locales.
A style guide is the document that everyone using a locale should refer to. It is the golden standard of localization for the locale.
It is possible that your locale already has a style guide created by localizers who worked in your language before you.
It is also possible that you will be involved in creating a style guide from scratch! It is not a trivial task, but it helps everyone who starts to localize the project after it is created. Creating a style guide is a responsibility of the Locale Leaders and Reviewers.
Locale Leaders and Reviewers should cooperate online to make the style guide as broad and definitive as possible. It is a good idea to take an existing style guide (for example from a different project) and base your own style guide on it.
Languages are processes, rather than mathematical constants - so, a style guide should be open for reviews and updates by the community using it, if necessary.
A style guide should be written in the target (native) locale, so that all localizers can understand what it contains, even if they are not experts in the source (English) locale.
What should a style guide include? Some of the categories of information included in a style guide should be:
The most popular types of text that are to be localized following the rules of this style guide. SUMO texts are generally divided into two broad categories:
An explanation of the terms and concepts present in the source and their counterparts in target locales; may include a list of ‘false friends’ (= terms that you think mean one thing, but actually mean another). SUMO terminology is mostly based on the terms gathered in the Transvision tool.
An explanation of how code in the text looks like and what should (and should not) be done with it. For example, at SUMO this will include options for displaying different content to different platform configurations (also known as the for tags).
All the tricky vocabulary shortcuts we love to use in IT. IYKWIM ;-)
Which words are Capitalized. Some terms could even be ALL CAPS!
Different locales use different formats for dates and numbers. For example 03/04/15 means a different thing to someone from USA, and someone from Spain
The way different parts of text are separated by empty spaces (for example: paragraphs, images, headings)
General rules about spelling, grammar, and punctuation in the locale. The basics everyone should know by heart, but that is better to have written down for reference.
Building a community is a great way to reach all your goals at SUMO and having a lot of fun while doing it. Some great friendships were born here, so you might end up having a lot of friends. Building a healthy community is an art that gets interpreted very differently by everyone. We'll give you some ideas and tools, you can use the ones that adapt the best to your style: