MUI Deep dive edition Presented by Andy Van Steenbergen
•Download as PPTX, PDF•
0 likes•441 views
This document summarizes a presentation about developing multilingual user interfaces (MUI) in SharePoint. The presentation covered where to store resource files for different languages, how MUI works in sandboxed solutions versus full trust environments, common pitfalls when using MUI, and how to create custom language packs. The speaker was Andy Van Steenbergen and resources for learning more about MUI included blogs by The SharePoint Baker and Tom Nys.
Recommended
Recommended
More Related Content
Similar to MUI Deep dive edition Presented by Andy Van Steenbergen
Similar to MUI Deep dive edition Presented by Andy Van Steenbergen (20)
More from BIWUG
More from BIWUG (20)
Recently uploaded
Recently uploaded (20)
MUI Deep dive edition Presented by Andy Van Steenbergen
- 1. MUI Deep dive edition Presented by Andy Van Steenbergen #Biwug3011
- 2. About the speaker • Andy.vansteenbergen@biwug.be • SharePoint Consultant at Ordina • Twitter: Meligo • Blog: http://meligo.blog.com • Linkedin: Andy Van Steenbergen #Biwug3011
- 3. Agenda Kind of resources and locations How to develop in MUI MUI in Sandboxed? Last but not least – Lessons learned #Biwug3011
- 4. #Biwug3011
- 5. #Biwug3011
- 6. Can central admin be MUI enabled? #Biwug3011
- 7. #Biwug3011
- 8. MUI in Dev - resource files Language invariant • Muidemo.resx Language neutral • Muidemo.nl.resx Culture specific • Muidemo.nl-NL.resx #Biwug3011
- 9. Mui in Dev Feature resource location 14hiveresources App resources 14hiveconfig and Resources WPResources (legacy) configadminresources Locations #Biwug3011
- 10. #Biwug3011
- 11. #Biwug3011
- 12. Can MUI exist in Sandbox? #Biwug3011
- 13. #Biwug3011
- 14. Dev pitfalls? • There are a couple of downfalls for the use of MUI – Try finding a list via a resourcename (good luck) – Fields: Do not use displayname! (why?) • Always use ID or internal name via a constant class #Biwug3011
- 15. #Biwug3011
- 16. Can you Create your own custom language pack? Yes, just create an empty solution and only add the resource files in this solution linked with lcid So 1043 (dutch-NL) , only dutch resource files But set the solution ID to the original solution Link to MSDN #Biwug3011
- 17. #Biwug3011
- 18. What if Only 1 language is requested? #Biwug3011
- 19. Take away • MUI = resource files (+ language packs) • Forget displayname • Not all site templates support MUI: Blog, meeting workspace #Biwug3011
- 20. #Biwug3011
- 21. Resources MUIExt The SharePoint Baker Tom Nys – tomBlog Microsoft technet Sharepointbits (Sandbox) #Biwug3011
- 22. How many times was the word “MUI” mentioned in this presentation? Last person who was registered is………………… TOM NYS #Biwug3011
- 23. Us SharePint End of session #Biwug3011
Editor's Notes
- If you haven’t installed language packs in your SharePoint environment, “Language Settings” option is never shown under Site Administration section in Site Settings page, also both “Export Translations” and “Import Translations” options show up under site administration section in site settings page as soon as you specify alternate languages.
- In the term store you can select the languages that you want to have for MUICreate new term set, new term group, new term and the new term window you can select the language and enter additional data
- 14 hiveconfig ->copieren van appglobalresources bij het aanmaken van een web appConfig\\adminresources -> mui in centraladminDeployment type ApplicationResource of resx -> wpresourcesHide feature when resources are notavailable
- Business needs to validate the labels Usean invariant resource file even ifyou are notgoingmultilingual (1 placefor label values, no longer in code)
- Beheer van labels -> businessDiscussie
- Zinveranderen
- Business needs to validate the labels Usean invariant resource file even ifyou are notgoingmultilingual (1 placefor label values, no longer in code)
- Business needs to validate the labels Usean invariant resource file even ifyou are notgoingmultilingual (1 placefor label values, no longer in code)