Recommended way to localise document-oriented pages.

C

Cat

I've seen many ASP.NET localization samples and tutorials. Most of
them were dealing with simple pages that contain some server controls
and simple labels. Now I know how to localize them but what about
document texts? Suppose that there's a master page that contains
navigation menus, and a content page that contains document text.
Localizing the master page was simple, but what am I supposed to do
with the content page? If the document is all text, then I can force
it to be placed in a resx file, but what about that the document
contains html?

I thought myself and maybe I have to write a whole HTML document in a
seperate file and crop the document html and save it to some other
text-based file, and do this for each languages. Well, I could do so,
but this seems to be very exacting. What is the Microsoft-recommended
way to this job? I wonder how you professionals do this job?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
474,432
Messages
2,571,682
Members
48,796
Latest member
Greg L.

Latest Threads

Top