On Wed, Nov 23, 2011 at 12:54 PM, krastanov.ste...@gmail.com <krastanov.ste...@gmail.com> wrote: > About translating the wikipedia pages: I agree on adding tasks for that. We > should just check if there is any sandboxing mechanism that can be used - It > won't be great to have wrong translations online.
Do you think it's necessary? What's the Wikipedia standard for this I wonder. If so, we could require that they write the page in a subpage of their user page, and then move it to the official page when they are done. For example, say I wanted to translate it to Spanish. Then I would write it at http://es.wikipedia.org/wiki/Usuario:Asmeurer/SymPy, and then when I am done and it is reviewed, I would move it to http://es.wikipedia.org/wiki/SymPy (this is just to demonstrate what I am saying, I don't speak Spanish). I think it's actually pretty typical for people to write drafts of pages on subpages of their userpage before moving it to the main page. The userpage subpages are basically personal sandboxes where you can write (almost) anything. Aaron Meurer > > On 23 November 2011 20:08, Aaron Meurer <asmeu...@gmail.com> wrote: >> >> 2011/11/23 Ondřej Čertík <ondrej.cer...@gmail.com>: >> > On Tue, Nov 22, 2011 at 11:37 PM, Aaron Meurer <asmeu...@gmail.com> >> > wrote: >> >> On Wed, Nov 23, 2011 at 12:12 AM, Joachim Durchholz <j...@durchholz.org> >> >> wrote: >> >>> Am 23.11.2011 08:01, schrieb Ondřej Čertík: >> >>>> >> >>>> On Tue, Nov 22, 2011 at 4:47 PM, Aaron Meurer<asmeu...@gmail.com> >> >>>> wrote: >> >>>> At the Google Mentor Summit we were specifically told, that it needs >> >>>> to be a human translation and that students will try to use automated >> >>>> services for it, so that's why a native speaker needs to check this. >> >>> >> >>> Ah, right, I recall that part. >> >>> >> >>> Professional translators use automated tools and rework the >> >>> translation >> >>> afterwards. That means the tool does 80% of the work and the >> >>> translator does >> >>> the other 80% - spotting mistranslations and cleaning up the style is >> >>> essentially a full rewrite after all. >> >>> So I would ask people to start with Google Translate or whatever suits >> >>> them, >> >>> then read both the original and the automatted translation, and then >> >>> rewrite >> >>> the page *in their own words", as if they were writing the page from >> >>> scratch >> >>> in the target language. >> >>> >> >>> Not sure whether that will cause problems with the Google folks >> >>> though. I >> >>> don't know how pushy they are around their rules. >> >>> >> >>> Regards, >> >>> Jo >> >>> >> >> >> >> Remember two things. First, this is a contest, with a big reward for >> >> the person who completes the most tasks, and also money for everyone >> >> who completes tasks (I think it's $100 for each three tasks, up to >> >> $500). Second, remember that these are mid- to high-school students. >> >> Many of them will see a translation task and think that it will be >> >> easy points, because they can just run it through Google translate, >> >> and it will be "good enough". This is why the translation has to be >> >> "perfect" to be accepted. This is a little different from the code >> >> tasks, where we can let some small insignificant things like code >> >> quality slip through, with the understanding that they are new to >> >> coding. >> >> >> >> As to how they do this, I would leave it up to them to figure out. If >> >> they can run it through Google translate as an initial step, and still >> >> make the translation very good, then that's fine. But I don't think >> >> it's a good idea to suggest it. >> > >> > At least for Czech, I would *not* recommend to use google translate at >> > all, because >> > it gives a bad structure of the sentences, and its very hard to make it >> > right. >> > >> > And rather than having a bad translation I think it's better to have >> > no translation, because everybody can simply put it to google >> > translate to get the idea what the page says, but the official >> > translation (in my opinion) should be a good one, so that people can >> > read it and don't get driven away by mistakes in it, or bad style. >> > >> >> >> >> Frankly, I wouldn't have any translation tasks if Google didn't >> >> require it (though that's partly just because this is the one kind of >> >> task that's impossible for me to review :-). >> > >> > I was surprised too at first, it didn't occur to me that we >> > could/should translate anything in sympy, but now I must say that >> > actually I like it. >> > >> > I think it's a great idea to translate some parts, like the tutorial. >> > It allows to get involved with people who would otherwise not get >> > involved, and also to target people that otherwise would not be >> > targeted. I think there are a lot of people who really prefer to read >> > things in Czech (let's say in my case) rather than English. >> > >> > Ondrej >> >> I see what you mean. To degree do you think people who do not speak >> English at all will use it if only the tutorial is translated (i.e., >> the rest of the documentation is not)? We would have to have tons of >> volunteers to translate *everything* and keep it translated, and even >> then, names in the code are in English, and Python is in English. >> >> By the way, I was thinking. One of our tasks is to improve the >> Wikipedia article (http://en.wikipedia.org/wiki/Sympy). Someone is >> working on it right now, actually (or supposedly is). What do people >> think about adding adding translation tasks to translate that for the >> next round of tasks. So far, it is only in Spanish and Japanese (see >> the "Languages" on the left), and those will become out of date once >> the English version is improved. This is definitely something that I >> think should be translated into all languages. >> >> Aaron Meurer >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sympy" group. >> To post to this group, send email to sympy@googlegroups.com. >> To unsubscribe from this group, send email to >> sympy+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/sympy?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To post to this group, send email to sympy@googlegroups.com. > To unsubscribe from this group, send email to > sympy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com. To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
