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

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

deyan (10 matches)

Ticket Summary Component Milestone Type Created
Description
#1376 bin/sms must also extract LXMID tools sTeX 1.0 release defect 09/09/07

for something like $[junk]\LXMID{foo}{bar}[junk]$ in XXX.tex it should extract $\LXMID{foo}{bar}$ to XXX.sms.

When this is done, we can re-share the LXM{unary-???} in slides/dmath/en


#1395 \LXMRef does not work any more STeX/ltxml sTeX 1.0 release defect 09/16/08

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.


#1604 binding on the last variable does not seem to work. STeX/ltxml GenCS2013 defect 07/13/10

In missing/en/highschool.tex we see

  \symdef[bvars=4]{definiteintegral}[4]{\int^{#1}_{#2}#3 d#4}

which is converted to

    <prototype>
        <om:OMBIND>
          <om:OMS cd="highschool" cr="fun" name="definiteintegral"/>
          <expr name="arg1"/>
          <expr name="arg2"/>
          <expr name="arg3"/>
          <om:OMBVAR>
            <exprlist name="args">
              <expr name="arg"/>
            </exprlist>
          </om:OMBVAR>
        </om:OMBIND>
      </prototype>

But in OM, bound variables should always be the second child. We would like to see the prototype

        <om:OMBIND>
          <om:OMS cd="highschool" cr="fun" name="definiteintegral"/>
          <expr name="arg1"/>
          <om:OMBVAR>
            <exprlist name="args">
              <expr name="arg"/>
            </exprlist>
          </om:OMBVAR>
         <expr name="arg2"/>
         <expr name="arg3"/>
        </om:OMBIND>

Actually, this is not correct either, since we want to put the bounds into an interval, but this is a more difficult problem I will have to think about. But the right order of OMBVAR is needed in any case.


#1403 LXMRef across files STeX/ltxml sTeX 1.0 release defect 10/06/08

one of the things the broke with the new make systems is that LXMref breaks. Now we have only one theory per file, we cannot just use a id/idref method. So we have to record the current theory in an LXMId and use that for reference in LXMRef. The main problem is that

I am not sure how this should go in detail and what the general mechanism should be. But I will develop this here.


#1480 get the sTeX branch changes into the LaTeXML trunk STeX/ltxml sTeX 1.0 release defect 12/06/09

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.


#1553 Genetate FOAF from DCMPerson STeX/ltxml sTeX 1.0 release defect 04/21/10

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.


#1644 tikz.sty.ltxml should define \tikzstyle STeX/ltxml sTeX 1.0 release defect 10/01/10

it is needed in swim/en/swim-nutshell.tex


#1665 export \symdef source to OMDoc STeX/ltxml defect 11/18/10

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).


#1444 build stex2omdoc web service STeX/ltxml GenCS2013 enhancement 08/14/09

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.


#1622 extend \tableofcontents by @level STeX/ltxml GenCS2013 defect 08/23/10

The OMDoc <tableofcontents> element (now) defined in omdoc.dtx needs a @level attribute, which is filled from the toclevel counter, this needs to be implemented in omdoc.sty.ltxml.


kohlhase (18 matches)

Ticket Summary Component Milestone Type Created
Description
#1384 implement \elide in LaTeXML STeX/ltxml sTeX 1.0 release defect 07/02/08

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


#1648 think about the notation environment and notatiendum macro. STeX/sty sTeX 1.0 release defect 10/03/10

these two are currently relatively ad-hoc, and their relation to the symdef process should be better understood. In particular, there is no clear indication on how \notatiendum should be used (and conflicting documentation and examples in statements.dtx.

All of this needs to be understood and cleaned up.

There is also an issue with markup practice: \symdef macros need to be done in the running text; probably best in notation or definition environments to have more locality.


#1634 beamer-style \only not treated correctly in mikoslides.dtx STeX/ltxml GenCS2013 defect 09/20/10

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.


#1707 Support top-level article classification metadata in sTeX STeX/ltxml sTeX 1.0 release enhancement 04/29/11

What we need specifically (for the EPC): ACM classification of the articles in the Planetary documentation/help book.

What that means in general: OMDoc-style RDFa annotation support in sTeX (what we had actually promised for I-Semantics 2010).


#1765 interleave presentation and content formulae STeX/ltxml GenCS2013 Question 05/15/13

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.


#1426 weird interaction the omgroup environment with Beamer/mikoslides STeX/sty sTeX 1.0 release defect 06/27/09

The omgroup environment generates harmless errors

(\end occurred when \ifx on line 45 was incomplete)

when used in with the mikoslides.cls with slides option. It seems to work when used with the notes option, and it also works with article.sty. So I think that this is a beamer issue.

The errors can be suppressed by adding a spurious \fi at the end of \begin{omgroup} code, but this leads to problems in article.cls of course.


#1466 need \snumref and \spageref in sref package STeX/sty sTeX 1.0 release defect 09/29/09

The \sref macro insists to give the class of the reference, e.g. "Section 2.1". So we need a variant \snumref that only generates the reference "2.1".

Furthermore it would be good to have an analogon to \pageref in sref.

And finally, I would like to have a \stref that also provides the title of the referenced object.


#1486 completely rework physml.dtx STeX/sty sTeX 1.0 release defect 12/14/09

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


#1505 need \importqualified in modules package STeX/ltxml sTeX 1.0 release defect 01/13/10

In an earlier version of the modules package we used the usesqualified key on the module environment for importing macros with a disambiguating prefix (this is used whenever we have conflicting names for macros inherited from different modules). This is not accessible from the current interface. We need something like a importqualified macro for this.

We need to specify the importqualified interface, implement it in LaTeX and then do the LaTeXML equivalent.


#1507 Item type always capitalized in sref? STeX/sty sTeX 1.0 release defect 01/13/10

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.


#1532 create a new stable branch for sTeX1.0 and announce it widely General sTeX 1.0 release defect 02/11/10

announcement targets:

OMDoc list MKM list are there TeX lists?


#1533 bump the version numbers in sTeX packages to 1.0 Documentation sTeX 1.0 release defect 02/11/10

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


#1597 \href not defined in \documentclasss[notes]{mikoslides} STeX/sty sTeX 1.0 release defect 07/01/10

\href is not defined in \documentclass[notes]{mikoslides} , but it is defined when using \documentclass[slides]{mikoslides} . If I have a fragment, and I write make fragment.pdf there are different errors and the pdf file is not produced, unless it is changed to [slides].

The fragment with which I was working was stats/fragments/statisticalconcepts.tex . Deyan has changed locally the pre.tex to use \documentclasss[slides]{mikoslides} so that I can produce the pdf


#1750 document application and binder uses of \symdef Documentation GenCS2013 defect 08/30/12

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.


#1500 Consider features of other exam/exercises document classes STeX/sty sTeX 1.0 release enhancement 01/09/10

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:


#1531 sTeX support for flexible metadata (MOLE) STeX/ltxml sTeX 1.0 release enhancement 02/11/10

We have published the idea that we can use OMDoc (and thus sTeX) for ontologies. In the Flexiform paper and the FormalSafe? case study we describe sTeX as a vocabulary specification language writing OMDoc1.3 flexible metadata annotations conveniently. Right now, we can only do this by writing custom *.sty and *.ltxml files for external packages.

It should be possible to internalize this into sTeX, just as \symdef internalizes the creation of semantic symbol macros into sTeX and \termdef for semantic concept macros.

This would allow us to bring sTeX light to a whole new level.


#1609 Dealing with implicit knowledge in documents STeX/ltxml enhancement 08/09/10

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.


#1658 allow to configure the proof labeling system in sproof STeX/sty sTeX 1.0 release enhancement 11/06/10

We should make the labeling system used for proof steps configurable. The current one is very intrusive.


Note: See TracReports for help on using and creating reports.