The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Well hypothetically speaking you would need to have a separate language translation for every single piece of content. Whether it be a blog post, article, comment, etc. So for example, you would need one table with all the languages and a separate table for each piece of content holding every translation.

blogs
-- blogs_id
...

languages
-- languages_id

blog_translations
-- blogs_id
-- languages_id

Just as an example. So that every blog can have a different translation.Then you would need to do the same with say comments, articles, etc.

comments
-- comments_id

articles
-- articles_id

comments_translations
-- comments_id
-- languages_id

articles_translations
-- articles_id
-- languages_id

That is where I would start. That is if you weren't using a automated system and needed different *custom* translations for every piece of content.

Now I have some few questions
1> How to present the field to be translated
a> Atricle Title (En) ...input field goes here...
Atricle Title (Nl) ...input field goes here...
......
b> Or using the tabs
c> How to make effective inserts/updates
2> Suppose initially we have two languages and there are datas in articles_content for the related languages.

Now I have some few questions
1> How to present the field to be translated
a> Atricle Title (En) ...input field goes here...
Atricle Title (Nl) ...input field goes here...
......
b> Or using the tabs
c> How to make effective inserts/updates
2> Suppose initially we have two languages and there are datas in articles_content for the related languages.

I would say the language choice should be in a dropdownlist ..so avoid using one input field per Atricle Title ..

I think the example you provided is of structure no 3 which is the generalised form.
Obviously this deals with the lots of complex query operations.
Any further discussion / analysis are warmly welcome.