|
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/ |
- [farcry-dev] Re: Multi-Lingual Content Geoff Bowers
- [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 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
