|
I am most of the time dealing with 3 Latin languages
(English, French and Spanish), so I don't have any experience with non-Latin
language design issues.
Pro's for language version per object (we tend to refer to
it as horizontal translation) is often easier tracking of what needs
translation.
Biggest problems setting up such a site are
usually:
- what to do with pages that aren't (yet) translated? Don't
show / display in foreign language / warning in the link text /
...
- what to do with content that isn't relevant in another
language?
In any case, you'll have to deal with every single
tiny word, alt text or other UI components that needs translation. This can slow
a site down, unless you use three separate sites with the usual keywords hard
coded.
My experience with customers in a previous life is that the
first reaction is: "yes, everything should be translated 1-on-1". But after
running through the workload and decisions that need to be taken, it's often
downgraded to "well, let's start with the most important pages".
A lot can depend on how quick the content is
updated.
As I'm writing this I would be more and more in favour of a
site per language. Food for thought. But how would one be able to track if
something needs translation or is updated in one language and not in
others?
Alain From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Micha Schopman Sent: 25 August 2005 10:24 To: FarCry Developers Subject: [farcry-dev] Re: Multi-Lingual Content Object based
translations are usually a definite no go. You will not find object based
translations in any medium or enterprise based CM system. There are several
reasons for this; a)
Not every
type of content can be translated because they do not apply to the
culture. b)
Taxonomy
might differ between cultures. So it could well be your translated objects are
not accessible anymore, because a parent object was not suitable for
translation c)
Design
might differ between cultures, ex. different products for different types of
markets. Japanese phones require a different approach to sell, than US phones
for example. d)
It becomes
difficult to manage other aspects of CM, like selecting audience (which
culture), select profile options (which culture), select permissions (different
user groups per culture?), select workflow (idem). The most used approach
is by creating multiple branches, a branch per culture, and you are then free to
create a relation between two objects within two separate branches so you can
easily switch from culture but still stay on the appropriate page.
Micha
Schopman Modern
Media, Databankweg 12 M, 3821 AL Amersfoort
----------------------------------------------------------------------------------------------------------------------------------------------------- Modern
Media, Making You Interact Smarter. Onze
oplossingen verbeteren de interactie met uw doelgroep. From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gary Menzel I have been following this thread in the multiple places
it has been happening. I agree with Geoff. I had a major role in looking
at multi-lingual for an For example, the order and placement of menu items often
needed different cultural VS. linguistic treatment. A design that works
for a Latin language will more than likely fail for an Asian or Arabic based
one. You only have to go and have a look at some of the Japanese or
Chinese sites that are targetted to those audiences to see this.
So, I think the jury is still out on CMS management of
multi-lingual sites. Having said that, if all you want is translations, I'd
think changing the core content object to have an array (i.e. one to many table)
of the different languages for an object node could be one possible
solution. But, as Geoff also point out, it would probably have to
be added by someone who wants the feature. That's how FarCry has
become a "community" project. Regards,
On 8/25/05, Geoff Bowers <[EMAIL PROTECTED]>
wrote: Robertson-Ravo, Neil (RX) wrote:
You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ --- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ |
- [farcry-dev] Re: Multi-Lingual Content Robertson-Ravo, Neil (RX)
- [farcry-dev] Re: Multi-Lingual Content Geoff Bowers
- [farcry-dev] Re: Multi-Lingual Content Gary Menzel
- [farcry-dev] Re: Multi-Lingual Content Micha Schopman
- [farcry-dev] Re: Multi-Lingual Content Robertson-Ravo, Neil (RX)
- [farcry-dev] Re: Multi-Lingual Content Robertson-Ravo, Neil (RX)
- [farcry-dev] Re: Multi-Lingual Content Robertson-Ravo, Neil (RX)
- [farcry-dev] Re: Multi-Lingual Content Robertson-Ravo, Neil (RX)
- [farcry-dev] Re: Multi-Lingual Content Micha Schopman
- [farcry-dev] Re: Multi-Lingual Content Robertson-Ravo, Neil (RX)
- [farcry-dev] Re: Multi-Lingual Content Alain Baute
