Hot answers tagged multilingual
MUI and Variations are 2 different concepts in SharePoint 2010! They both rely on Language packs to properly work, but the purpose is different: MUI only handles UI elements such as Menu Items, Actions Links down to Column Headers (most OOTB are automatically translated, but you need to export Resource files for your own columns) Variations handle CONTENT ...
In SharePoint 2007 every site collection and website is tied to a language, it cannot be changed dynamically. So you have to rebuild a new site collection for each language (French and Canadian one). Furthermore you'll have to adopt you custom controls and web parts to use resource files. By this way you could use your controls and web parts for every ...
You could use some nice work around. The first solution that you could implement is working with the GUID of the list and the column instead of the title. Or you can deploy a service that you can ask for the list and it'll reply to you with the name of the list translated in the current language.
SharePoint 2010 offers 2 ways of multilanguage support: MUI - which is basically loading of resources for standard menus according to language currently selected Variations - which actually consists in using "labels" for languages (more details http://hermansberghem.blogspot.ch/2009/10/best-practices-to-build-multi-lingual.html), which basically generates ...
Though I am not sure about this, you can play with powershell and try to do this. Look at SPWeb.UICulture property and try to set it to some other language and update web. Also look at this discussion: How to change the default site language?
I found some explanations on Timmy Gilissen's Blog of this behaviour: MUI Managed metadata vs. Search http://www.moss2007.be/blogs/timmy/archive/2011/12/01/mui-managed-metadata-vs-search.aspx And a workaround Multilingual Taxonomy Search http://www.moss2007.be/blogs/timmy/archive/2011/08/01/multilingual-taxonomy-search.aspx Hope it helps, Cheers, ...
If I understand your example correctly I think it's impossible to create a library with MUI-enabled name. The url fragment you're trying to localize is a folder in the file system in SP content database. It can be viewed in Windows Explorer via Web-DAV, for example. How do you think this localization can be handled on the file system level?
1 - You need to install the language packs for all the languages do you want to support 2 - You must create a site-collection for all these languages (ex: en-us, it-it, ...) 3 - You need to create and deploy resources for these languages 4 - You must use the resources on your code.
Content translation is always a manual process. Once a variation has been created from a published page, it appears in the target variation as a draft, ready for manual translation. Ensure your list schemas and navigation nodes match your requirements before creating your variation hierarchies. Styling will always be consistent and inherit from the root ...
Only top voted, non community-wiki answers of a minimum length are eligible