From: Eero T. <ee...@us...> - 2007-05-14 19:22:06
|
Hi, On Monday 14 May 2007, bm...@ca... wrote: > Please file a bug. > > Info here http://www.graphviz.org/doc/FAQ.html > > It appears UTF-8 symbols must be between <> or "" > I would think GRAMPS does not produce dot files like that. I think I fixed that (put all text strings inside "") a long time ago in the GraphViz plugin output. > Can somebody with he arabic data check this? > Then only svg works, ps has not utf fonts. The FAQ: > Output: It is essential that a font which has the glyphs for your > specified characters is available at final rendering time. The choice of > this font depends on the target code generator. For the gd-based raster > generators (PNG, GIF, etc.) you need a TrueType or Type-1 font file on > the machine running the Graphviz program. If Graphviz is built with > the fontconfig library, it will be used to find the specified font. I.e. the first thing is that one has a font with arabic glyphs *and* specifies that font for the GraphViz (in the *.dot file). > Otherwise, Graphviz will look in various default directories for the font. > The directories to be searched include those specified by the fontpath > attribute, related environment or shell variables (see the fontpath > entry), and known system font directories. The table > http://www.graphviz.org/doc/char.html points out that these glyphs are > from the times.ttf font. With fontconfig, it's hard to specify this font. > Times usually gets resolved to Adobe Type1 times, which doesn't have > all the glyphs seen on that page.) And makes sure that when fontconfig is used by GraphViz, the fontconfig finds that font too... > For Postscript, the input must be either the ASCII subset of UTF-8 or > Latin -1. (We have looked for more general solutions, but it appears that > UTF-8 and Unicode are handled differently for every kind of font type in > Postscript, and we don't have time to hack this case-by-case. If someone > wants to volunteer to work on this, let us know.) I.e. PostScript (and PDF) support unicode, but each postscript font type does it differently so GraphViz supports only latin-1 glyphs for PostScript. > For SVG output, we just pass the raw UTF-8 (or other encoding) straight > through to the generated code. And this is the best option I think. Then rendering the text strings (fonts etc) is problem of the SVG viewer. If your browser can show arabic pages, I would hope its SVG supports that too... - Eero |