TUGboat 43:1 article: “Markdown 2.15.0: What's new?”

[Witiko]

By March 31, I would like to submit a TUGboat article, which will discuss the new features since the Markdown 2.10.0 article:

• Can I Play, Daddy?
  • Allow Jekyll Frontmatter #22 and Add an option to include arbitrary YAML documents #117 (see also here)
  • Adding Checklists #95
  • Add Markdown LaTeX themes for different document classes #104
  • Make HTML attributes actionable #91
  • Add hardLineBreaks option #98
• Bring 'Em On!
  • Allow Jekyll Frontmatter #22 and Add an option to include arbitrary YAML documents #117 (see also here)
  • Pass HTML through to TeX4ht #90
  • Integrate with jgm/pandoc #25
  • Make HTML attributes actionable #91
  • Make the beginning and the end of a markdown document actionable #109
• Quality of Life
  • Improve ConTeXt interface #17
  • Preserve trailing spaces in ConTeXt MkIV #101
  • Add the \markdownImportSnippets LaTeX command #107
  • Support bulk and partial redefinitions in the `\markdownSetup` LaTeX command #121
• Show Me the Code!
  • Make markdown-cli in the Docker image a simple alias #102
  • Add reflection to the TeX implementation #119
  • Reimplement LaTeX setup snippets using lthooks #93

I already drafted an outline of the article. Co-authorship by those who contributed the new features is welcome (@drehak, @xvrabcov, @TeXhackse, @michal-h21, @writersglen). Alternatively, if you'd like to contribute to the text in small ways but don't want to commit to full authorship, informal review of the text will also be appreciated. 🙂

[writersglen]

Hello, I heartily applaud and support as best I can Vit’s initiative to extend the utility of markdown to the TeX community. As I see it, there are three stakeholders in this project: coders engaged in the technical challenges, the TeX community at large, and the many thousands of self-publishers who stand to publish trade-quality books with less sweat and tears. I fall into the third category. I’ve published three books composed and typeset with LaTeX and am close to launch of a fourth. My insufficient LaTeX fluency has made all four projects more difficult than necessary. For this reason I’m particularly interested in Vit’s book publishing interface proposal. Given my limited TeX competencies, however, the best I can offer is a Mickey-the-Dunce user perspective. As an end user, the first thing I’d like to see is a clear statement of how the book publishing interface can help me publish better books. The second thing is clear and comprehensive how-to documentation. In short, I need confidence that adoption of TeX markdown shortcomings will not leave me in a lurch if I choose to adopt it into my workflow. Much work needs to be done, seems to me, to accomplish this goal. First is a statement of intent that inspires all stakeholders to put their shoulders behind the project. Second is a definitive list of markdown tags necessary and sufficient to meet the diverse needs of book publishers. This list will require input and consensus of all stakeholders—but may not be an easy thing to achieve. I’d be happy to add my evolving wish list to the functional necessities of the book publishing interface as well as help with end-user documentation. I can also offer modest bounties for accomplishment of well-specified technical milestones. Such is my belief that book publishing-focused markdown is a significant and consequential contribution to the TeX ecosystem. Lloyd R. Prentice Writersglen Publications

…

Sent from my iPad

On Feb 27, 2022, at 4:41 AM, Vít Novotný ***@***.***> wrote:  By March 31, I would like to submit a TUGboat article, which will discuss the new features since the Markdown 2.10.0 article: #22 and #117 (here are some ideas) #25 #90 #91 #104 Other new features: #101, #102, #98, #109 I already drafted an outline of the article. Co-authorship by those who contributed the new features is optional but welcome ***@***.***, @xvrabcov, @TeXhackse, @michal-h21, @writersglen). Alternatively, if you'd like to contribute to the text in small ways but don't want to commit to full authorship, informal review of the text will also be appreciated. 🙂 — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.

[Witiko]

Dear Karl, my contributors and I are planning to submit an article to TUGboat 43:1. Is it OK if we submit by March 31, or would you rather if we submit our article in advance -- say during the next week? Best, Vitek

…

On Sat, Nov 20, 2021 at 02:13:43PM -0700, Karl Berry wrote: Extending the article is all to the good. In that case, yes, sure, we'll wait to read it until you send us the final version. Thanks for thinking of this, and looking forward to it. --all the best, karl.

[Witiko]

my contributors and I are planning to submit an article to TUGboat 43:1. Is it OK if we submit by March 31, or would you rather if we submit our article in advance -- say during the next week? It's ok to submit March 31, but earlier is always appreciated, when possible. I.e., when an article is ready, go ahead and send it in anytime. Looking forward. Thanks! -k