-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardizing the use of Markdown and LaTeX for the documentation layer #3636
Comments
General LaTeX support sounds very scary, but what about KaTeX, would it be considered mature, maintained and stable enough for the Modelica specification to depend upon? License concerns? Markdown would be handy, but then we would need to agree on some dialect, which needs to be stable and come with a maintained and generously licensed implementation. What are the options? |
For our part, using something significantly different than what Dymola uses would be a showstopper. We switch from LaTeX to markdown some years ago (relying on pandoc) for most usages to accomodate more people. LaTeX is astounding and I love it, but it is esoteric. Markdown (any reasonably well spread dialect would do for my part) could a be a low common denominator. Aren't we writing in markdown right here? Markdown is used for readme on git repositories, to write documentation with Sphinx increasingly often as a replacement for cumbersome reST, as well as many popular tools such as Notion or Obsidian. There are diverse specifications of Markdown, with first “vanilla markdown”: https://daringfireball.net/projects/markdown/. As far as I am concern, required features include:
The rest would be considered bonus. |
Well said, totally agree! |
We will have to investigate exactly what Markdown extensions Dymola uses ( @DagBruck ). As I see the main benefit it is quick and works for simple documentation - without having to use a specialized editor. For LaTeX it is display math, e.g.,
Not because LaTeX math is the easiest to read and write, but because there's no viable alternative. |
To my knowledge Dymola supports the GitHub dialect of Markdown. (We haven't implemented it ourselves, but that is what the toolkit documentation says.) |
Note that GitHub isn't good at documenting their Markdown. The formal specification they link to is: https://github.github.com/gfm/ from 2019, and then Math was added in 2022 https://github.blog/news-insights/product-news/math-support-in-markdown/ with separate documentation https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions Test from blog: When Note that the latter (directly copied from the blog!) doesn't work in GitHub, it should be And two variants from doc: The Cauchy-Schwarz Inequality The Cauchy-Schwarz Inequality Unfortunately Dymola 2025x only support display math, not inline math or math-language. On the other hand without the weird white-space issue for display math. Conclusion: I would just specify GitHub flavored Markdown with display math; and hope that tools will be more consistent. |
Inline math works in Dymola with the following syntaxe :
|
Follow up of modelica/ModelicaStandardLibrary#3122 in the proper place, i.e., MAP-Lang:
Regarding OpenModelica I'm a bit hesitant at investing resources to implement a feature that is not standardized, just by reverse-engineering other tools. But I am definitely in favour of adding this feature to the standard, and I would definitely go ahead with the implementation and with an MCP if there is some consensus that this should be standardized. That would also provide two test implementations, which I understand is a (de-facto?) requirement for adding two language feature to the spec.
What do the other tool vendors think? I guess DS is fine with that, since they implemented it already. What about Wolfram, MapleSoft, and ESI?
The text was updated successfully, but these errors were encountered: