Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Good day, SharePointers a customer requirement is to have CVs entered in a list with his name in English and a local language. which means we will have a field for each language.

is there a better way to accomplish that in SP 2010?

thanks

share|improve this question
    
what do you mean, "a field for each language". why don't you want to use only two fields: for english & for local language? –  Andrey Markeev Apr 20 '11 at 13:06

3 Answers 3

up vote 2 down vote accepted

Could you not limit it to the following columns?

  1. Name (English)
  2. Name (Local)
  3. Local Language
share|improve this answer
1  
Jaap is back :-D –  Anders Rask Apr 20 '11 at 12:50
    
it has so many other columns including lookup and description. –  Bassel Alkhateeb Apr 20 '11 at 13:18
    
I'm not sure I got what you meant though –  Bassel Alkhateeb Apr 20 '11 at 13:19
    
Will you ever store more than 2 names against one item? If not, why would you need a column for each language? You could have an optional third column to indicate which language the non-English version of name was in. Obviously your other columns would be added to the list as well, I am just listing the ones you would need to allow for multilingual names. –  Jaap Vossers Apr 20 '11 at 13:30
1  
No official way. What I am proposing gets around having a column per language, does it not solve your problem? –  Jaap Vossers Apr 20 '11 at 14:15

What if you create another list for CV information. That list should columns: linking id, language(valuelist) and CV-text. By that way there you could have as many languages as you want.

share|improve this answer

I wouldn't create a column for every language, unless it is limited to only a few as you will run out of available columns eventually.

Other options include:

  • One field that stores all the other non-primary language names

  • Create a second list with: Name, Localized Name and Locale columns. Make the Name column at look up to your primary list & Locale could be a choice field with the various locales in it. Enter a row for each localized name for that person. A typical One to Many DB relationship. A stretch goal could be to customize the primary List View to show the related name rows inline.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.