|Due to organizational changes, the Graphviz web site will see some modifications in the near future. In particular, it will probably no longer provide binary packages for Windows and Macs. The latter can be obtained via Macports or Home Brew. If someone wants to set up Appveyor for Windows, we would be grateful.|
Handling of special characters
Normally I use graphviz with the tool 'gvedit 1.01' that is part of the Windows installation of graphviz. Now, because of a certain demand described in forum topic "Different spline-styles on different levels not possible?", I had to use the command line version of 'dot'. When processing my gv-file with 'dot' I've got this warning:
(dot.exe:5472): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
In my input-file I use the Ascii-Character 133 (three dots in a row) for some labels.
So the gv-file looks like this (I hope that the charater "..." between A and B will be visible after saving this posting):
C [label = "A…B"];
A -> C [splines = "true"];
B -> C [splines = "false"];
But the result when using the command line call of 'dot' shows a different character (a box with a cross). Only when I call dot from 'gvedit' I get the desired result. In the past I also created graphviz-files with cyrillic unicode characters in the labels of the nodes. This was no problem when I opened the files in 'gvedit'. But I just made a test with comand line dot and got the message:
Warning: ju.gv:1: syntax error in line 1 near '´╗┐Digraph'
Why do I get these different results?
Is there any way to influence the way, 'dot' handles special characters and unicode files?
- I need to check, but the
6 hours 46 min ago
- I'm guessing you are running
1 day 10 hours ago
- on the command line i got
1 day 11 hours ago
- If you are using a GUI, you
1 day 12 hours ago
- thanks for your replay, sorry
1 day 13 hours ago
- gvedit features..
1 day 19 hours ago
- Use the gvpr command. If your
2 days 5 hours ago
- The only supported attribute
2 days 5 hours ago
- Sorry, the interface does not
3 days 11 hours ago
- > Easy Solution
1 week 3 days ago