home.social

#dhconvalidator — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dhconvalidator, aggregated by home.social.

  1. Thanks for flagging this. Could you send the error details (and ideally your test ODT) to [email protected]? We'll take a look on our end and also raise the #DHConvalidator issue with @adho

  2. Thanks for flagging this. Could you send the error details (and ideally your test ODT) to [email protected]? We'll take a look on our end and also raise the #DHConvalidator issue with @adho

  3. Thanks for flagging this. Could you send the error details (and ideally your test ODT) to [email protected]? We'll take a look on our end and also raise the #DHConvalidator issue with @adho

  4. Thanks for flagging this. Could you send the error details (and ideally your test ODT) to [email protected]? We'll take a look on our end and also raise the #DHConvalidator issue with @adho

  5. Thanks for flagging this. Could you send the error details (and ideally your test ODT) to [email protected]? We'll take a look on our end and also raise the #DHConvalidator issue with @adho

  6. @dh2026daejeon @adho I am down to running a test suite through the #DHConvalidator. Submitting ODT with multiple paragraphs of Lorem Ipsum in the “DH-Default” style results in a conversion error claiming that not a single of the required children of `tei:body` is present, among them `tei:p`. Why?

  7. @dh2026daejeon @adho I am down to running a test suite through the #DHConvalidator. Submitting ODT with multiple paragraphs of Lorem Ipsum in the “DH-Default” style results in a conversion error claiming that not a single of the required children of `tei:body` is present, among them `tei:p`. Why?

  8. @dh2026daejeon @adho I am down to running a test suite through the #DHConvalidator. Submitting ODT with multiple paragraphs of Lorem Ipsum in the “DH-Default” style results in a conversion error claiming that not a single of the required children of `tei:body` is present, among them `tei:p`. Why?

  9. @dh2026daejeon @adho I am down to running a test suite through the #DHConvalidator. Submitting ODT with multiple paragraphs of Lorem Ipsum in the “DH-Default” style results in a conversion error claiming that not a single of the required children of `tei:body` is present, among them `tei:p`. Why?

  10. @dh2026daejeon @adho I am down to running a test suite through the #DHConvalidator. Submitting ODT with multiple paragraphs of Lorem Ipsum in the “DH-Default” style results in a conversion error claiming that not a single of the required children of `tei:body` is present, among them `tei:p`. Why?

  11. The #DHConvalidator makes me want to kill myself. Again! The .odt templates generate endless errors and the .docx templates return only partial content on success! Any idea, @dh2026daejeon , @adho ?

    #DH2026 #DigitalHumanities #fail

  12. The #DHConvalidator makes me want to kill myself. Again! The .odt templates generate endless errors and the .docx templates return only partial content on success! Any idea, @dh2026daejeon , @adho ?

    #DH2026 #DigitalHumanities #fail

  13. The #DHConvalidator makes me want to kill myself. Again! The .odt templates generate endless errors and the .docx templates return only partial content on success! Any idea, @dh2026daejeon , @adho ?

    #DH2026 #DigitalHumanities #fail

  14. The #DHConvalidator makes me want to kill myself. Again! The .odt templates generate endless errors and the .docx templates return only partial content on success! Any idea, @dh2026daejeon , @adho ?

    #DH2026 #DigitalHumanities #fail

  15. The #DHConvalidator makes me want to kill myself. Again! The .odt templates generate endless errors and the .docx templates return only partial content on success! Any idea, @dh2026daejeon , @adho ?

    #DH2026 #DigitalHumanities #fail

  16. What happened to the #DHConvalidator and #TEI? I am about to submit proposals for #DH2026 and it appears that submissions must not conform to any specific style or tooling.

  17. What happened to the #DHConvalidator and #TEI? I am about to submit proposals for #DH2026 and it appears that submissions must not conform to any specific style or tooling.

  18. What happened to the #DHConvalidator and #TEI? I am about to submit proposals for #DH2026 and it appears that submissions must not conform to any specific style or tooling.

  19. What happened to the #DHConvalidator and #TEI? I am about to submit proposals for #DH2026 and it appears that submissions must not conform to any specific style or tooling.

  20. What happened to the #DHConvalidator and #TEI? I am about to submit proposals for #DH2026 and it appears that submissions must not conform to any specific style or tooling.

  21. @awinkler @DHdKonferenz
    Ich habe leider auch Probleme. Auch das Beispiel Dokument produziert Fehler. Versuche es gerade mit einem Text ohne alles.

    #DHConvalidator #dhd2026

  22. @awinkler @DHdKonferenz
    Ich habe leider auch Probleme. Auch das Beispiel Dokument produziert Fehler. Versuche es gerade mit einem Text ohne alles.

    #DHConvalidator #dhd2026

  23. @awinkler @DHdKonferenz
    Ich habe leider auch Probleme. Auch das Beispiel Dokument produziert Fehler. Versuche es gerade mit einem Text ohne alles.

    #DHConvalidator #dhd2026

  24. @awinkler @DHdKonferenz
    Ich habe leider auch Probleme. Auch das Beispiel Dokument produziert Fehler. Versuche es gerade mit einem Text ohne alles.

    #DHConvalidator #dhd2026

  25. @awinkler @DHdKonferenz
    Ich habe leider auch Probleme. Auch das Beispiel Dokument produziert Fehler. Versuche es gerade mit einem Text ohne alles.

    #DHConvalidator #dhd2026

  26. @tillgrallert

    Only seeing this now, sorry. No worries, though! I firmly expect that #DH2025 will also use the #DHConValidator and produce XML/TEI versions of abstracts for long-term documentation.

    The difference with respect to #DHd is that the Convalidator version will only be expected from authors with accepted submissions, not in the reviewing stage.

  27. @tillgrallert

    Only seeing this now, sorry. No worries, though! I firmly expect that #DH2025 will also use the #DHConValidator and produce XML/TEI versions of abstracts for long-term documentation.

    The difference with respect to #DHd is that the Convalidator version will only be expected from authors with accepted submissions, not in the reviewing stage.

  28. @tillgrallert

    Only seeing this now, sorry. No worries, though! I firmly expect that #DH2025 will also use the #DHConValidator and produce XML/TEI versions of abstracts for long-term documentation.

    The difference with respect to #DHd is that the Convalidator version will only be expected from authors with accepted submissions, not in the reviewing stage.

  29. @tillgrallert

    Only seeing this now, sorry. No worries, though! I firmly expect that #DH2025 will also use the #DHConValidator and produce XML/TEI versions of abstracts for long-term documentation.

    The difference with respect to #DHd is that the Convalidator version will only be expected from authors with accepted submissions, not in the reviewing stage.

  30. @tillgrallert

    Only seeing this now, sorry. No worries, though! I firmly expect that #DH2025 will also use the #DHConValidator and produce XML/TEI versions of abstracts for long-term documentation.

    The difference with respect to #DHd is that the Convalidator version will only be expected from authors with accepted submissions, not in the reviewing stage.

  31. @janhorstmann @DHdKonferenz Dieses Jahr übrigens keine Probleme mit dem #DHConvalidator, da wir das Abstract kollaborativ direkt im #FidusWriter geschrieben haben. Dort gibt es am Ende einen nahtlosen Export nach HTML, #TEI-XML, .docx -- und eben auch .DHC-Format. Hat sehr gut funktioniert und ich wäre für Fidus für alle ab #DHd2025 ;)
    #DayOfDH2024

  32. @janhorstmann @DHdKonferenz Dieses Jahr übrigens keine Probleme mit dem #DHConvalidator, da wir das Abstract kollaborativ direkt im #FidusWriter geschrieben haben. Dort gibt es am Ende einen nahtlosen Export nach HTML, #TEI-XML, .docx -- und eben auch .DHC-Format. Hat sehr gut funktioniert und ich wäre für Fidus für alle ab #DHd2025 ;)
    #DayOfDH2024

  33. @janhorstmann @DHdKonferenz Dieses Jahr übrigens keine Probleme mit dem #DHConvalidator, da wir das Abstract kollaborativ direkt im #FidusWriter geschrieben haben. Dort gibt es am Ende einen nahtlosen Export nach HTML, #TEI-XML, .docx -- und eben auch .DHC-Format. Hat sehr gut funktioniert und ich wäre für Fidus für alle ab #DHd2025 ;)
    #DayOfDH2024

  34. @janhorstmann @DHdKonferenz Dieses Jahr übrigens keine Probleme mit dem #DHConvalidator, da wir das Abstract kollaborativ direkt im #FidusWriter geschrieben haben. Dort gibt es am Ende einen nahtlosen Export nach HTML, #TEI-XML, .docx -- und eben auch .DHC-Format. Hat sehr gut funktioniert und ich wäre für Fidus für alle ab #DHd2025 ;)
    #DayOfDH2024

  35. @janhorstmann @DHdKonferenz Dieses Jahr übrigens keine Probleme mit dem #DHConvalidator, da wir das Abstract kollaborativ direkt im #FidusWriter geschrieben haben. Dort gibt es am Ende einen nahtlosen Export nach HTML, #TEI-XML, .docx -- und eben auch .DHC-Format. Hat sehr gut funktioniert und ich wäre für Fidus für alle ab #DHd2025 ;)
    #DayOfDH2024

  36. Wait, there is no #DHConvalidator for this year's submission to #ADHO's annual conference? While I appreciate the reduced hoops to jump through, not having a template, converting to TEI/XML and verifying against a schema seemingly spells the end to conference abstracts easily to access for computational analyses (including metadata harvesting).

    #DH2025 #TEI #DigitalHumanities #DH @[email protected]

  37. Wait, there is no #DHConvalidator for this year's submission to #ADHO's annual conference? While I appreciate the reduced hoops to jump through, not having a template, converting to TEI/XML and verifying against a schema seemingly spells the end to conference abstracts easily to access for computational analyses (including metadata harvesting).

    #DH2025 #TEI #DigitalHumanities #DH @[email protected]

  38. Wait, there is no #DHConvalidator for this year's submission to #ADHO's annual conference? While I appreciate the reduced hoops to jump through, not having a template, converting to TEI/XML and verifying against a schema seemingly spells the end to conference abstracts easily to access for computational analyses (including metadata harvesting).

    #DH2025 #TEI #DigitalHumanities #DH @[email protected]

  39. Wait, there is no #DHConvalidator for this year's submission to #ADHO's annual conference? While I appreciate the reduced hoops to jump through, not having a template, converting to TEI/XML and verifying against a schema seemingly spells the end to conference abstracts easily to access for computational analyses (including metadata harvesting).

    #DH2025 #TEI #DigitalHumanities #DH @[email protected]

  40. Wait, there is no #DHConvalidator for this year's submission to #ADHO's annual conference? While I appreciate the reduced hoops to jump through, not having a template, converting to TEI/XML and verifying against a schema seemingly spells the end to conference abstracts easily to access for computational analyses (including metadata harvesting).

    #DH2025 #TEI #DigitalHumanities #DH @[email protected]

  41. While helping a colleague in trying to get #LaTeX into #dhconvalidator for #dh2023 I wonder if nobody has already built something better than LaTeX to #odt via #pandoc + #bibTeX to text via #zotero (or any other reference manager) and lots of manual interventions? Maybe done this but not sharing? Or not worth to share?

  42. While helping a colleague in trying to get #TeXLaTeX into #dhconvalidator for #dh2023 I wonder if nobody has already built something better than LaTeX to #odt via #pandoc + #bibTeX to text via #zotero (or any other reference manager) and lots of manual interventions? Maybe done this but not sharing? Or not worth to share?

  43. While helping a colleague in trying to get #LaTeX into #dhconvalidator for #dh2023 I wonder if nobody has already built something better than LaTeX to #odt via #pandoc + #bibTeX to text via #zotero (or any other reference manager) and lots of manual interventions? Maybe done this but not sharing? Or not worth to share?

  44. While helping a colleague in trying to get #TeXLaTeX into #dhconvalidator for #dh2023 I wonder if nobody has already built something better than LaTeX to #odt via #pandoc + #bibTeX to text via #zotero (or any other reference manager) and lots of manual interventions? Maybe done this but not sharing? Or not worth to share?

  45. While helping a colleague in trying to get #LaTeX into #dhconvalidator for #dh2023 I wonder if nobody has already built something better than LaTeX to #odt via #pandoc + #bibTeX to text via #zotero (or any other reference manager) and lots of manual interventions? Maybe done this but not sharing? Or not worth to share?