[haiku] Re: Supporting web content in non-English languages

  • From: Niels Reedijk <niels.reedijk@xxxxxxxxx>
  • To: haiku@xxxxxxxxxxxxx
  • Date: Fri, 13 Nov 2009 14:18:55 +0100

Hi,

2009/11/13 Jorge G. Mare <koki@xxxxxxxxxxxxx>:
> Now that translation teams for various languages have been gradually
> forming around the Haiku User Guide translation project, I thought this
> could be a good time to also start thinking about providing non-English
> content on the Haiku website.
>
> The idea is to make at least basic information about the project, Haiku
> and the community more accessible to non-English speakers (initial focus
> could be on the About and Community sections). For reliability purposes,
> we could rely on the language managers from the translation teams that
> have been forming around the Haiku User Guide translation project.

I have three issues with people translating the main website.

1. Content changes will cause less-maintained languages to get
outdated. I find it very discouraging when a web page is partly
English and partly another language.

2. It would probably lead to a mixing of languages, not between pages
and hyperlinks, but also for example a localized header of the 'Latest
Articles' box and the English titles within it.

3. Much of the content is intermixed and not relevant. Let's be
honest, you need to have an adequate command of the English language
to participate. Having the mailing list descriptions translated to
another language is useless. (So this is an issue with selecting the
translatable pages).


I would rather suggest coming up with an alternative plan, something
which I proposed before, about creating a http://start.haiku-os.org/
[working title].

It would be a website catered at first-time users, to give them an
entrance into the Haiku project (somewhat like the Mozilla website,
which is a localized product website, instead of the community
website). The updating of this website could be done periodically
(with milestones) so that it is possible to judge the status of
translations. Finally, this website could be localized and the
translators can put local resources (and perhaps even news items) on
it - though I think this could rather be left to specialized localized
community websites.

Within this proposal there is the assumption that we as project do not
have to host things like local forums, or mailing lists, that is up to
3rd party community websites.

N>

Other related posts: