public inbox for [email protected]  

help / color / mirror / Atom feed

From: Robert Treat <[email protected]>
To: [email protected]
Cc: Magnus Hagander <[email protected]>
Subject: Re: Multi-language to be or not to be
Date: Sun, 11 Feb 2007 11:45:15 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On Sunday 11 February 2007 08:22, Magnus Hagander wrote:
> I'm working on a rewrite and major cleanup of parts of the code that
> runs the main website, and came across a thought.
>
> We currently have support for translation of news, events, surveys,
> quotes and pages. So far, we have zero news, zero events, zero surveys,
> zero quotes and zero pages translated.
>
> The only translated pages are the press information ones, and I don't
> count them because we don't actually use the translation infrastructure
> for them - we link specifically to each and every page.
>
> All the other translations live on completely separate sites - I think
> because they only translate parts of the information and also provide a
> lot of native information in that language.
>
> I know adding translation capabilities was one of the big requirements
> for the last rewrite. But I'd still like to bring up the question -
> should we bother keeping it, or just get rid of it? We thought we had a
> need then, but do we still have it?
>
> Getting rid of it will significantly simplify some code, and it will
> make the static mirrors about half the size they are now (we currently
> mirror every page both in English and in language-neutral (which means
> English again)).
>

See recent post on advocacy from italian community asking about providing 
translation capabilities.  We need to talk to them and see if we have 
something that they want to use; if we don't then I have no objections to 
removing it (though fwiw I don't find it a terrible burden as it currently 
stands)

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

view thread (52+ 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], [email protected]
  Subject: Re: Multi-language to be or not to be
  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