public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Maier <[email protected]>
To: PostgreSQL www <[email protected]>
Subject: Re: PostgreSQL website translations
Date: Mon, 10 Mar 2008 10:39:19 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Sun, Mar 9, 2008 at 9:48 AM, Guillaume Lelarge
<[email protected]> wrote:
> Adrian Maier a écrit :
>  > [...]
>
> > So:  should I spend time with bringing my Romanian translation
> > of the website up-to-date ?    or there is too little interest  ?
>
>  Despite the lack of answer, I think there is interest in translating the
>  website. But there's a few things to do before adding the translation. I
>  need to remember what Magnus told me about this last november :) ( ...
>  if I remember well, I had to find some way to figure out if pages are
>  out of date and if possible show the english page if the translated page
>  is out of date ... something like this but Magnus will correct me if I'm
>  wrong). Oh, and the pictures need to be "translatable" too.

Sure: currently it's extremely painful to keep track of the
modifications.  And the last time this was discussed i've
understood that  for the time being the translators can
only rely on cvs and the pgwww-commits mailing list
because there were no resources for creating something
more elaborate ( especially because there were no
translations available ).

Another thing that will need serious thinking is, IMHO, the
mechanism used for selecting the language.  I personally
hate when a website decides the language based on
something unintuitive and transparent like the default
language in the browser or the IP location.    I mean:  it's
much better to have a set of small flags or a combobox
so that the user can easily select the desired language
instead of digging into web browser 's configuration.



-- 
Adrian Maier

view thread (30+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected]
  Subject: Re: PostgreSQL website translations
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox