|Join the Graphviz open source team!|
|With the explosion of graph-based data, the Graphviz project offers new contributors excellent opportunities to explore new concepts, or enhance tools that thousands of projects already use. We're looking for programmers and technical experts in core algorithms, interactive and command line programs, and rendering. This page provides a list of possible open work. And, of course, we are open to your suggestions. If you are interested, please contact us.|
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?
- What system are you running
1 hour 11 sec ago
- What is graph_qt.h ?
3 hours 25 min ago
- You can look in config.log to
4 hours 26 min ago
- - I solved my icon's problem.
4 hours 40 min ago
- No warning message that is the problem
10 hours 48 min ago
- How is the result worse with
1 day 2 hours ago
- how to avoid edge overlap?
1 day 2 hours ago
- The overlap parameter only
1 day 6 hours ago
- Right, I forgot you would be
6 days 1 hour ago
- This is really great! Many
6 days 3 hours ago