Home/ Questions/Q 46301
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T15:56:40+00:00

How should I store (and present) the text on a website intended for worldwide

  • 0

How should I store (and present) the text on a website intended for worldwide use, with several languages? The content is mostly in the form of 500+ word articles, although I will need to translate tiny snippets of text on each page too (such as ‘print this article’ or ‘back to menu’).

I know there are several CMS packages that handle multiple languages, but I have to integrate with our existing ASP systems too, so I am ignoring such solutions.

One concern I have is that Google should be able to find the pages, even for foreign users. I am less concerned about issues with processing dates and currencies.

I worry that, left to my own devices, I will invent a way of doing this which work, but eventually lead to disaster! I want to know what professional solutions you have actually used on real projects, not untried ideas! Thanks very much.

I looked at RESX files, but felt they were unsuitable for all but the most trivial translation solutions (I will elaborate if anyone wants to know).

Google will help me with translating the text, but not storing/presenting it.

Has anyone worked on a multi-language project that relied on their own code for presentation?

Any thoughts on serving up content in the following ways, and which is best?

(these are not real URLs, i was just showing examples)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Firstly put all code for all languages under one domain – it will help your google-rank.

    We have a fully multi-lingual system, with localisations stored in a database but cached with the web application.

    Wherever we want a localisation to appear we use:

    <%$ Resources: LanguageProvider, Path/To/Localisation %>

    Then in our web.config:

    <globalization resourceProviderFactoryType='FactoryClassName, AssemblyName'/>

    FactoryClassName then implements ResourceProviderFactory to provide the actual dynamic functionality. Localisations are stored in the DB with a string key ‘Path/To/Localisation’

    It is important to cache the localised values – you don’t want to have lots of DB lookups on each page, and we cache thousands of localised strings with no performance issues.

    Use the user’s current browser localisation to choose what language to serve up.

    • 0