28/09/2012 14:54, sgrìobh Rob Weir:
Another way of looking at language demands is to look at visitors to
our website and what language preference they set in their browsers.
This information is sent to our servers and Google Analytics gives us
a summary of what locales our website visitors are using.
Caveat: OO supports (smaller) locales for which there are no localized
browsers and, for quite a few (smaller) locales, the choice of browser
language may not map directly to the choice of UI for OO. For example
there's Tibetan OO but I don't think there's many browsers which support
Tibetan at the moment. As for the accept-language settings, most users
aren't even aware of those so I don't think they're reliable. But for
bigger languages, yes, it should work.
But one question: does anyone have an estimate for how much time is
required, if a translation is 95%, 97% or 98% done? Any rough
estimates that we can give? Words/hour? Something that we can use to
help volunteers know how large (or small) this effort is?
Hard one. On average, a professional translator should manage
2,000-5,000 words a day, depending on the content. Given the lack of
experience of many volunteers and, for many locales, the lack of
agreed/standardised terminology, and/or proofing tools I think we're
definitely looking at the lower end of the spectrum. I think
guesstimating it as "full days of translation" is the closes meaningful
measure we can offer.
Michael
