ASP.NET and Localized Content
-
Hello, I am new to the forum and am seeking some advice about my website redesign. We are creating an ASP.NET site with a sql backend. Our site is a heavily content-based site. We are looking to have an English and Spanish site. Ideally, I would like all the content to be stored in a separate file or db.I have read a few articles about localization but still have some unanswered questions. My questions are as follows: 1. Considering that most of our content is comprised of many paragraphs, what is the best method to store the content? Is it best to use sql db rather than xml to store text? (I have seen arguments for both and am leaning toward sql db.) 2. Will there be significant delays with displaying content given the fact that the site is such a heavily content-based site? Thank you in advance for your suggestions and input. Allison
-
Hello, I am new to the forum and am seeking some advice about my website redesign. We are creating an ASP.NET site with a sql backend. Our site is a heavily content-based site. We are looking to have an English and Spanish site. Ideally, I would like all the content to be stored in a separate file or db.I have read a few articles about localization but still have some unanswered questions. My questions are as follows: 1. Considering that most of our content is comprised of many paragraphs, what is the best method to store the content? Is it best to use sql db rather than xml to store text? (I have seen arguments for both and am leaning toward sql db.) 2. Will there be significant delays with displaying content given the fact that the site is such a heavily content-based site? Thank you in advance for your suggestions and input. Allison
Seems you are building some kind of CMS (Content Management System), anyway in such cases where you store too much paragraphs and they are localized I think you should go toward database. If you designed the app very well and took in consideration all minor details trust me performance will eliminate it self on the spot. having Xml is something horrible for large texts that you will have to live with through the development and maintenance life cycles of the your app.
Sincerely Samer Abu Rabie Imagination is more important than knowledge !