Note that in Figure 2, the pages are all mirrored in the language-specific directories. Although all of the pages show up for both languages, you could easily be missing pages in a specific language if those pages had not been localized. The code in lang.asp checks to see which pages are actually present. In the case of frameless pages, the same architecture is used, but a redirect moves to the localized content. (On Windows 2000 I use Server.Execute, which allows me to completely hide the site's architecture from people viewing its content. Unfortunately, Server.Execute is call specific to version 5.0 of Microsoft Internet Information Services, so you can't do this with WindowsÂ® NT 4.0.) For the frame pages, server-side scripting takes care of building the list and setting up links, while the client side does the actual navigation work. In the frameless pages, everything is done on the server. The use of locale IDs (LCID) also makes it easy to provide localized content, for instance specific date, time, currency, or number formats for a given locale. You can read more about this in the Microsoft Knowledge Base article Q229690; I use a slightly more complex scheme than the one that's described in the Knowledge Base article.
Set cnv = Server.CreateObject("TsiAToW.Convert")
' Convert the string in stUnicode to UTF-8 and write
' it out with BinaryWrite so that the IIS 4.0 ASP can
' handle the job
Response.BinaryWrite cnv.WToA(stUnicode, 65001)
From the July 2000 issue of MSDN Magazine.
More MSDN Magazine Blog entries >
Browse All MSDN Magazines
Subscribe to MSDN Flash newsletter
Receive the MSDN Flash e-mail newsletter every other week, with news and information personalized to your interests and areas of focus.