-
Notifications
You must be signed in to change notification settings - Fork 96
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
Umlauts causing error on build #81
Comments
@mgaitan The Screenshot with the diagram you see in my Post is not the result in the rendered sphinx doc. I've rendered this with the online tool. Mermaid still throws an error and only the Error - Placeholder is shown in the doc. |
@sgaechter the screenshot I've posted was after copying/pasting your diagram code in a .rst file and then building html with sphinx. Is it not the issue reported? |
@mgaitan I tested the output again. Unfortunately, either the HTML or latexpdf is rendered correctly on my side: as soon as I replace the umlaut "ö" to "oe " the rendering works as expected: Attached you can find the full source code of the sphinx-Project. I'd be pleased if somebody can tell me what's wrong. Used versions in requirements.txt Thanks |
Issue still open also with latest release. |
This is still a problem. The following line in a sankey-beta diagram causes a Diagram syntax error:
|
Umlauts, as common in German Language (like: ä, ö, ü) causing problems buildung Sphinx Docs. The infected Charts are replaced by "Syntax error in graph mermaid version 8.13.7":
Error Message displayed in Doc:
As soon as all umlauts are replaced, the graphs will be displayed as expected.
Tested
make
commands: html, latexpdfExample:
`.. mermaid::
flowchart LR
a(Kundeninput) --> b(Product-Backlog) --> c(Sprintplanung) --> e("Sprint (2-4 Wochen)") --> f(Sprint-Review) --> g([Zum Veröffentlichungsprozess])
e --> d(Sprint-Retrospektive) --> c`
When I build the mermaid chart with mermaid-cli the umlauts are built correct (see output.png below):
used version: Master (a6c1f8b)
The text was updated successfully, but these errors were encountered: