In admin/config/regional/language/list we have the language labels be presented using both the native and the non-native form of the language:

In places like the user account edit form however, we output only the native label:

...and in the "Add language" form (in admin/config/regional/language/add), the dropdown select uses the non-native version:

This is because the function language_list() accepts an optional boolean $native_names parameter, which outputs the labels either in the non-native/English version (default behaviour), or in their native version (if $native_names is passed as TRUE to the function).
I would like us to consistently be outputting both versions of the language labels everywhere, and I also believe that the default should be that (like in the language listing page). Since that would constitute a backwards compatibility breaking change though, I would like us to at least figure out a way to allow output of both native and non-native labels in the #options array (if the optional $option_list parameter is set to TRUE), and see if we can do that in the 1.x cycle, keeping backwards compatibility and the output of the function otherwise unchanged if possible.
Recent comments
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists