[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [virt-tools-list] [libosinfo 1/2] install-config: Document expected kbd layout format



On Fri, Nov 30, 2012 at 11:37 AM, Christophe Fergeau
<cfergeau redhat com> wrote:
> On Fri, Nov 30, 2012 at 03:00:47AM +0200, Zeeshan Ali (Khattak) wrote:
>> From: "Zeeshan Ali (Khattak)" <zeeshanak gnome org>
>>
>> ---
>>  osinfo/osinfo_install_config.c | 14 +++++++++++++-
>>  1 file changed, 13 insertions(+), 1 deletion(-)
>>
>> diff --git a/osinfo/osinfo_install_config.c b/osinfo/osinfo_install_config.c
>> index adbf9df..e7a8946 100644
>> --- a/osinfo/osinfo_install_config.c
>> +++ b/osinfo/osinfo_install_config.c
>> @@ -124,7 +124,19 @@ const gchar *osinfo_install_config_get_hardware_arch(OsinfoInstallConfig *config
>>                                           OSINFO_INSTALL_CONFIG_PROP_HARDWARE_ARCH);
>>  }
>>
>> -
>> +/**
>> + * osinfo_install_config_set_l10n_keyboard:
>> + *
>> + * Sets the #OSINFO_INSTALL_CONFIG_PROP_L10N_KEYBOARD parameter.
>> + *
>> + * The expected format of this string is an X Window System keyboard layout
>> + * specifier:
>> + *
>> + * http://www.freedesktop.org/wiki/Software/XKeyboardConfig
>> + * http://fedoraproject.org/wiki/Anaconda/Kickstart#keyboard
>
> None of these links are really helpful to figure out what the format looks
> like.

Thats the best I could find. If you could help me find better
references, I'll be grateful.

>This API seems to be very fedora-specific,

The format is more like Linux specific but yeah, currently we only
need this for Fedora and 'keyboard' command is required in the
kickstart.

> the way it works on win7
> is described there:
> http://technet.microsoft.com/fr-fr/library/cc749191%28v=ws.10%29.aspx
> though I did not quite get the format of keyboard layouts
>
>  void osinfo_install_config_set_l10n_keyboard(OsinfoInstallConfig *config,
>                                               const gchar *locale,
>                                               const gchar *keyboard_layout);
> will probably be more flexible. 'locale' would be in the same 'gettext'
> format as in other places. Not sure at all what the format of
> keyboard_layout should be, just that it can be NULL to use the default
> keyboard layout (which is what we'll want most of the time).

IMO for now we shouldn't set the keyboard layout for windows since its
autodeteced (right?) from the language params that we do set. We also
have the API for apps to know if a param is used by a script or not
and if it is used, if its mandatory.

If we decide to do so in future, we could either figure a way to
translate from X layouts to locale names or add new param/API to
set/get locale and declare in windows scripts that they make use of
this param.

-- 
Regards,

Zeeshan Ali (Khattak)
FSF member#5124


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]