Closed Bug 703183 Opened 13 years ago Closed 13 years ago

Ask for languages spoken as part of the registration

Categories

(Participation Infrastructure :: Phonebook, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
2012-09-12

People

(Reporter: limi, Assigned: aakashd)

References

Details

A very valuable thing to be able to find via mozillians.org would be language(s) spoken. The reason I think it should be a proper field in the DB instead of tags are: a) It's central to whether you can communicate with the person. b) It should be able to be localized, in the cases where I don't know what Tagalog is called in English, but know what it is in Norwegian. We're using tags right now, but they have multiple problems — you won't think to add them since we don't ask, they aren't localizable, trying to establish a "community standard" for how languages are listed is unlikely to work out, and should I list "Norwegian" or "Norsk" or "Norsk (Bokmål)" or…
Hey Bram, Can you take a look at this. It might fit well with the addition of "Languages" tags in the new Edit Profile UX we're doing.
Depends on: 699866
Blocks: 699866
No longer depends on: 699866
This is a good proposal. Languages additions can be done easily and across devices by using a dropdown menu. We can try to be smart and autocomplete, or detect the user’s Firefox UI language and preselect that language upon registration, but this feature is best saved for the next version. We can focus on getting basic language selection that works across devices and will scale well. The best practice is to call out a language by its local spelling and name, and then order it alphabetically. So: * Français, not French * русский, not Russian * 日本, not Japanese * 中文, not Chinese * हिन्दी, not Hindi And so on.
Assignee: nobody → mozaakash
Depends on: 782724
Depends on: 785944
Fixed by bug 785944.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2012-09-05
Target Milestone: 2012-09-05 → 2012-09-12
Verified in bug 78544.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.