RE: Re: proposal for translated content projects

On Mon, 2003-11-17 at 12:35, Manfred Riem wrote:
> > Alternative to the parallel site structure would be to have 
> > an absolutely unrelated website with no interconnections. As 
> > far as Russian is concerned, I don't have enough time to 
> > maintain proposed http://ru.netbeans.org...
> 
> Why not just use the content language the browser sends 
> and use that as an indicator for which language to present
> to the user?

This is a nice idea, and the next version of Sourcecast
will do this.  (Manfred as background, netbeans.org is
hosted on an app called SourceCast, provided by CollabNet.
We don't have server access, and we can't for eg change
apache config ... so we can't do this ourselves right
now.)  Next Sourcecast release is due anytime now.

But, this wouldn't help when there is no translated
version available, and wouldn;t help a non-english
speaker find what other fr/ru/nl/xy content there is.

> > I propose if any page doesn't have a translated 
> > correspondence, then the click on a Flag should point to "Not 
> > Localized Yet" page in French/Russian/etc, maybe with an 
> > autogenerated site map of a corresponding language.
> 
> And then if you click on a page that hasn't been translated yet,
> you can revert back to the original English page.

Yes ... still doesn't help the non-english speaker ...

> Or if you want, you can make the language selection part of the 
> profile that is associated with a cookie for the site?

That's an interesting idea.  We are not able to run
any server side scripting (perl/php/etc) so we would
have to set the cookie via Javascript I think. 
Previously we were reluctant to use JS but if it is our
only choice ...

-- 
Jack Catchpoole
NetBeans/Sun Microsystems
http://www.netbeans.org/