- From: Uldis Bojars <captsolo@gmail.com>
- Date: Fri, 24 Nov 2006 17:15:56 +0000
- To: danbri@danbri.org
- Cc: semantic-web@w3.org, ot@w3.org
Is it still located at the same URL - http://www.w3.org/RDF/Validator/ ? When trying it now (with the RDF/XML snippet quoted in the original mail) the validator returns an error message instead of a graph: " The graph image file is empty. " A graph is not generated and the same message is returned regardless of the image format option chosen (PNG, GIF, SVG, ...). Uldis [ http://captsolo.net/info/ ] On 11/24/06, Dan Brickley <danbri@danbri.org> wrote: > > I know a lot of people here care about the RDF Validator, so ... passing > on some good news: some progress with non-latin scripts in the output > graphs. Sounds like this is as good as it'll get without improvements in > the underlying (ie. non-W3C) GraphViz system and its supporting libraries. > > Thanks, Olivier & co :) > > cheers, > > Dan > > > > ---------- Forwarded message ---------- > From: olivier Thereaux <ot@w3.org> > To: Martin Duerst <duerst@it.aoyama.ac.jp> > Date: Wed, 22 Nov 2006 15:41:25 +0900 > Subject: Re: RDF Validator moved to new server - graph issues gone > > Hello Martin, All. > > On Sep 20, 2006, at 21:54 , Martin Duerst wrote: > > Great to see the basic graph problem fixed. But non-Latin-1 > > characters (e.g. Japanese) still seem to work in SVG, > > but not in PNG or GIF. > > I am happy to report progress on this. > We have managed to make the graphing tool use a font covering a very > hight number of scripts. > > RDF such as: > > <?xml version="1.0"?> > <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" > xmlns="http://example.org/foo"> > <rdf:Description rdf:about="http://www.w3.org/"> > <contains>ascii 漢字 цириллик Ërôpéàñ > ελαδδα ฉันก</contains> > </rdf:Description> > </rdf:RDF> > > Will now get nicely displayed. > > We can not guarantee that all possible glyphs will be displayed > properly. Unfortunately, the raster output for graphviz uses a > library which uses only one font (instead, as some more advanced > systems do, of trying other fonts which may contain the glyph if the > current font does not), and as far as our research has shown, there > is no such thing as a (free, truetype) font covering the whole of > unicode. > > More info on the issue: > http://www.graphviz.org/doc/FAQ.html#Q10a > > Thank you, > -- > olivier > > >
Received on Friday, 24 November 2006 17:16:20 UTC