Tag Info

Hot answers tagged

6

If you examine page source you will see that Select Display Language > Language calls simple javascript: OnSelectionChange(1033); Where 1033 is language id. I have tried launching this form FireFox FireBug console and it works. So your link could be something like: <a href="" onclick="OnSelectionChange(1033);">English</a> You can also ...


6

Use the System.Threading.Thread.CurrentThread.CurrentUICulture.LCID to get the current LCID


5

What you are seeing sounds like you are seeing a My Site created in english and where the pt-BR alternate language has been enabled and selected. The SharePoint MUI does not handle webpart titles, so My Site, my profile, etc will be a mix of languages unless you are using a third party product like PointFire and enabling the feature on these sites. You ...


5

You can create a JS object and fetch the values using the LCID: var CultureNames = { 1033:"en", 1036:"fr" };//Store it in a utility file somewhere. var currentCultureName = CultureNames[SP.Res.lcid]; //will return 'en' if current culture is english.


4

I did it last week using this article: Mirjam's thoughts on SharePoint: Changing the language of an existing SharePoint site


3

Did you manually add that link? Looks like the only viewlsts.aspx I can find resides directly in the /_layouts/ directory. It's possible that the old viewlsts.aspx was localized and was replaced in 2010 by a generic viewlsts.aspx containing resource strings.


3

The supported limit is still 50 in SP 2010


3

For shared resource files in SharePoint (i.e. RESX files that must be shared amongst Features/Projects/Solutions), the best thing to do is to deploy them to the SharePoint Root's "Resources" folder (14/Resources). Then you'd reference them in one of two ways. In the RESX reference, you can specify the file name in the RESX reference like so (leaving off ...


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


2

Step by Step instruction to install and configure language pack for SharePoint 2010. http://virtualizesharepoint.com/2011/07/21/installing-language-packs-for-sharepoint-2010/ Once the configuration is completed, navigate Central Administration -> Upgrade and Migration –> Check product and patch installation status. Now Open the SharePoint site -> Site ...


2

This has been quite a wild goose chase! There definitely was a mistake in cmscore.es-ES.resx, however, it's fixed in the service pack for the language pack: http://www.microsoft.com/download/en/details.aspx?id=26621 I had no idea that a service pack was available for the language packs; it makes sense because SP1 and the CUs didn't address any ...


2

Why do it in 2 steps? The New-SPSite cmdlet takes a webtemplate and a title parameter too?


2

Could you not limit it to the following columns? Name (English) Name (Local) Local Language


2

The default language for a whole SharePoint system is based on the installation language of original SharePoint installation media and cannot be changed (without a re-install). With additional language packs, site collections can be created in a selection of languages, but once again, once the site collection has been created, the default language cannot be ...


2

There is no supported way of changing the language of a site.


2

You can use resource files to allow our custom application page to be available when users switch languages. Check a very good example on how to do it But just make sure SharePoint 2010 installation has different language packs deploy. It can easily be checked If you jump into Site Actions > Site Settings you should have a link under the ‘Site ...


2

You need to run additional timer jobs. For the root variation (in your case english), running the Variations Create Hierarchies Job Definition is sufficient to create the hierarchy. For all additional variation labels you need to start additional timer jobs. In central administration you should see these 4 timer jobs related to variations (per web ...


2

An interesting question! I assume you want to load the locale in javascript (in order to use it with Globalize.js). Regardless the solution I see some problems: What data source to trust: navigator.language, user prefered language in browser (Accept-Language) or SPRegionalSettings of an SPUser? What if the user locale differs from the web locale and you ...


2

Look at this post. To check which SharePoint language packs were installed - check registry. For SharePoint 2010, change 12.0 to 14.0 and for 2013, change it to 15.0. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\InstalledLanguages\ here you will see something like this: LCID – Reg_SZ – {language pack build level} ...


2

Modifying the resources files is your only option unless you want to replace them with your own. Yes, some may consider it a big no-no. But there isn't much other option. Just make sure to keep backups of the resources files you do modify, in case the files gets overwritten by an update from Microsoft.


2

There is a typo in your success callback function. Replace the line: function onRequestSucceeded(web, args) { to function onRequestSucceeded(sender, args) {


2

SPRegionalSettings.TimeZone property gets the time zone that is used on the SharePoint server. Example using (var site = new SPSite(siteUrl)) { using (var web = site.OpenWeb()) { var regionalSettings = web.RegionalSettings; var tz = regionalSettings.TimeZone; Console.WriteLine(tz.Description); } }


1

I'd use uint localIdentifier = (uint)SPContext.Current.Web.Language; to create the new web using the same language as used to create the current web, and then set locale after creation


1

One way to do this without accessing the database is to use site templates (or probably even export/import). It's not very pretty, but the theory is simple and it have worked for me: Save site as template Find, download and extract the WSP (it's a CAB file). Create missing resource files, find and replace all current language ids (like 1033) with the one ...


1

The language toggle is actually just a javascript function that sets a cookie and reloads the page. You can put it anywhere. It was very cleverly named: OnSelectionChange(lcid) To have for example a French/English toggle, put the following div in your page: <div class="language-switch"> <a id="language-fr" ...


1

You can use localization which is a .NET feature to provide resources based on the culture of the user. This MSDN article explains localization in context to SharePoint development (http://msdn.microsoft.com/en-us/library/ee696750.aspx). You can generate two resource lists, one in english and one in French. Then you can tell the feature to display the ...


1

This sounds a lot like a bug in Office Web Apps. When Office Web Apps is installed, it overrides the file links in sharepoint. It looks like there is some language selection related error in the functionality that does the overriding. Could you try enabling / disabling the "Always open in client application" site collection feature?


1

If you dont want to set up a site collection at http://www.somecompany.com, You can achieve the redirection using httpmodule. The httpmodule is applied at web application level so it doesn't care if your site collection really exists. In the httpmodule, You can check for Accept-Language header using the Headers collection in the Request object : ...


1

Double check to make sure cmscore.es-ES.resx file actually exists in the Resources (or App_GlobalResources, I can't remember which of the two cmscore exists in). This kind of thing happens when it can't find the resource file for the target locale so falls back to the operating system language (English). If it's not there, reinstall the language pack for ...



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