# Ticket #1552 (assigned defect)

Opened 3 years ago

## dc:creator text mangled

Reported by: Owned by: kohlhase deyan normal dfgproposal Future STeX/ltxml trunk major YYYY/MM/DD no YYYY/MM/DD

### Description

in dcm.sty.ltxml we have a facility that reads the information from DCMpeople.tex and generats <dc:creator>...</dc:creator>. Eventually, this should generate FOAF metadata (see also #1531, but for the moment it should not delete spaces). See  https://svn.kwarc.info/repos/stex-content/problems/SML/en/huffman.omdoc for an example.

## Change History

### Changed 3 years ago by deyan

• status changed from new to assigned

This error was due to the "inPreamble" state marker being set to 1, instead of 0. It is quite peculiar, since we explicitly set "inPreamble" to 0 at omdoc.cls.ltxml for the entire document. Apparently something is reseting the value and should be found and corrected.

There is a separate issue with \DCMperson, regarding the proper digestion of the names given as primary arguments. Currently, the digestion does not in any way transform the given argument and there is no obvious reason why that is the case.

I am looking further into this, the whitespace fix is already committed.

### Changed 3 years ago by kohlhase

having inPreamble being true sounds right for this, since DCMPersons is loaded in the preamble. Did you take this into account?

### Changed 3 years ago by deyan

Yes I did. I actually had to investigate for quite some time, since the problem was due to a special behavior at LaTeXML's Stomach.

Currently, LaTeXML assumes that whenever digestion occurs and "inPreamble" is true all whitespace is to be treated like in math mode, i.e. omitted from output. I presume this is TeX motivated, since you don't want to typeset anything to output when in the preamble, but I am just guessing.

I presume this is exactly the reason "inPreamble" is set to false at the \begin{document} binding in omdoc.cls.ltxml. However, there are other LaTeXML internals that could flip the "onPreamble" switch, so I am hunting those down and figuring out which one is the culprit here.

### Changed 3 years ago by kohlhase

Just for perspective, I have specified what we would really like to see in the future in #1553. But I guess that we have to understand what goes on here as well.

Note: See TracTickets for help on using tickets.