Yes, I definitely need a database because the contents will have to remain editable. What I have in mind is a content management system with a split screen: The left half of the user interface will contain the English content, and the right half the German content. This way, the CMS will be ideal for bilingual people (like me) because they can create text in language A on the left, and then immediately afterwards add the text for language B, without having to constantly refer back and forth between the pages.
I don't actually understand why you suggest to use two database tables. Wouldn't just one be enough? What I have in mind is this:
create table contents (
id int not null auto_increment,
keyword varchar(100) not null,
english text not null,
german text not null,
primary key (id)
To initially populate the table with some data, one might run a script like this:
insert into contents values(null, 'page1_title', 'Welcome', 'Willkommen');
insert into contents values(' ', 'page2_title', 'Products', 'Produkte');
insert into contents values(' ', 'page3_title', 'Contact', 'Kontakt');
insert into contents values(' ', 'page1_heading', 'Hello guys!', 'Hallo Leute!');
insert into contents values(' ', 'page2_heading', 'Our Products', 'Unsere Produkte');
insert into contents values(' ', 'page3_heading', 'Contact Us', 'Kontaktieren Sie uns');
On the actual website there must be a button on top of every page, so visitors can easily switch from one language to the other, that is change the language of the entire website.
Do you get what I mean? In the views the contents will be referenced using the keys from the "keyword" column. Do you think this whole thing would work...? I am not as experienced as you are...
Last edited by PixelLover (2006-10-27 17:11:45)