Start by placing controls on the page that hold anything that has to be in a
specific language. You then create a resource file for your default
language.
For any bits that change regularly, you are better to store in a persistant
store, like a database, than resource files, so it is sometimes useful to
put all text in the database and use a custom resource provider.
For menus, you can set the text with resource pointers and use resource
files.
As far as language shown to user, I would start with their default language
(selected in their browser) and then allow the drop down to set a cookie
that overrides that decision.
Regardless of whether you store in a database, you can use a resource
provider. Michele Leroux Bustamante has an article on MSDN on custom
providers that is a good start.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it:
http://gregorybeamer.spaces.live.com/
*************** *************** *************** ****
| Think outside the box!
|
*************** *************** *************** ****
"Jonathan" <no**@none.comw rote in message
news:eB******** ******@TK2MSFTN GP02.phx.gbl...
Before I start creating a new asp.net website, is there a standard way of
making it multi-lingual?
For example, rather than type in body text to a page, should I rather
refer
by number code to a row in a language table from which to pull the
appropriate text? Same with menu elements etc? I am thinking of having a
drop-down on the top-right like MS does with Language and country flag
too.
