Tag Info

Hot answers tagged

4

Here is a way to do it in sharepoint 2013 in visual studio 2012 1)Create a empty sharepoint 13 solution Farm solution . 2) Add a sharepoin 13 project into it . 3)Add a mapped foder "Resources" to the project . 4)Now you gonna add three resources one for english "testMutliLing.en-US.resx" and one for german "testMutliLing.de-DE.resx" and one default ...


3

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


2

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


1

You will need to find a translation service that you can access via REST such as Google's or Bing's translation APIs if they support your languages. The problem is you really should write a proxy service and host it so that it can be accessed via your app. This will prevent someone from using your API developer key. You could use SharePoint 2013's proxy if ...


1

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

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.


1

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


1

We finally found a solution: There is a property in the Field tag; Overwrite="TRUE". If this property is set, it will ignore localization of labels, for some reason that I haven't yet figured out. So when I removed this property completely, it worked just fine. Just SharePoint working as designed, I guess!


1

In SharePoint 2013 many (most?) of those strings are available either directly in JavaScript files (localized in folders such as Layouts\1033), or in culture-specific resource DLLs. Many of these DLLs are then loaded through the ScriptResx.ashx handler. For example, see these objects in JavaScript: SP.Res.* -> Loaded through ScriptResx.ashx Srch.Res.* -> ...


1

To get the peer page of the page that you are currently in Use the below method:- ReadOnlyCollection<VariationLabel> spawnedLabels = Variations.Current.UserAccessibleLabels; foreach (VariationLabel label in spawnedLabels) { try { if (!currentUrl.StartsWith(label.TopWebUrl, ...


1

It depends on how the content will be accessed, shared and distributed across different sites and site collections. I think you need to view multilingual support in a broader context before your question can be answered: When you plan for multilingual sites, consider whether you have to create content that will be shared across sites, but must be changed ...


1

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.


1

While SharePoint does provide certain multilingual features, we find that our clients require a little more flexibility and responsiveness in the multilingual user interface and content delivery as well as a simplified method to manage multilingual content and documents. PointFire provides this solution as well as providing many other useful tools for ...


1

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


1

I found one way of showing it in the language I want to show it it in, Japanese. On your site navigate to Site settings -> Site Administration -> Regional settings On the Regional settings page switch your Local to Greek and click ok. Now you calendar view should be in Greek. That is the solution and the problem, at least for me. It now will be in Greek ...


1

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?


1

I don't think this can be done. If you want those site columns to be reused on other sites, having the correct translations, you're better of using a custom solution with a site feature anyway. Suppose you've got your source site and you want to add a new column including translations. Or suppose you've reused you're columns on three sites, and then you ...


1

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, ...



Only top voted, non community-wiki answers of a minimum length are eligible