diff --git a/source/text/sbasic/python/python_handler.xhp b/source/text/sbasic/python/python_handler.xhp
index 1f9e9ce354..87887105e3 100644
--- a/source/text/sbasic/python/python_handler.xhp
+++ b/source/text/sbasic/python/python_handler.xhp
@@ -23,6 +23,7 @@
          <bookmark_value>API;DialogProvider2</bookmark_value>
          <bookmark_value>API;XDialogEventHandler</bookmark_value>
       </bookmark>
+      <bookmark xml-lang="en-US" branch="hid/cui/ui/assigncomponentdialog/AssignComponent" id="bm_id66701251" localize="false"/>
       <h1 id="N0665"><variable id="pythonhandler_h1"><link href="text/sbasic/python/python_handler.xhp" name="Creating a Dialog Handler">Creating a Dialog Handler</link></variable></h1>
       <paragraph role="paragraph" id="N0666">Next to <link href="text/sbasic/shared/01040000.xhp" name ="Assigning macros to events">assigning macros to events</link> or <link href="text/sbasic/basic/python/python_listener" name ="creating event listeners">creating event listeners</link>, one can use dialog handlers, whose principle is to define UNO keywords, or methods, that are mapped to events to watch for. The event handler is responsible for executing methods using the <literal>vnd.sun.star.UNO:&lt;method_name&gt;</literal> protocol. Unlike listeners that require to define all supported methods, even if unused, dialog handlers require only two methods on top of intended control hook scripts.</paragraph>
       <paragraph role="paragraph" id="N0667">The advantages of this approach are:</paragraph>