How translation works on Muhamor

<h2>Why a community site needs translation</h2> <p>Most questions people ask online have already been answered somewhere, just in another language. A cyclist in Leipzig and a cyclist in Valencia fix the same chain the same way. When every community is split by language, each side solves the same problem alone. On Muhamor a <a href="/en/c/" rel="nofollow ugc noopener">community</a> is about a topic, not about a language.</p> <h2>What gets translated</h2> <p>The title of a publication, its text and the comments under it. The interface itself is in English and Russian; the content can be written in any of 31 languages. You choose your reading language once, and the feed shows titles in that language.</p> <h2>Where the original is</h2> <p>Every translated text has a small note that it was translated, with a link to the original. Machine translation is good but not perfect, so the original is never hidden. If a translation is wrong, you can report it from the same note.</p> <h2>How to write so that translation works well</h2> <p>Short sentences translate better than long ones. Name things directly instead of using local slang, and put numbers and units next to each other. You do not need to write in English to be understood: write the way you would explain it to a friend.</p> <h2>Where to start</h2> <p>Open the <a href="/en/help/" rel="nofollow ugc noopener">help centre</a> for the reading-language setting, or <a href="/en/explore/" rel="nofollow ugc noopener">explore</a> what people are discussing right now.</p>