1. I didn't do other extra operations, I clicked on export, then immediately click on import, then it appears this error, and the two errors are different, I don't know what else to pay attention to, could it be because I use the Chinese system to cause it,Also attached is a video of me in action.
2. I've also found that creating a new keymap and selecting it also causes a bug!

我没有做其它多余的操作,我点击导出之后,立刻点击导入,然后它就出现了这样的报错,而且两个报错还不同,我也不知道还有其它什么地方注意的,会不会是因为我使用的中文系统导致的呢,另外附上我操作的视频
我还发现一个问题,就是新建一个 keymap 选择它也会出现BUG

@EMM (IMBI) Unfortunately the video in your last comment doesn't play for me. If you could re-upload it, that would be very helpful.

Just to avoid any misunderstandings, is it correct that you're doing the following steps?

1. Open Blender
2. Open the keymap user preferences Edit > Preferences > Keymap
3. Select a keymap and then press Export (First error appears on export)
4. Click on Import, select the previously exported file (Second error appears)

Was the first keymap that resulted in the export/import error created by editing one of the built-in keymaps through Edit > Preferences > Keymap? Is the EMM.py or .py (from your original report) the keymap what you get after exporting and you're trying to import this file again? Is keymap.py what you get after attempting to import EMM.py or .py?

I don't know what the "Blender-PME" addon is, but you use non-English names in it, I think so.

It could be something like this rBA86c4ca71ef18: Fix T76736: incorrect filename in SVG, fails to load elsewhere.

("wm.pme_user_pie_menu_call",
 {"type": 'SPACE', "value": 'PRESS'},
 {"properties":
  [("pie_menu_name", '±à¼­Ä£Ê½-Íø¸ñÊý¾Ý'),
   ("invoke_mode", 'HOTKEY'),
   ("keymap", '3D View'),
   ],
  },
 ),

In T82292#1045707, @Yevgeny Makarov (jenkm) wrote:

I don't know what the "Blender-PME" addon is, but you use non-English names in it, I think so.

Yes, I'm using a PIE plugin, it can use custom UI.
Its forum address is this:https://blenderartists.org/t/pie-menu-editor-1-18-0/662456/3680

是的,我正在使用一个PIE插件,它能使用自定义UI.是这个原因吗
它的论坛地址是这个:https://blenderartists.org/t/pie-menu-editor-1-18-0/662456/3680

I can reproduce the import error by attempting to import EMM.py. This is caused by the pie menu entries as @Yevgeny Makarov (jenkm) said and as I've noted in my first comment the encoding for these characters is not in UTF-8 but seem to be GB2312. It appears that the Blender-PME add-on doesn't handled encoding properly and stores non UTF-8 characters in the keymap. We can't provide support for the paid third-party add-on, however Blender shouldn't let an add-on store invalid characters in the keymap either.

I'll try to reproduce this issue through the Python API.

Edit: It's Blender's fault.

@EMM (IMBI) As a workaround I've edited the EMM.py file which can now be imported. The Chinese characters have been replaced with the (poorly machine translated) English words and it's been saved with UTF-8 encoding.

Thank you, the file you sent can be imported, thank you very much, in addition to this bug I have feedback to the plug-in developers there, should be resolved!
谢谢您,您发的文件可以导入了,十分感谢,另外这个BUG我已经反馈到插件开发者那里了,应该会得到解决

I've tried to intentionally break the keymap through the Python API, but haven't been successful so far. Will continue to investigate.

It seems that the problem is caused when an operator has a string property, there is a shortcut registered for it in the keymap and the shortcut uses a value for the operators string property that is not UTF-8 encoded. However, I can't get a keymap to export after assigning e.g. Chinese characters to the property in the keymap preferences. It gives the following exception:

location: <unknown location>:-1
Traceback (most recent call last):
  File "Z:\02_software\blender-2.81a-windows64\2.81\scripts\startup\bl_operators\userpref.py", line 259, in execute
    all_keymaps=self.all,
  File "Z:\02_software\blender-2.81a-windows64\2.81\scripts\modules\bl_keymap_utils\io.py", line 194, in keyconfig_export_as_data
    fw(kmi_data)
  File "Z:\02_software\blender-2.81a-windows64\2.81\python\lib\encodings\cp1252.py", line 19, in encode
    return codecs.charmap_encode(input,self.errors,encoding_table)[0]
UnicodeEncodeError: 'charmap' codec can't encode characters in position 37-38: character maps to <undefined>

As of now I cannot reproduce the exact error from the original bug report with my current system configuration, but I have an idea. Since the error references cp1252.py Blender always seems to be using the system locale to determine the encoding. Reproducing the exact error from the original report may be possible with a different system locale configuration, which then presumably fails to import it later on. I would guess that in order to reproduce this bug you would have to set Windows' system locale to Simplified Chinese, which then results in code page 936 being used. This would then have GB2312 encoding applied to the input, which is what I've seen in the keymap included in the bug report.

If anyone wants to test this and investigate further, below is a script that implements a simple operator which is added to the keymap when registered.

I think I found the issue. The code page error in my last comment means that Blender isn't using UTF-8 for the export on my system either. The function keyconfig_export_as_data that writes the keymap doesn't set the encoding to UTF-8. The encoding should be explicitly set in Python's open() function.

Currently:

with open(filepath, "w") as fh:

Possible fix:

with open(filepath, "w", encoding="utf-8") as fh:

Edit: @Yevgeny Makarov (jenkm) was spot on with his comment.

@Robert Guetzkow (rjg)

In T82292#1045707, @Yevgeny Makarov (jenkm) wrote:

It could be something like this rBA86c4ca71ef18: Fix T76736: incorrect filename in SVG, fails to load elsewhere.

:)

@Yevgeny Makarov (jenkm) Yes, I know. Would've found/verified the problem quicker if I checked keyconfig_export_as_data or grepped open( first, instead of attempting to reproduce the reported error condition.