If you want two sets of LINKS tables (not databases...think out of the flat file system) with different data, but share the same link, then you could do one of the following:
1) Add duplicated fields like the Description field in the LINKS table and then add a new field called Language (this should be an ENUM field - Arabic/English)[/b]. Then you could possibly duplicate the build process across a different set of folders for the Arabic veruse English pages.
OR you could:
2) Use two licenses of Links SQL to cleanly build two different directories without hacking the scripts.
OR you could:
3) Simply use the DYNAMIC script called page.cgi and create a duplicate set of template files in Arabic versus English. Then you would use page.cgi to call the different template sets: English versus Arabic. Out-of-the-box, Links SQL already comes with a set of different templates.
Regards,
Eliot Lee
1) Add duplicated fields like the Description field in the LINKS table and then add a new field called Language (this should be an ENUM field - Arabic/English)[/b]. Then you could possibly duplicate the build process across a different set of folders for the Arabic veruse English pages.
OR you could:
2) Use two licenses of Links SQL to cleanly build two different directories without hacking the scripts.
OR you could:
3) Simply use the DYNAMIC script called page.cgi and create a duplicate set of template files in Arabic versus English. Then you would use page.cgi to call the different template sets: English versus Arabic. Out-of-the-box, Links SQL already comes with a set of different templates.
Regards,
Eliot Lee