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. :-)

Signature
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
*************************************************
> Hi,
>
[quoted text clipped - 12 lines]
>
> Thanks
Hans Artm - 28 Sep 2007 07:29 GMT
Thanks,
HTML-version it is then - a custom provider seems to be overkill in this
project. Will look at MBs articles though
Thanks
> 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
[quoted text clipped - 25 lines]
>>
>> Thanks