Hi everybody, I’m thrilled to announce that I’ll be speaking at SharePoint Saturday Ottawa. On Nov the 23rd!

My session: translating SharePoint 2013 from beginning to ending. We’ll cover all multilingualism provided by SharePoint.

With lot of examples and demonstrations we’ll see what are the tools provided to IT pro’s, power users and developers. The goal of this session is to give you some insight about how to get your SharePoint environment in multiple languages seamlessly.

This article is written for SharePoint developers who already developed multilingual webparts.

It is a good practice to localize an application when you develop for SharePoint, which will make the adding of a new language easier.

When we developed for SharePoint 2010 we used to put resources files in hive/config/resources (and then run a stsadm –o copyappbincontent or automate it via a timerjob when activating features)

Or we used to create an empty SharePoint solution element in which we added our files and indicated that the deployment target was the appglobalresources folder (see https://stackoverflow.com/questions/296003/deploy-a-resource-file-to-app-globalresource-folder-on-activation for more details)