public inbox for [email protected]  
help / color / mirror / Atom feed
From: Michael Glaesemann <[email protected]>
To: [email protected]
Subject: Re: Considerations on a Multi-Lingual Site
Date: Tue, 11 Nov 2003 10:20:16 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On Tuesday, November 11, 2003, at 08:03 AM, Andreas Grabmüller wrote:
> It's difficult to create elements like lists without knowing HTML.

Couldn't it be done along the lines of building selects? Say you've got 
an array of list items:

$list_array = array ('apples','oranges','grapes');

$list_string =  '<ul>';
foreach $list_array as $this_item {
	$list_string .=  '<li>'.$this_item.'</li>';
}
$list_string .= '</ul>';

This doesn't solve the problem of how you get the list into the 
database, but that shouldn't be too hard.

>  I think we have two options here: a bbcode parser that allows some 
> input like the popular bulletin boards do or using a WYSIWYG editor

A bbcode parser would probably be adequate. Wiki markup isn't too hard 
and parsers are easy to come by.

> If a translator creates a page in its own language, should it be not 
> available to other languages or appear in that foreign language for 
> the english people? Should they be able to change the menu (just for 
> their own language or for all)?

I could see a link with something like "Translate this item" if a 
translation isn't available in the preferred language of the viewer. 
That then brings them to the bbcode page (requiring whatever 
authentication you want, if you want to limit the translations to be 
done only be authorized translators).

As for what news is displayed, I think it might be a good idea to 
display all of the items, with as many translated as translations are 
available. For languages that haven't got a full version of everything 
translated, you might get some pretty sparse pages, and people wouldn't 
necessarily know what they're missing.

It might be nice if you could store a language preference order in the 
cookie. So for example, if I wanted English first, then German, then 
Japanese, I'd get the translation of the highest preference that was 
available.

This may have already been hashed out. I haven't looked closely enough 
at that section of the code yet.

Michael





view thread (13+ 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: Considerations on a Multi-Lingual Site
  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