forgot to say the problem is on the keyboard: it writes with ÅÅ£ instead of ÈÈ

Does this problem occur at the text console or under X11? What's the contents of your /etc/sysconfig/keyboard file?

Note that some of the Romanian keyboard maps in the kbd package have this note:

# This one uses the correct Šand ţ with comma below but many fonts don't have
# these character, so we keep it as an option for now

so the mapping you're seeing is likely "correct" as far as the authors are concerned. You may need to switch to a different mapping to use the alternate characters.

It's true there is no ro.uni file, but there is iso02.uni and lat2.uni.

CC: (none) => dan

And who are the authors, because I am writing many pages/day in this language and never exaust myself with those cedillas. Comas would be coorect. As I can see on my monitor "," looks like the little thing beneath "t" in "È".

About the keyboard file, it is now in US because I usually write by hand.

adding Pablo to the cc, in case he can help

CC: (none) => marja11, pablo

The "ro2" keyboard map, in unicode mode, correctly sends U+0219    U+0218 and U+021B    U+021A; that is, the "with comma" variants of the letters.

If the problem is about text mode *display* it depends on the console font used.

Likely it won't be fixed. The problem is that the amount of simultaneously displayable symbols is limited (to 512 ones, I think), so similar looking glyphs have been unified (various codepoints use the same symbol to display).

If you find a console font with better looking glyphs, you can use it.
But including another font in the distribution takes place on the installer (and place at install time is a very sc

very scarce ressource. Having less space for a minor display problem, and a console one, is not a wanted thing.

But, if you know of a better looking console font (a romanian specific MS-DOS font for example), you can just use it.

If a font has both "with comma" and "with cedilla" variants, the proper one will be displayed; but if a font has only one variant, then both letters will display using the same glyph (it is better than displaying nothing, the goal is to be able to read text).

The "ro" keyboard "ro.map" is altready in unicode description; so there is no problem if "ro.uni.map" is missing (actually, ro.map *is* ro.uni.map; a symbolik link could be made, if needed).

And it is sending the right symbols.

To check it, you can edit a text file in console, and open it on a graphical editor, you will see the proper letters have been typed.

Resolution: (none) => INVALID
Status: NEW => RESOLVED

So editing in console uses comas? How can this be repaired after installing Mageia?