Comment # 7 on bug 942896 from
Well, actually the console font is managed by the "Language" option in YaST,
not by the "Keyboard layout" one. And I actually think it's correct to define
the font based on the language and not on the keyboard layout.

We have a single yast2-country package that provides 3 YaST clients:

 - keyboard (a.k.a. "System Keyboard Layout")
 - language (a.k.a. "Language)
 - timezone (a.k.a. "Date and Time")

As said, I thing that the console font belongs to the second one, as it is
right now. When changing the language you can ask YaST to adjust your keyboard
according to the new language. But you can also use only the keyboard client to
change the layout without affecting the language (and, thus, the console font).

About the mapping. YaST uses the file /usr/share/YaST2/data/consolefonts.ycp.
As you can see there, our mapping is way more complex than

"latarcyrheb-sun16 for Russian, Hebrew and Arabic; eurlatgr for everything
else"

I would happily simplify our mapping if all the parties agree that it's the
correct thing to do. Just one note about it, we don't have a file called
latarcyrheb-sun16.psfu.gz in our kbd package, so you'll have to point me to the
right one.


You are receiving this mail because: