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.
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"
news:eBevkZ1mIHA.2396@TK2MSFTNGP02.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.
>
>
>
Hi Jonathan,
Sure, globlization/mutli-lingual application development is supported from
the begining of .net framework. Ever since 2.0, ASP.NET web application
has much improved multi-lingual web application development (especially
when you design page in Visual Studio 2005 or new VS 2008). For example,
when you create the page in designer, you can specify the page to load
property values from resource items rather than static values. And then,
you can author the resource files for different languages. Here are some
web article that can give you some quick view and ideas:
#Localization Made Easy with ASP.NET 2.0
http://www.codeguru.com/csharp/.net/net_asp/miscellaneous/ar ticle.php/c12407
/
#How to build Multi-Language Web Sites with ASP.NET 2.0 and VS.Net 2005
http://www.c-sharpcorner.com/UploadFile/mosessaur/aspnetloca lization02042006
165851PM/aspnetlocalization.aspx?ArticleID=96602e53-0fb1-44e c-a67b-1c68b05eb
2e1
You can also get more ideas from MSDN reference or the ASP.NET quickstart:
#ASP.NET Globalization and Localization
http://msdn2.microsoft.com/en-us/library/c6zyy3s9.aspx
#Internationalizing Your Application
http://quickstart.developerfusion.co.uk/QuickStart/aspnet/do c/localization/d
efault.aspx
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx .
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Jonathan"
>Subject: How to make asp.net website multi-lingual from the outset
>Date: Fri, 11 Apr 2008 09:56:33 +1200
>
>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.
>
>
>
>
Thanks Stephen.
"Steven Cheng [MSFT]"
news:fS%23tgZ4mIHA.8872@TK2MSFTNGHUB02.phx.gbl...
> Hi Jonathan,
>
> Sure, globlization/mutli-lingual application development is supported from
> the begining of .net framework. Ever since 2.0, ASP.NET web application
> has much improved multi-lingual web application development (especially
> when you design page in Visual Studio 2005 or new VS 2008). For example,
> when you create the page in designer, you can specify the page to load
> property values from resource items rather than static values. And then,
> you can author the resource files for different languages. Here are some
> web article that can give you some quick view and ideas:
>
> #Localization Made Easy with ASP.NET 2.0
>
http://www.codeguru.com/csharp/.net/net_asp/miscellaneous/ar ticle.php/c12407
> /
>
> #How to build Multi-Language Web Sites with ASP.NET 2.0 and VS.Net 2005
>
http://www.c-sharpcorner.com/UploadFile/mosessaur/aspnetloca lization02042006
>
165851PM/aspnetlocalization.aspx?ArticleID=96602e53-0fb1-44e c-a67b-1c68b05eb
> 2e1
>
> You can also get more ideas from MSDN reference or the ASP.NET quickstart:
>
> #ASP.NET Globalization and Localization
> http://msdn2.microsoft.com/en-us/library/c6zyy3s9.aspx
>
> #Internationalizing Your Application
>
http://quickstart.developerfusion.co.uk/QuickStart/aspnet/do c/localization/d
> efault.aspx
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
> Delighting our customers is our #1 priority. We welcome your comments and
> suggestions about how we can improve the support we provide to you. Please
> feel free to let my manager know what you think of the level of service
> provided. You can send feedback directly to my manager at:
> msdnmg@microsoft.com.
>
> ==================================================
> Get notification to my posts through email? Please refer to
>
http://msdn.microsoft.com/subscriptions/managednewsgroups/de fault.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx .
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
>
>
> --------------------
> >From: "Jonathan"
> >Subject: How to make asp.net website multi-lingual from the outset
> >Date: Fri, 11 Apr 2008 09:56:33 +1200
> >
> >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.
> >
> >
> >
> >
>