First of all currently no automatic conversion for text to any specific language.
So, any data which is going to be input you've to make change in each table where those inputted data is being saved.
What I mean suppose you were saving Question text in table namely 'tbl_questions'
tbl_questions {question_id (PK) int , question_text nvarchar(max)}
But now you have to change type of question_text to ntext to support multilingual text and also add an additional field for language and also primary key constraint composite of question_id and languaage_id
.
tbl_questions { question_id(PK) int ,language_id (PK) int, question_text ntext}
Now on you have to save the text in selected language. Which means if you've support for four language then same question text has to save four times against those languages.
So u need to make changes in DB end. Mean while on front end no changes would be required. To render the correct text you have to fetch the data against current selected language.
That's how I achieve multilingual site with resource files and db with ntext field.