I believe:
- translating the ide is indeed useful. I was asked for that in a course
once, to do just that is a start.
- to have one start guide translated would be useful (I believe there was
one already, but the link I had is down, maybe it is in the homepage).
- translating core classes and ugens, but is true that: 'We currently have
no way of providing localized versions of documentation - that's a big-ish
engineering task in itself... without that, there's really no use in
translating documentation in the first place.'
- It can be made automatically, I can help to check the result too.
- later, different countries call some basic things, some times, very
different, I don't know what would be the "international" mode, so, it
would be good to be more than one person from one country.
How is it in other languages? how is it with the Japanese translation for
example?
> Would it be helpful to integrate google translate to the docs somehow, to
improve usability of untranslated things - or would the translations
simply be too bad?
1st try:
Comete errores groseros a veces -> I make rude mistakes sometimes -
(...really?)
2nd try:
Comete errores groseros, a veces -> He makes rude mistakes, sometimes
(better but a comma doesn't changes the sentence's pronoun).
3th try, the other way around:
Does rude mistakes sometimes -> Comete errores groseros a veces
4rd try:
Comete errores groseros a veces -> Make rude mistakes sometimes -
(translation changed after I checked the previous sentence, that's cheating)
I don't trust him :-) (now I don't know how to write that) The Android
version seems to be better I don't know why.
However: Let's just internationalise the IDE and we can just check it
after. I'll send another email in a moment with another idea.
2018-04-02 16:23 GMT-03:00 <scott-y6qSm6YX8/[email protected]>:
> And, actually, not to sound negative: I think addition support for
> localized documentation WOULDN'T be super hard - even the most minimal
> support would be enough to allow people to start submitting translations,
> which I imagine would be very very valuable. That's work that those of us
> who can't contribute translations could still help out with.
>
> - S
>
> On Mon, Apr 2, 2018 at 12:19 PM Scott Carver <scott-y6qSm6YX8/[email protected]> wrote:
>
>> I might be useful to have some of SC's spanish language users build a
>> rough prioritized list of improvements to SC's localization. Translating
>> the IDE UI seems straightforwardly useful - but spanish language
>> documentation is a *very* large and open-ended task. Breaking this into
>> smaller tasks would make it much easier for people to contribute, and make
>> sure their contributions are hitting the most important things first. For
>> example, is it better to spend time translating guides, or documentation of
>> important core classes? Is it important to translate all the help
>> navigation terminology to spanish (e.g. "Search", "Browse", "Classes"), or
>> better to simply spend that time on class docs themselves? Would it be
>> helpful to integrate google translate to the docs somehow, to improve
>> usability of untranslated things - or would the translations simply be too
>> bad? We currently have no way of providing localized versions of
>> documentation - that's a big-ish engineering task in itself... without
>> that, there's really no use in translating documentation in the first place.
>>
>> And, fwiw, I believe the microsoft translation database Brian mentioned
>> are actual human-generated translations of common terminology like "File"
>> or whatever.
>>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.