Hi Guys
Having separate site structures in different languages can turn into a
consistency nightmare, and after having done a few multi-lingual custom
projects with our software, I agree that forcing the site structure on
each language helps maintain consistency or structure, and also helps
Hi Andre,
On Wednesday, November 6, 2002, at 11:53 AM, André Milton wrote:
Hi Robert,
Big big big issue here. In Montreal (where we are) everything MUST be
english and french (by law). I don't think I've ever built a
non-multilingual site... oh maybe 1 but I was in New York at the time.
;)
Hi Chris,
I don't think you understand what I'm saying. There are no language
specific pages. You don't "force pages into their respective tongues".
It's the other way around. A page should have "versions" in every tongue.
And it definately isn't machine translation... Don't know where y
is Johnson
-Original Message-
From: André Milton [mailto:a@;mlore.com]
Sent: Wednesday, November 06, 2002 12:53 PM
To: Robert Clarke ; Mattias Konradsson; [EMAIL PROTECTED]
Subject: RE: [cms-list] multi-language cms
Hi Robert,
Big big big issue here. In Montreal (where we are) every
Hi Robert,
Big big big issue here. In Montreal (where we are) everything MUST be
english and french (by law). I don't think I've ever built a
non-multilingual site... oh maybe 1 but I was in New York at the time. ;)
I can safely say from experience that even though sites today are often
Hello Mattias,
There are many ways to do it and it is really up to you to decide how you
want to do it. I think the best approach is to keep all files in the same
directory because there is often media shared by all languages that's best
stored in the root. Flat navigation is also easier
.com]
>>Sent: Wednesday, November 06, 2002 3:49 PM
>>To: Voigt, Ingo, NMG-FC; 'Lennart Regebro'; [EMAIL PROTECTED]
>>Cc: Apoorv Durga
>>Subject: Re: [cms-list] multi-language cms
>>
>>
>>Not necessarily. Usability is more about
>>- keeping the use
Not necessarily. Usability is more about
- keeping the user informed (visibility of system status)
- enabling them to complete tasks
- not getting in their way when they try and complete a task
- user control and freedom (always give the user a way out)
- consistency and standards
- error preventio
>>if you click
>>on the link on the home page labelled "Google.com [English]",
>>they will
>>set a cookie and you'll never be redirected to google.de again.
>>
>>It's easy but not explained.
Kevin,
OK, I have to admit I'm one of those purists who don't accept cookies. So
that may be no problem fo
> Ingo Wrote
> >your example has this done in a nice way. But there is also
> one way how this
> >shouldn't be done. www.google.com, when I enter it with a
> german version of
> >the browser I get redirected to www.google.de, no matter
> what. I would call
> >that usability. Since in my understa
Ingo Wrote
your example has this done in a nice way. But there is also one way how this
shouldn't be done. www.google.com, when I enter it with a german version of
the browser I get redirected to www.google.de, no matter what. I would call
that usability. Since in my understanding usability is abo
> > Are there any other issues to keep in mind when doing
> > multi-language sites?
>
> There are loads of issues with multilingual sites.
In addition to the predominantly technical issues Robert mentions, there are
also business issues. Do you primarily author in one language and translate
to
At 10:25 2002-11-06 +0100, Voigt, Ingo, NMG-FC said:
>>At 00:00 2002-11-06 +0100, Lennart Regebro said:
>>When doing language aware sites I think the language should
>>be selected
>>automatically from the languages selected in the browser, but
>>that it's also
>>important to have a possibility to s
> From: <[EMAIL PROTECTED]>
> > Wouldn't users rather expect the domainname to change ?
> > Like:
> >
> > konradsson.fr
> > konradsson.de
> > konradsson.dk
>
> To me that indicates that you have company prescence in all of these
> countries. That is only one reason that you want a multiple-langua
Hi Mattias
> a) Should the url for a document in different languages be the same or
> different, ie "document.html/sida.html" vs
> "document.html?langID=1/document.html?langID=2" I'm leaning towards the
> second alternative since it's easier to manage but I could be wrong on this.
I'd lean towa
[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, November 06, 2002 1:50 AM
Subject: RE: [cms-list] multi-language cms
> right but hasn't the user by using the german version of browser already
in
> a way decided?
>
> > your example has this done in a nice way. But there
From: <[EMAIL PROTECTED]>
> Wouldn't users rather expect the domainname to change ?
> Like:
>
> konradsson.fr
> konradsson.de
> konradsson.dk
To me that indicates that you have company prescence in all of these
countries. That is only one reason that you want a multiple-language site.
Best Regard
right but hasn't the user by using the german version of browser already in
a way decided?
> your example has this done in a nice way. But there is also
> one way how this
> shouldn't be done. www.google.com, when I enter it with a
> german version of
> the browser I get redirected to www.google
>>right but hasn't the user by using the german version of
>>browser already in
>>a way decided?
My personal opinion:
But that's that not what I would expect when I explicitly select the
com-site. Especially when there are differences in what you find on the
different country sites.
--
http://cms
Lennart,
>>When doing language aware sites I think the language should
>>be selected
>>automatically from the languages selected in the browser, but
>>that it's also
>>important to have a possibility to select langauges manually,
>>by a drop down
>>box, for example. http://www.energy-plus.org/
From: "Mattias Konradsson" <[EMAIL PROTECTED]>
> a) Should the url for a document in different languages be the same or
> different, ie "document.html/sida.html" vs
> "document.html?langID=1/document.html?langID=2" I'm leaning towards the
> second alternative since it's easier to manage but I cou
Hi Mattias,
just what came to my mind right away...
>>a) Should the url for a document in different languages be the same or
>>different, ie "document.html/sida.html" vs
>>"document.html?langID=1/document.html?langID=2" I'm leaning
>>towards the
>>second alternative since it's easier to manage
22 matches
Mail list logo
