Thanks Micha.
Micha Schopman wrote:
The point with multilingual content objects is it forces the user to translate levels before it can use a certain deeper level. I don't want to brag but I have built hundreds of content managed websites, and only some of them wanted object level multilingual content management. Due to the high costs involved in multilingual content (approx. 4 times the usual cost) they still haven't got things right, and the clients with branching do. Situations were you have the exact structure for each language are very hard to find.
Yes sure. But thats exactly whats needed for my special case.
I would go for branching initial, and fake the object level by relating different instances to eachother. This is how I've done it in my own system, and currently I have no complaints from the 80 customers running on the system :)
Btw, think further, what are you going to do with links from google on a certain object id? Are you gonna give them a page in the default language, or the language defined in their browsers? .. and even then... is that information relevant to that culture?
You're right here. This would be an subject especialy for public sites.
This could be solved if the URL call would reference the language object below the dmHTML object for example. The CMS gets the language objectID for an content object and from an reference table it knows the dmHTML object. Above there must be an table which keeps available languages for selecting in the PLPs and maybe an standard language. In any case you have an unique objectid. Catching spiders in the way you want should'nt be an big deal then.
Regards,
Silvio
--- 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/
