none
MSDN globalization style RRS feed

  • Question

  •  

    I'm wondering what technique for localization the MSDN team used on its site ?

     

    Resources assemblies ?? dont think so

    entire different sites per region??

     

    Anyone have an idea?

     

    thanks
    Saturday, October 20, 2007 7:14 PM

Answers

  • The platform (called MTPS) is built on top of a SQL Database with an ASP.NET front end.  All of the page format and content is stored in the database as XML.  We extract this XML and localized the text values in it.

     

    Then we run this XML back into the database to create an exact clone of the source page but in the localized language.  Each language page is differant so that we can change the content by language if desired.  Alot of pages, like technical articles, are localized clones, but many, like the home page or the support pages, are combinations of localized content and also locally produced content.

     

    The platform also uses a series of fallbacks to create "virutal sites".


    For example for French Canadian customers the fallback is

     

    FR-CA-->FR-FR-->EN-CA-->EN-US

     

    This means if a customer requests a page, like http://msdn2.microsoft.com/fr-ca/vbasic/ the system will look for a French Canadian VB Home page.  Since none exists it goes and looks for one in the same language, Since one exists from France it serves this page up in the French Canadian page chrome and replace certain key content items, like the ads, with ones relavent to French Canadians.  This allows us to extend large amounts of content to varoius smallers locales that share the same language.

    Wednesday, October 31, 2007 11:28 PM

All replies

  • The platform (called MTPS) is built on top of a SQL Database with an ASP.NET front end.  All of the page format and content is stored in the database as XML.  We extract this XML and localized the text values in it.

     

    Then we run this XML back into the database to create an exact clone of the source page but in the localized language.  Each language page is differant so that we can change the content by language if desired.  Alot of pages, like technical articles, are localized clones, but many, like the home page or the support pages, are combinations of localized content and also locally produced content.

     

    The platform also uses a series of fallbacks to create "virutal sites".


    For example for French Canadian customers the fallback is

     

    FR-CA-->FR-FR-->EN-CA-->EN-US

     

    This means if a customer requests a page, like http://msdn2.microsoft.com/fr-ca/vbasic/ the system will look for a French Canadian VB Home page.  Since none exists it goes and looks for one in the same language, Since one exists from France it serves this page up in the French Canadian page chrome and replace certain key content items, like the ads, with ones relavent to French Canadians.  This allows us to extend large amounts of content to varoius smallers locales that share the same language.

    Wednesday, October 31, 2007 11:28 PM
  •  

    Wow thats so cool,

     

     

    I want to know more about the localized text.

     

    The text lines are in the Database in every single language?

     

    who translate that?

     

     

    There's and official site regarding to this project?

     

    where can I read About the MTPS project , Architecture- Desing,  hardware platform , farms, etc.

     

    I'm really facinated about this hufe solution.

     

    thanks

    Thursday, November 1, 2007 9:29 PM