Translate wiki into Russian

[execut4ble]

I’m from Lithuania (1337huania), they teach us Russian in schools.

[EnterGin]

@˙executλble

I’m from Lithuania (1337huania), they teach us Russian in schools.

CIS countries.

[EnterGin]

@D4rw1N

I’m not very good with wiki stuff so I can’t help with the technicalities, but on my end I’m cool with you translating it, as long as someone is willing to actively tell me and/or Jared (Centaur1um) if the translation is well written with good grammar and not adding stuff that wasn’t in the original article. YaLTeR, would you be up for that?

We’re very keen on keeping everything SourceRuns related at a high standard. So naturally we need someone we know to read through all the translations and tell us if it’s good or not, and since we don’t know Russian… Yeah, you get it.

And like YaLTeR said, absolutely NO Russian on the forums. Everyone should be able to understand everyone. I do not want to see you guys using Russian in your posts again (unless it’s asking for help with certain words you’re not sure how to translate for example).

To summarize, I’ll check with Jared on this once he gets on and then either him or me will give you a heads up in this thread if you’re good to go or not.

So, what solution?

[Cameron_D]

If I find the time tomorrow I’ll set up the plugin needed to support the multiple languages.

[EnterGin]

@Cameron:D

If I find the time tomorrow I’ll set up the plugin needed to support the multiple languages.

Good news!

[Arianon]

Well, now that we’re entering the multi-language wave - perhaps I could help with a spanish translation too?

:>

[moozooh]

@YaLTeR

@˙executλble

Thing is, people will watch our speedruns and will see that we refer to this glitch as ABH, so they’ll have no idea what the Russian URZ thing means. It’s very unlikely that they’ll find anything by searching for URZ too.

Well, that’s why I’m for keeping the acronyms. “АБХ” is how I say ABH in my russian chats and, well, my mind when I’m thinking about it.

^ This is the correct way of thinking. See also: UNESCO, IUPAC, laser (would have become something like “успви” if it were translated), etc; they’re transliterated in Russian, not translated. In my line of work, which is writing and translating all sorts of technical text (from information pamphlets to instruction manuals), there are various guidelines that we typically adhere to:
— never invent a new term for something there is an existing one for;
— when writing for a specific audience, prefer terms used and understood by that audience;
— make full use of morphology;
— when transliterating, make good judgement on new spelling, else fall back on a precedent case.

There are also more generic translation guidelines, which I assume you’re well aware of, but just in case:
— Russian and English are fundamentally different, and should never be approached the same way;
— break the original text up into points and translate those points rather than particular words or sentences;
— if something is worded poorly in the original text, fix it in the translation;
— make full use of Russian vocabulary, syntax, punctuation, and morphology—you don’t have to be limited by the original language’s constraints.

I suppose I could help with some translations/wording as well; shoot me a message if you need something tidied up.

[Zezima242]

Dont think we need to translate all trick names completely thorough (aka Google translate). Trick names should stay on english (so russian players will find necessary articles easier) and then, all explanations and “how to” should be translated into russian. If needed, i can help with translation, comrads.

[EnterGin]

@Zezima242

Dont think we need to translate all trick names completely thorough (aka Google translate). Trick names should stay on english (so russian players will find necessary articles easier) and then, all explanations and “how to” should be translated into russian. If needed, i can help with translation, comrads.

If we do not translate the explanations and “how to”, then we will have nothing to translate.

[YaLTeR]

@Zezima242

Trick names should stay on english (so russian players will find necessary articles easier)

I’d do it that way for the beginning: “ABH (Accelerated Back Hopping) - АБХ (Ускоренная распрыжка задом) - это …”

[execut4ble]

^

[EnterGin]

@YaLTeR

@Zezima242

Trick names should stay on english (so russian players will find necessary articles easier)

I’d do it that way for the beginning: “ABH (Accelerated Back Hopping) - АБХ (Ускоренная распрыжка задом) - это …”

I thought we already discussed this theme.

[EnterGin]

@Cameron:D

If I find the time tomorrow I’ll set up the plugin needed to support the multiple languages.

So…

[EnterGin]

@Cameron:D

If I find the time tomorrow I’ll set up the plugin needed to support the multiple languages.

So. You leave me?

Admin edit: Please don’t double (triple in this case) post in the forums, just edit your last post.

[moozooh]

Pretty sure you can start already anyway? I mean you don’t have to have a write access to begin translating at all, do you.

[EnterGin]

@moozooh

Pretty sure you can start already anyway? I mean you don’t have to have a write access to begin translating at all, do you.

I translate articles and put text in Microsoft Word. But it is inconvenient. Also I do not know whether they will agree in the end.

[Cameron_D]

Hi guys, sorry for the lack of updates on this.

Currently there is no real plugin that will function in a way that will suit the site (They are all either out of date or designed for very large/complex wikis, like Wikipedia) so I’ve started developing my own extension to do it.

If you guys want to get a head start on translating pages just pick any page and add “/ru” on to the end of the URL. (i.e. http://wiki.sourceruns.org/wiki/Accelerated_Back_Hopping/ru ).

Also regarding the discussion about language-specific names, what are people’s thoughts on making things like “АБХ” redirect to “ABH/ru”. I’m not sure, just a thought I had.

[YaLTeR]

Yeah, and discuss translation related stuff in /ru pages’ “discussion”-s (or talks), they can be accessed by going into the page and pressing the “discussion” button at the top, near the “edit” and other buttons.