Sladescross's Blog

Blogging about Sharepoint related stuff

SharePoint Search Index Language Aspects July 5, 2012

Filed under: Language,Registry,Search,Stemmer,Wordbreaker — sladescross @ 9:03 am

en-us English (United States) en-gb English (United Kingdom)
en-au English (Australia) en-ca English (Canada)
en-nz English (New Zealand) en-ie English (Ireland)
en-za English (South Africa) en-jm English (Jamaica)
en English (Caribbean) en-bz English (Belize)


sb Sorbian es Spanish (Spain)
es-mx Spanish (Mexico) es-gt Spanish (Guatemala)
es-cr Spanish (Costa Rica) es-pa Spanish (Panama)
es-do Spanish (Dominican Republic) es-ve Spanish (Venezuela)
es-co Spanish (Colombia) es-pe Spanish (Peru)
es-ar Spanish (Argentina) es-ec Spanish (Ecuador)
es-cl Spanish (Chile) es-uy Spanish (Uruguay)
es-py Spanish (Paraguay) es-bo Spanish (Bolivia)
es-sv Spanish (El Salvador) es-hn Spanish (Honduras)
es-ni Spanish (Nicaragua) es-pr Spanish (Puerto Rico)


<QueryText language=xml:lang type={STRING|MSSQLFT|FQL}> searchQuery </QueryText>

Language detection for search queries.

If the above is not set by a user, an administer can set language on each search page as follows: a. Edit the search results page b. Edit the core results web part c. Under Result Query Options – Use the Query Language Dropdown to select the preferred language for the results page

Wordbreakers and stemmers registry settings.

Force language settings for query results.

Basically, when a configuration is taken from the browser – it could easily be manipulated via code. This gives us a very simple solution to the IE Language problem. Here’s what you need to do:

  • Create your own search results page (can be done by copying the default)
  • Configure the search to use your new results page.
  • Now, use the new page and code it to set a hard-coded culture – The code should be executed in the page load event. That’s it. Effectively, this will make a unanimous culture for all of the clients in the system and the speller/results will always the same.

Enable language sensitive search results.


However, it’s not always desirable behaviour. In a multi-lingual site with a variation for each language the search results should be in the language of the current variation.

By default SharePoint will ignore the variation settings and still take the browser language.

There are several posts with the same problem, here and herehere. The suggested solutions range from changing the browser language programmatically to creating a new masterpage with the Culture hard coded, to subclassing the search results web part and changing the Culture settings in the OnInit event.

Unfortunately these solutions either do not work or require a lot of work for a simple change.


About these ads

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


Get every new post delivered to your Inbox.

Join 63 other followers