action #31585
Updated by JERiveraMoya almost 7 years ago
Regarding how could be implemented in future a full installation in another languages I was playing around and researching a bit. This is what I found:
+ I was able to change qumu language adding after https://github.com/os-autoinst/os-autoinst/blob/master/backend/qemu.pm#L570:
<blockquote>
`gen_params @params, 'k', $vars->{QEMULANGUAGE} if $vars->{QEMULANGUAGE};
</blockquote>
`
+ Our bootloader.pm has a working subroutine select_bootmenu_language that allows to change the language, but should be called the first and not the last due to we need to first change the language to type the bootloader parameters.
--> It works but VNC is in the middle and keys that needs modifier keys (shift, alt, control, etc) does not return the right result (as I could check returns the right key in the corresponding language without using shift for example).
--> How is done in autoinst?: There is a specific mapping https://github.com/os-autoinst/os-autoinst/blob/master/consoles/VNC.pm#L634 https://github.com/os-autoinst/os-autoinst/blob/master/consoles/VNC.pm#L670
+ On the other hand, we might not want to change the language in the bootloader, but once the qemu is configured with -k we need to do it because it starts to convert from the very beginning.
I found specially interesting this article recommended in the qemu documentation https://wiki.archlinux.org/index.php/QEMU: https://www.berrange.com/posts/2010/07/04/more-than-you-or-i-ever-wanted-to-know-about-virtual-keyboard-handling/ which doesn't recommend to use -k parameter in the same way that many other sources neither do.