Activity for Jan Schlamelcher

  • Jan Schlamelcher Jan Schlamelcher modified a comment on ticket #12

    Commit #9ae8779d63e4cc646 introduces anchors to all the respective elements in the generated HTML output. For table content, this is realized using the HTML <a> element and for section content (e.g. a VMD), this is realized using the respective <hX> element's "id" attribute as it works for classic HTML. The former is already supported by the external ieee-converter, the latter isn't. I've also prepared the attached patch for the ieee-converter to implement <hX id=""> based anchors that I will also...

  • Jan Schlamelcher Jan Schlamelcher modified a comment on ticket #12

    Commit #9ae8779d63e4cc646 introduces anchors to all the respective elements in the generated HTML output. For table content, this is realized using the HTML element and for section content (e.g. a VMD), this is realized using the respective <hX> element's "id" attribute as it works for classic HTML. The former is already supported by the external ieee-converter, the latter isn't. I've also prepared the attached patch for the ieee-converter to implement <hX id=""> based anchors that I will also provide...

  • Jan Schlamelcher Jan Schlamelcher modified a comment on ticket #12

    Commit #9ae8779d63e4cc646 introduces anchors to all the respective elements in the generated HTML output. For table content, this is realized using the HTML element and for section content (e.g. a VMD), this is realized using the respective <hX> element's "id" attribute as it works for classic HTML. The former is already supported by the external ieee-converter, the latter isn't. I've also prepared the attached patch for the ieee-converter to implement <hX id=""> based anchors that I will also provide...

  • Jan Schlamelcher Jan Schlamelcher modified ticket #12

    Need to Resolve Nomenclature Reference in Text

  • Jan Schlamelcher Jan Schlamelcher posted a comment on ticket #12

    Commit #9ae8779d63e4cc646 introduces anchors to all the respective elements in the generated HTML output. For table content, this is realized using the HTML element and for section content (e.g. a VMD), this is realized using the respective <hx> element's "id" attribute as it works for classic HTML. The former is already supported by the external ieee-converter, the latter isn't. I've also prepared the attached patch for the ieee-converter to implement <hx id=""> based anchors that I will also provide...

  • Jan Schlamelcher Jan Schlamelcher posted a comment on ticket #10

    Closed by commit #19bcb6b68867d181c.

  • Jan Schlamelcher Jan Schlamelcher modified ticket #10

    Separation of structure and content in output documents

  • Jan Schlamelcher Jan Schlamelcher modified ticket #11

    Rendering of Alert System Information in HTML Output

  • Jan Schlamelcher Jan Schlamelcher posted a comment on ticket #11

    Your assumption was exactly right, Martin. The code only handled the general alert system properties and than traversed into alert group specific code, ignoring any alert conditions defined directly below the alert system element. Commit #ef9197fa600bd71099 fixes the issue by moving the code for generating alert condition tables into a separate function an then calling this function for both the alert system and any alert group elements below it. I believe we are probably not mixing alert systems...

  • Jan Schlamelcher Jan Schlamelcher modified ticket #7

    ProductionSpecifications in HTML

  • Jan Schlamelcher Jan Schlamelcher posted a comment on ticket #7

    Finally fixed by commit #82a3ca367383f4ba.

  • Jan Schlamelcher Jan Schlamelcher modified ticket #7

    ProductionSpecifications in HTML

  • Jan Schlamelcher Jan Schlamelcher posted a comment on ticket #7

    Commit ebdcbf74cfc52b65d06 introduces initial support for this, please review the results and provide feedback as required.

  • Jan Schlamelcher Jan Schlamelcher modified ticket #8

    Table-Prefixes seem to have limited syntax

  • Jan Schlamelcher Jan Schlamelcher posted a comment on ticket #8

    Fixed by commit 84c851d17a97be3.

  • Jan Schlamelcher Jan Schlamelcher posted a comment on ticket #7

    To ask a stupid question: where shall they go? Is this a subsection under all the levels? A table column? I'm not sure where to place the output and what exactly the output shall be: the common name and description from the referenced term in the nomenclature?

  • Jan Schlamelcher Jan Schlamelcher modified ticket #9

    Quotations are not displayed in HTML output

  • Jan Schlamelcher Jan Schlamelcher posted a comment on ticket #9

    Fixed by commit 156a08b96b959d.

  • Jan Schlamelcher Jan Schlamelcher created ticket #37

    Image Documentation needs introductory text

  • Jan Schlamelcher Jan Schlamelcher created ticket #4

    Handle TODO: descriptive text

  • Jan Schlamelcher Jan Schlamelcher created ticket #8

    Metric Accuracy Considerations

1
MongoDB Logo MongoDB
Gen AI apps are built with MongoDB Atlas
Atlas offers built-in vector search and global availability across 125+ regions. Start building AI apps faster, all in one place.