[haiku-doc] Use of multiple languages on this list (was: [German] User Guide - Übersetzungs Richtlinien)
- From: "Jorge G. Mare" <koki@xxxxxxxxxxxxx>
- To: haiku-doc@xxxxxxxxxxxxx
- Date: Mon, 12 Oct 2009 07:37:29 -0700
Hallo,
On Sun, 2009-10-11 at 23:09 -0700, Humdinger wrote:
> -- Jorge G. Mare, on Sun, 11 Oct 2009 12:41:47 -0700:
> > I don't think anybody wants their mailboxes flooded with messages in
> > all
> > these languages that they don't understand.
>
> The topics are so distinguishable that the mails are easily dismissed/
> deleted without even opening them.
>
> > So would it be possible to have discussions in languages other than
> > English elsewhere? Perhaps each language can have a mailing list for
> > localization/translation purposes?
>
> Separated mailing lists are no solution. For German, for example, I'd
> be alone there... It's supposed to offer the possibility to comment for
> someone who doesn't have the time or motivation to join the actual
> translating, but does have some valid input.
>
> Besides that I don't expect huge traffic on this topic, we could try
> this: When some of the other languages post their first draft of their
> style guide, comment on it privately. Then after a while, post the next
> draft/end version.
Well, I am not sure what languages and/or discussions will be
considered to be acceptable on this list, but if the discussions that I
have seen to be common in localization projects ensue and are multiplied
by the potential number of languages/locales, then we could be up for a
mess. A separate list would keep focus instead.
Additionally, I don't see really how a multilingual list named
[haiku-doc] can be any better than language-specific lists from the POV
of following the process of and commenting on localization; actually, I
think it could be the contrary: anyone with a thread of interest in the
localization of Haiku into their language is more likely to subscribe
to, say, [haiku-de-l10n] or simply [haiku-de-translate] than to a list
described as the place for "Discussion for the API documentation," and
naturally so.
IMNSHO. :)
Regards,
Jorge/aka Koki
Other related posts:
