By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,852 Members | 2,116 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,852 IT Pros & Developers. It's quick & easy.

Need advice on localization

P: n/a
Hi,

We are developing a site that needs to be localized (english + spanish). The
site has a lot of "static" pages with a lot of text, and some dynamic pages.
We are unsure how to develop the static part. We could use a
localize/literal control and stick content in a resx-file - but it could be
several paragraphs in pure HTML and the text is not 100% static. It might
change a few times a year. Another way is to have two html pages and some
code to grap the right one based on culture, and stick the content in a
literal.This solution would need some output caching - but thats not a
problem.

What would your advice be - resx (can we get a good resx editor to handle
html?) or "our own solution"? Or do you have any alt. advice?

Thanks
Sep 27 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Depending on the nature, a third option is to use a custom localization
provider and a database. Michele Bustamante (look ma, no accents - yeah, I
am being lazy) has a couple of great articles on MSDN on localization. They
are worth a look. One includes localization using a database.

If you go that route, you can use one of the free HTML editor controls to
allow your editors to maintain the text for pages that way.

I also like the HTML version, but would also consider a custom provider if
you go this route, as ASP.NET will automagically do the work for you. :-)

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|
*************************************************
"Hans Artm" <ha*****@hotmail.comwrote in message
news:e5**************@TK2MSFTNGP02.phx.gbl...
Hi,

We are developing a site that needs to be localized (english + spanish).
The site has a lot of "static" pages with a lot of text, and some dynamic
pages. We are unsure how to develop the static part. We could use a
localize/literal control and stick content in a resx-file - but it could
be several paragraphs in pure HTML and the text is not 100% static. It
might change a few times a year. Another way is to have two html pages and
some code to grap the right one based on culture, and stick the content in
a literal.This solution would need some output caching - but thats not a
problem.

What would your advice be - resx (can we get a good resx editor to handle
html?) or "our own solution"? Or do you have any alt. advice?

Thanks

Sep 28 '07 #2

P: n/a
Thanks,

HTML-version it is then - a custom provider seems to be overkill in this
project. Will look at MBs articles though

Thanks
"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamMskrev i en
meddelelse news:en**************@TK2MSFTNGP05.phx.gbl...
Depending on the nature, a third option is to use a custom localization
provider and a database. Michele Bustamante (look ma, no accents - yeah, I
am being lazy) has a couple of great articles on MSDN on localization.
They are worth a look. One includes localization using a database.

If you go that route, you can use one of the free HTML editor controls to
allow your editors to maintain the text for pages that way.

I also like the HTML version, but would also consider a custom provider if
you go this route, as ASP.NET will automagically do the work for you. :-)

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box! |
*************************************************
"Hans Artm" <ha*****@hotmail.comwrote in message
news:e5**************@TK2MSFTNGP02.phx.gbl...
>Hi,

We are developing a site that needs to be localized (english + spanish).
The site has a lot of "static" pages with a lot of text, and some dynamic
pages. We are unsure how to develop the static part. We could use a
localize/literal control and stick content in a resx-file - but it could
be several paragraphs in pure HTML and the text is not 100% static. It
might change a few times a year. Another way is to have two html pages
and some code to grap the right one based on culture, and stick the
content in a literal.This solution would need some output caching - but
thats not a problem.

What would your advice be - resx (can we get a good resx editor to handle
html?) or "our own solution"? Or do you have any alt. advice?

Thanks


Sep 28 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.