Ticket #1681 (new defect)
Opened 2 years ago
definition environment in a module becomes omtext instead of definition
Description
All my definition environments become omdoc:omtext elements instead of omdoc:definition elements even though they are inside a module element.
I attach a testcase.
This seems to be highly related to #1598.
I have tried to debug this problem myself: In the sub definitionBody in statements.sty.ltxml the call LookupValue('current_module') always returns null. I have no clue what exactly is going on in the definition of the environment module in modules.sty.ltxml. (Why is it enough assigning only parent_module in afterDigest? What does activateScope do? Why gets parent_module the same value as current_module?) Even worse, I made a small testcase and added a command that just puts the value of LookupValue('current_module') into the omdoc document and there it gives always the correct values.

