Created attachment 38439 [details] Austrian keyboard layout in symbols/at Austria shares its keyboard layout with Germany (see http://en.wikipedia.org/wiki/Keyboard_layout#Germany_and_Austria_.28but_not_Switzerland.29), but can't be selected in keyboard layout settings yet. I've made a simple symbols file that inherits German layouts and makes them available as Austrian - a small effort to appeal to Austrian users. Not all German layouts are made available as Austrian but those that Austria shares with Switzerland. Furthermore, I've edited the base.xml.in to include references to the Austrian layout. I hope this finds entry into a future release of xkeyboard-config - if there's something wrong with my contribution or something else is to be done, I'd be glad to help! (I've been linked here via https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/447912 after having reported this as Ubuntu bug.)
Created attachment 38440 [details] rules/base.xml.in
Some questions: 1. Are you sure Austria is using all 4 variants? I personally do not know, just would like to confirm... 2. Let's not create symbols/at. Let's do it in rules. Would you be able to provide a patch to rules/base.* files ? 3. Could you please provide not the full base.xml.in file, but the patch? The diff with the current version from git is large.
Hi Sergey, thanks for your rapid response! 1. I am not sure if Austria uses all 4 variants I proposed, because I've never worked with Linux on a Sun or Mac. All I can say is that those variants exist in Switzerland and Germany, so the probability is high that those also exist in Austria, in which case they would be identical to the German layout. 2. I'd like to do that, however, I haven't found out how to adapt the rules files. Could you point me to documentation or other instructions? Which file(s) do I have to modify? 3. Yes, I will make a patch for the latest git version as soon as I have adapted the rules files.
Michael, what you need to do is 1. Grab the source code of xkeyboard-config and keep a copy of the repository sudo apt-get install git-core then git clone git://anongit.freedesktop.org/git/xkeyboard-config 2. According to the changes you did on your Ubuntu installation to get your Austrian layout, add those changes in the files found in the 'xkeyboard-config' repository. Then, to provide the necessary files for Sergey, you simply run (you need to be in the xkeyboard-config/ directory tree) git diff and the output of the file is the patch that Sergey needs. 3. If you mess up and want to start over, you can git reset --hard Sergey, what Michael wants to achieve is to have an Austrian entry in the keyboard layouts. This obviously helps in terms of usability for Austrian users of Linux. Could you please give an example of another layout that achieves the work of the patch that Michael produced (but using the rules/* files, as you mention above)?
> 1. I am not sure if Austria uses all 4 variants I proposed, because I've never > worked with Linux on a Sun or Mac. All I can say is that those variants exist > in Switzerland and Germany, so the probability is high that those also exist in > Austria, in which case they would be identical to the German layout. Fair enough. > 2. I'd like to do that, however, I haven't found out how to adapt the rules > files. Could you point me to documentation or other instructions? Which file(s) > do I have to modify? Actually, on the 2nd thought, since I would like to have the proper group name, your idea with symbols/at looks just right. > 3. Yes, I will make a patch for the latest git version as soon as I have > adapted the rules files. Cool!
Created attachment 38451 [details] [review] Patch for Austrian layout in base.xml.in This should work in combination with the new symbols/at file. I could also provide the required new translation entries for the German po file.
Great! Committed now. I added the missing bit for symbols/Makefile.am:)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.