Hi David, hi List i had some thoughts about the same problem. What is best practice for multi language nodes.
Maybe you can share some experience you made during the last month with your solution? I prefer the "One Tree with Translation" solution, because if i have i.e. product contents in different languages it is possible to switch between the languages and simply determine a fallback. A Product Gizmo52 can have a description in eng, de, fr the node tree could look like: /products/gizmo52/eng /products/gizmo52/de /products/gizmo52/fr I could also easily determine which description languages are available for the product gizmo52 (more easily than with a different tree for each language). I also thought of a proper way to map this structure to OCM classes. I.E. a content object with a collection of language objects?! What do you think? Cheers Sascha
