Comments on: SharePoint: Planning for the future http://jboye.com/blogpost/sharepoint-planning-for-the-future/ The international community for web and intranet professionals Mon, 30 Jan 2012 19:45:30 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: J. Boye » Blog Archive » Overlooked SharePoint success factors http://jboye.com/blogpost/sharepoint-planning-for-the-future/comment-page-1/#comment-1608 J. Boye » Blog Archive » Overlooked SharePoint success factors Mon, 08 Jun 2009 10:34:27 +0000 http://www.jboye.com/?p=1919#comment-1608 [...] Plan for future versions of SharePoint and see if you can be flexible and postpone the implementation of some of your most complex requirements. For the first many months after the release of SharePoint 2010, you need to a avoid first-mover disadvantage. [...] [...] Plan for future versions of SharePoint and see if you can be flexible and postpone the implementation of some of your most complex requirements. For the first many months after the release of SharePoint 2010, you need to a avoid first-mover disadvantage. [...]

]]> By: Dorothy Hoskins http://jboye.com/blogpost/sharepoint-planning-for-the-future/comment-page-1/#comment-752 Dorothy Hoskins Thu, 23 Apr 2009 02:31:24 +0000 http://www.jboye.com/?p=1919#comment-752 What in particular makes it hard to have 2 flavors of Spanish (or French for FR and CA) with Sharepoint? Does it not respect settings such as es-mx and es-es, fr-fr- and fr-ca? Can you not set profiles for these languages where if content is not available in es-mx, it will default to es-es? I am only asking half with tongue in cheek, as I worked for 3 years on a major corporation's global website (external) and language switching based on more than 30 country settings was one of their biggest headaches. IMHO all decent CMS and web apps should handle doing a switch based on language preferences with defaults to secondary language settings if content is not available in every case in all languages. However, often there is spotty coverage in some languages such as Danish while the German may be complete, for example. So in that case, so you show a mix of English and Danish, or Danish and German, or Danish and some other language? In the US we are often blind to the preferences of other populations for the language settings that they might prefer, such as providing more than one flavor of a language depending on location. If translating everything for Canadian French and European French is not affordable, a company needs to make a business decision on which to support. If their market is mostly Americas, then they can use the French Canadian; if mostly European, use the Euro French. People who work in regulated industries may have to abide by legal requirements to provide translated content in their markets or not be permitted to sell there. That is the type of incentive that companies dislike, but it makes translation a normal cost of doing business and not just a courtesy that a business engages in half-heartedly and cuts back when times are lean. What in particular makes it hard to have 2 flavors of Spanish (or French for FR and CA) with Sharepoint? Does it not respect settings such as es-mx and es-es, fr-fr- and fr-ca? Can you not set profiles for these languages where if content is not available in es-mx, it will default to es-es?

I am only asking half with tongue in cheek, as I worked for 3 years on a major corporation’s global website (external) and language switching based on more than 30 country settings was one of their biggest headaches.

IMHO all decent CMS and web apps should handle doing a switch based on language preferences with defaults to secondary language settings if content is not available in every case in all languages. However, often there is spotty coverage in some languages such as Danish while the German may be complete, for example. So in that case, so you show a mix of English and Danish, or Danish and German, or Danish and some other language?

In the US we are often blind to the preferences of other populations for the language settings that they might prefer, such as providing more than one flavor of a language depending on location. If translating everything for Canadian French and European French is not affordable, a company needs to make a business decision on which to support. If their market is mostly Americas, then they can use the French Canadian; if mostly European, use the Euro French.

People who work in regulated industries may have to abide by legal requirements to provide translated content in their markets or not be permitted to sell there. That is the type of incentive that companies dislike, but it makes translation a normal cost of doing business and not just a courtesy that a business engages in half-heartedly and cuts back when times are lean.

]]>