You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
If one looks at the USE "manual" it is completely outdated (last version is from 2007).
The switch to mardown would couple the documentation and changes, because of
Markdown files can be rendered in GitHub, so documentation is integrated inton the project website
A final PDF could still be generated so nothing is lost
Describe the solution you'd like
In a frist step: translate the LaTex based documentation to Markdown.
Afterwards add build-step to maven to genrate the PDF-manual and to generate some API-Docs
Describe alternatives you've considered
Further using LatTex.
Additional context
n/a
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
If one looks at the USE "manual" it is completely outdated (last version is from 2007).
The switch to mardown would couple the documentation and changes, because of
Describe the solution you'd like
In a frist step: translate the LaTex based documentation to Markdown.
Afterwards add build-step to maven to genrate the PDF-manual and to generate some API-Docs
Describe alternatives you've considered
Further using LatTex.
Additional context
n/a
The text was updated successfully, but these errors were encountered: