Hi, Joe.

I Hope the mojoPortal  be a realy multi-language.

Now some parts have become multi-language through App_GlobalResources\*.resx.

But other part have not become multi-language, e.g when I add a new page,  in the "page name" text box, i can only set a page name,

If I set page name for Chinese people, then other-language people can't understand, if I set Japanese name, then Chinese people can't understand....

So, I hope the page name's format can be this:

首页/zh-cn/;Home/en/;xxx/JP/;xxx/KR/....

when the ie's codepage is zh-cn, then the page name show 首页,  when the ie's codepage is en, then show Home.....,

or add a select language combox in the page for users.

Microsoft's Dynamic CRM can fit all language's people, he use xml string to store codepage<->name  pair in database.

Thanks!

Hi, Joe:

  You are right.

  But I think if these parts can't be multi-language, the other parts become multi-language through App_GlobalResources\*.resx has not too much meaning or effect too.

  I think I can do it by myself if I need this function one day. I can use the  page name as a key to find a translated name  in App_GlobalResources\*.resx, if find, I change the page name to the translated string in *.resx, if not find, I do nothing. thought this method, I can translate the page name as other parts too.

Thanks!

I'm doing a company web site which supports 3 languages. At first, i followed Joe's idea and i setup 3 child sites for the 3 languages. My team developed a few modules and it is fine as our modules supports multiple locale. For the sake of content creator, we created a HTML module which supports editing different language in the editing page (kinda redo of the existing HTML module in mojoportal). This approach still works fine. Until recently, we notice that some modules are not meaningful to have an instance for each language, such as forum (or blog, although you may argue). What we think is we need a mechanism of fallback or switching between sites in case a module cannot be found. Another problem is, to allow implementation of "language button" switching between languages, we have to make sure either the page ID or the page name add to the portal is the same across the 3 child websites. This makes the work for people doing content management difficult if the number of pages and modules is not small. Considering this factors (we understand the advantages of using 3 sites, as we're doing it now), our team is thinking of doing 3 languages in a single site. But this requires works to modify mojoportal core and so we don't really favor this as we continue to update Joe's source from SVN :P

This a kind of a trade-off problem.