Forum OpenACS Q&A: Re: RFC: How to internationalize content

Collapse
Posted by Jun Yamog on
Hi,

In our case the translated will be implemented by pointing the parent id.

Item C.parent_id -> Item B
Item B.parent_id -> Item A
Item A.parent_id -> usual folder id in CR.

It used to be design using relations like as stated above.  I think I change it using parent_id since it has built in tree functions.  What do you guys think?  I guess the draw back is that parent_id does not really say translated.  Although in our case we use it as basically cloned from or copy from.  The use cr_child_rel to denote that its a translation.

Collapse
Posted by Joel Aufrecht on
Maybe we should do both.  I definitely think we should do the child_rel stuff in some form.  I hope that you put it into your current implementation, because if you don't retain that information in your data model, it will be much harder to upgrade to a standard that has explicit translate/localize settings.
But if we have the child rels but don't use parent id, then any query that gets back a bunch of cr_items will have to filter out based on child_rel.  So this argues, if I understand the cr model correctly, for using your parent_id approach for every content item that is a translation or localization of another item.