Localizing SharePoint: Adding Multi-language Support to Your Site
Upcoming SlideShare
Loading in...5
×
 

Localizing SharePoint: Adding Multi-language Support to Your Site

on

  • 2,027 views

...


More and more, single SharePoint applications are being exposed to international audiences, both on the Internet and the intranets of
the world – and clients only want to pay once. We will dive into how localization works in SharePoint in markup, in code-behind, and in CAML. We will also look at the pros and cons of variations in 2007, and how they have been improved for 2010

Statistics

Views

Total Views
2,027
Slideshare-icon Views on SlideShare
2,013
Embed Views
14

Actions

Likes
1
Downloads
7
Comments
0

2 Embeds 14

http://greghurlman.wordpress.com 13
http://greghurlman.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Localizing SharePoint: Adding Multi-language Support to Your Site Localizing SharePoint: Adding Multi-language Support to Your Site Presentation Transcript

    • Hello!
    • Localizing SharePoint
      Adding Multi-language Support to Your Site
    • Who are you?
    • Greg Hurlman:
      Avanade Group Manager
      SharePoint Architect
      Developer
      Father
      Hokie
      Gamer
      World Famous Jungle Cruise Skipper (ret.)
    • Making life easy through localization
    • Language Packs: Mystery of the MS Download Center
    • Language Packs: Setup
      • No, you’re not screwed.
      • Don’t forget WSS!
      • Don’t forget WSS patches!
      • Going to have to run the Config Wizard at least 4 times
      (It’ll take a while)
    • Demo!
    • Variations
    • Variations
    • Not everything varies
      Yes:
      Publishing Content
      No:
      Page Layouts (all Site Collection-level stuff)
      Permissions
      List Changes (mostly)
      Web Part List References
      Pretty much everything else
    • So why bother with them?
      • Easy content management for end users
      • Automatic user redirection
      • Workflow-driven translation possible
    • Demo!
    • On with the code
    • So what can we build with this stuff?
      • Everything you’re already building
      • No more magic strings
      • Resources!
    • Resources: Learn to love them
      • All your strings/images/etc are belong to them
      • Stay neutral
      • One .resx per locale
      • Just say no to Properties/Resources.resx
    • Where do I put these .resx things?
      C:Program FilesCommon FilesMicrosoft Sharedweb server extensions12Resources
      In a Feature, of course.
    • How do I get my information back out?
      • $Resources:ResourceFileName,ResourceKeyName
      • In XML, just drop it in
      • In markup, surround it with <% %>
      • In code, use SPUtility.GetLocalizedString(…)
    • Demo!
    • What else is new?
    • Shiny!
      • Variations
      • Timer Jobs
      • Content Propagation
      • Site Collection Alternate Languages
    • Demo!
    • Questions?
    • Photo Credits
      http://www.flickr.com/photos/photojonny/2268845904/
      http://www.flickr.com/photos/magdalar/2950663799
      http://www.flickr.com/photos/angelsk/4176291456
      http://www.flickr.com/photos/caharley72/4343295169
      http://www.flickr.com/photos/bestrated1/341866875
      http://www.flickr.com/photos/gilderic/4240700822
      http://www.flickr.com/photos/damaradeaella/2822846819/
    • Thanks for coming!
      • Don’t forget your evaluations
      • You can find me at:
      • Blog: http://greghurlman.com
      • Twitter: @ghurlman
      • FB: http://facebook.com/greg.hurlman
      • Email: greg@greghurlman.com
      • Princeton Area SharePoint User Group
      • SharePoint Saturday New York