gml2gv.1 2.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889
  1. .TH GML2GV,GV2GML 1 "24 June 2011"
  2. .SH NAME
  3. gml2gv,gv2gml \- GML-DOT converters
  4. .SH SYNOPSIS
  5. .B gml2gv
  6. [
  7. .B \-?v
  8. ]
  9. [
  10. .BI \-g gname
  11. ]
  12. [
  13. .BI \-o outfile
  14. ]
  15. [
  16. .I files
  17. ]
  18. .br
  19. .B gv2gml
  20. [
  21. .B \-y
  22. ]
  23. [
  24. .B \-?
  25. ]
  26. [
  27. .BI \-o outfile
  28. ]
  29. [
  30. .I files
  31. ]
  32. .SH DESCRIPTION
  33. .B gml2gv
  34. converts a graph specified in the GML format to a graph in the GV (formerly DOT) format.
  35. .B gv2gml
  36. converts a graph specified in the GV format to a graph in the GML format.
  37. .SH OPTIONS
  38. The following options are supported:
  39. .TP
  40. .B \-v
  41. Turns on verbose mode
  42. .TP
  43. .B \-y
  44. Uses attributes according to yWorks.com documentation instead of the GML
  45. specification.
  46. .TP
  47. .B \-?
  48. Prints usage information and exits.
  49. .TP
  50. .BI \-g "gname"
  51. The string \fIgname\fP is used as the name of the generated graph.
  52. If multiple graphs are generated, subsequent graphs use the name
  53. \fIgname\fP appended with an integer.
  54. .TP
  55. .BI \-o "outfile"
  56. Prints output to the file \fIoutfile\fP. If not given, \fBgml2gv\fP
  57. uses stdout.
  58. .TP
  59. .SH OPERANDS
  60. The following operand is supported:
  61. .TP 8
  62. .I files
  63. Names of files containing 1 or more graphs in GML.
  64. If no
  65. .I files
  66. operand is specified,
  67. the standard input will be used.
  68. .SH RETURN CODES
  69. Return \fB0\fP
  70. if there were no problems during conversion;
  71. and non-zero if any error occurred.
  72. .SH "LIMITATIONS"
  73. As both the graph and graphics models of GV and GML differ significantly, the
  74. conversion is at best approximate. In particular, it is not clear how multiedges
  75. are differentiated in GML, so multiedges are created in GV with no user-available
  76. key. Also, no attribute information is lost, in that
  77. any GML attributes that aren't converted to GV equivalents are retained as
  78. attributes in the output graph.
  79. .P
  80. At present,
  81. .B gv2gml
  82. does not support subgraphs and clusters. In addition, there does not appear to be
  83. a standard mechanism for specifying default node and edge attributes in GML, so
  84. any attributes are repeated for every node and edge.
  85. .SH AUTHORS
  86. Emden R. Gansner <[email protected]>
  87. .SH "SEE ALSO"
  88. dot(1), libcgraph(3)