{5} Assigned, Active Tickets by Owner (Full Description) (34 matches)

We use \LXMRef for structre sharing, it is used in dmath/en/nat-basic.tex as $\LXMID{four-unary}{...}$ (the definition of four-unary and (later) as $\LXMRef{four-unary}$ (the reference). latexml still seems to do the right thing: <XMRef idref="four-unary"/>, but latexmlpost transforms this to <om:OMSTR/>, where it should be <om:OMR href="four-unary"/>. BTW, I am not sure where this information should reside and where the empty OMSTR comes from.

We had the declaration functions=s in the optional arguments of statements, so that we could write s(x) and have that be interpreted as the function s applied to the argument x. This does not seem to work any more; for example in stc/sissi/winograd/cds/linearextrapolation.tex.

We should push for getting the changes in our branch into the LaTeXML trunk, or have our own packages. Distribution of LaTeXML seems to be moving into the direction of packages.

A good first step for this would be detailing what the differences are, and what the consequences of using the normal distribution would be.

This issue is really a spin-off from #1552.

In dcm.sty.ltxml, the constructor for \DCMPerson does not generate output. This is OK, when read in the document preamble, which is the only way it is used currently. But the situation is more complex: there are two situations.

when \DCMperson is encountered outside the preamble, then it is used as a specification of information about the person. In this case, it should generate FOAF information. For instance,

\DCMperson[id=miko,affiliation={Jacobs University, Bremen},
           url=http://kwarc.info/kohlhase]{Michael Kohlhase}

should generate - well what should it generate? @CL, could you comment? I guess it should generate OMDoc symbols for the FOAF information, in our example (sorry I forget the FOAF theory in OMDoc, so I am guessing here)

<symbol name="miko"/>
<axiom>
  <FMP>
    <OMA><OMS cd="foaf" name="urlof"/>
      <OMS cd="???" name="miko"/>
      <OMSTR>http://kwarc.info/kohlhase</OMSTR>
   </OMA>
  </FMP>
</axiom>
...

Or should we generate RDF triples directly? Or maybe RDFa-annotated OMDoc; I am not sure.

when \DCMPerson is encountered in the preamble, then it should update an internal dictionaly, so that it can be used to generate metadata references to the FOAF information. For instance, if we encounter a

\begin{omgroup}[creators=miko]{the title}

then this should generate

<omgroup>
  <metadata>
    <link rel="dc:creator" resource="KWARCstaff??miko"/>
  </metadata>
  ...

using a MMT URI in the metadata.

OK, these are still very first ideas of what should really happen here. I guess the first step would be to specify what we would really like, so I am assigning this to CL for the moment. When things are fully specified, we can re-assign to DG.

We should find a way to export the \symdef source to the notation definitions for the symdef lookup service envisioned at  https://trac.mathweb.org/planetary/ticket/117.

The way I see this is to add additional formats to the generated notation definitions. For example I would like to see

\symdef{powerset}[1]{\prefix{P}{#1}} 

to

    <notation cd="sets-operations" name="powerset" xml:id="powerset.symdef">
      <prototype>
        <om:OMA>
          <om:OMS cd="sets-operations" cr="fun" name="powerset"/>
          <expr name="arg1"/>
        </om:OMA>
      </prototype>
      <rendering>
        <m:mrow>
          <m:mo cr="fun">P</m:mo>
          <m:mrow>
            <m:mo fence="true">(</m:mo>
            <render name="arg1" precedence="-1000000"/>
            <m:mo fence="true">)</m:mo>
          </m:mrow>
        </m:mrow>
      </rendering>
      <rendering format="LaTeX">
       <text>P(</text>
       <render name="arg1" precedence="-1000000"/>
       </text>)</text>
      </rendering>
      <rendering format="sTeX">
       <text>\prefix{P}{</text>
       <render name="arg1"/>
       </text>}</text>
      </rendering>
    </notation>
    <private reformulates="#powerset.symdef">
      <data format="sTeX">\symdef{powerset}[1]{\prefix{P}{#1}}</data>
    </private>

I have to think some more about the <rendering format="LaTeX">, which does not deal with precedences at the moment. It is also less important (I guess).

For arxmliv we have the service  http://tex2xml.kwarc.info/. It should be simple to supply a variant of this for sTeX, so that people can use sTeX without having to install it. We will just need a local checkout of sTeX repository that is kept up to date automatically.

this is needed for elision. This is in presentation.dtx.

In #1437 we have implemented beamer-style overlay specifiers for itemize,... and also the \only macro. But that is treated incorrectly.

\only is different from \item; it can be used everywhere. It takes an overlay specifier like \item, but just putting

Let('\only'=>'\beamer@group@item');

treats it like an \item. But it should not.

BTW there is an environment onlyenv that is the block-type analogon.

Currently, sTeX aims to generate content representations (OpenMath?) from LaTeX formulae exclusively. This is bad for a migration format, where we may not have enough semantic macros. In particular, in OMDoc2, we want to allow the interleaving of content and presentation (and parallel markup) arbitrarily, so we should start thinking about this in the sTeX context as well.

This issue should serve as discussion container on this issue.

Just re-reporting this, so we don't forget:

Sometimes, a spurious vspace is inserted below a task environment. Apparently this happens whenever there is some cross-reference (ref or cite) close to the end of a text line that fills the whole text width.

this is a torso. Or leave it out of the sTeX submission to CTAN.

Thanks for fixing the previous bugs with statements and sref, it works now. Except for one stylistic issue: I don't like the item type a reference points to to be capitalized (as in: see Definition 1.1). I know that many people do it, but I don't like it, and I have done a little bit of research on it:  You don't have to do it, in fact there are well-reputed sources saying that you should not do it. Of course except for situations when you have to capitalize anyway.

I could imagine two solutions:

1. create a variant of sref that behaves like ref, i.e. only generates the number. Then the author has full control.
2. introduce an option that allows for controlling capitalization, or something like the current optional argument \sref[label]{key} but which does not affect the whole link but only the part of the label that precedes the number.

I'd prefer having (1) in any case. (2) would additionally be nice to have.

At least when referencing statements, there is a workaround to achieve (1):

\begin{definition}[id=def:foo]
  \label{def:foo}
  ...
\end{definition}

From definition~\ref{def:foo} ...

But it forces you to insert a redundant label.

both in the documentation, and the changes and ... and reinstate the checksums

There is currently no documentation of application and binding uses of \symdef in modules.dtx. This is needed together with some examples. In particular, the new keys for \symdef are completely undocumented.

The latest issue of the TeXnische? Komödie (DANTE magazine) made me aware of other existing packages for exams/exercises. Maybe they have some interesting features that could be adopted for sTeX:

•  eqexam
•  uebungsblatt

In my document collection the term "laserscanner" is used a lot and I want to formalize its occurrences. The definition of a laserscanner is not explicitly given anywhere in the collection, so I have no definition to reference.

The problem of referencing implicit knowledge appears quite frequently. Therefore, I like an option "display=none" when creating a definition: one that is invisible in the generated pdf but visible in the generated OMDoc.

Some proposal sections have upper page limits. Would it be possible to represent these sections by

\begin{typeofsection}
...
\end{typeofsection}

and check at the end how many pages we are away from the beginning?