Ticket #1681 (new defect)

Opened 2 years ago

definition environment in a module becomes omtext instead of definition

Reported by: uholzer Owned by: deyan
Priority: normal Milestone:
Component: STeX/ltxml Version: trunk
Severity: major Keywords:
Cc: Blocked By:
Blocking: Due to close: YYYY/MM/DD
Include in GanttChart: no Dependencies:
Due to assign: YYYY/MM/DD

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.

Attachments

functions.tex Download (482 bytes) - added by uholzer 2 years ago.
functions.omdoc Download (5.5 KB) - added by uholzer 2 years ago.

Change History

Changed 2 years ago by uholzer

Changed 2 years ago by uholzer

Note: See TracTickets for help on using tickets.