Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to use my first name as an username but it contains character 'ä'. I found this thread.

Now I understand, why some some characters are disabled, but what about 'ä'? Can this character cause any problems?

Why are some unicode characters (ü, õ, ö, ä) disabled, when they are used in full names?

share|improve this question
up vote 8 down vote accepted

On a modern system (with full-out Unicode support), this shouldn't be a problem - with emphasis on "shouldn't". As quoted in that answer,

The default is NAME_REGEX="^[a-z][-a-z0-9]*\$"

Although this may be overly strict for current systems, it makes for easier administration - as in, "one less thing to worry about". Note that the username gets used in many places - e.g. your home directory would probably be of the form /home/username; most sane filesystems have full Unicode support, but as with anything computer-related, sanity under all circumstances is not guaranteed.

Note that there is the actual login name as used by the system (which falls under these rules), mapped to an UID in /etc/passwd, and there's "Full Name", which is a string (and most valid characters can be entered, although there's a "non-ASCII" warning).

What to do: Where applicable, I use the name without diacritics (or romanized, in case of non-Latin scripts) for username, and the real form for Full Name. The entry in your /etc/passwd might then look similar to this:

martrang:x:1001:1001:Märt Rang,,,:/home/martrang:/bin/bash
share|improve this answer
I think that modern desktop OS should allow unicode characters, from the servers part, everything is understandable. – Märt Rang Sep 19 '11 at 13:12
@MärtRang Thing is, nowadays absolutely everything speaks basic ASCII (THANKFULLY -- look up EBCDIC if you ever want nightmares), but beyond that there are about a gazillion different codepages that deal with nonstandard characters, and if both sides of a conversation don't know to use the exact same one, you can get pretty spectacular clusterfucks that take forever to dissect because each side insists the other side is talking gibberish. As Piskvor says, "one less thing to worry about". Pretty much every graphical frontend will use your real name nowadays anyway. – Shadur Jan 12 '14 at 21:39

Using non-ASCII login names is not generally supported and sounds like a recipe for trouble. While UTF-8 is becoming the de facto standard encoding, there are still many people who use other encodings (especially outside the English-speaking world, where people have been using other, incompatible 8-bit or 16-bit encodings for a long time). For example, you're likely to encounter applications that try to interpret your username according to the current locale's encoding, rather than (attempt to) translate it to the current locale's encoding. Your login name is also the left-hand part of your email address, and that is even more likely to cause problems since you're depending on your chosen encoding being supported and respected by all the systems that your mail goes through.

The login name is intended for computers. Use ASCII in your login name. The full name is intended for humans. Use UTF-8 in your full name.

share|improve this answer

The last question is the easiest to answer: Tradition, practicality, simplicity (for the developer) and portability, if you want to be charitable, or alternatively backwardness, impracticality (for the user), ignorance and non-portability, if you don't. US-ASCII is simply the character set which has been used since the dawn of time (pre-web for the youngsters) pretty much everywhere.

In many, many applications there are simply no built-in support for characters outside of what you can see on an English keyboard (and sometimes not even that). In other words, the software may or may not support it, and you can only expect the unexpected.

share|improve this answer
I agree with that when I need to create user to server. Why not to enable unicode characters when you use linux as a desktop OS? – Märt Rang Sep 19 '11 at 13:10
and what if the username is used to access proxy, samba, nfs, or other services ? Or home folders via shared paths ? – Sirex Sep 20 '11 at 6:46

Your Answer


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.