W3C home > Mailing lists > Public > public-svg-wg@w3.org > July to September 2012

Re: spec building on cygwin

From: Chris Lilley <chris@w3.org>
Date: Tue, 24 Jul 2012 20:15:30 +0200
Message-ID: <858476918.20120724201530@w3.org>
To: Cameron McCormack <cam@mcc.id.au>
CC: SVG WG <public-svg-wg@w3.org>
On Tuesday, July 24, 2012, 7:54:32 PM, Cameron wrote:

CM> Chris Lilley:
>> Now it seems to build, but complains about the new property that I added. I just added it to propidx.html as well, but it still complains. Where else do I need to add this?

>> $ make
>> [ -f /usr/bin/cygpath.exe ] || make -C master/images/implnote/arcs/
>> java -classpath "D:\cygwin\home\Chris\SVG2\svg2-tools\saxonb\saxon9.jar" net.sf.saxon.Transform -ext:on -dtd:off -expand:off -l:on "D:\cygwin\home\Chris\SVG2\svg2\master\publish.xml" "D:\cygwin\home\Chris\SVG2\svg2-tools\publish.xsl" chapters-to-build="propidx"
>> Unknown name "white-space" at file:/D:/cygwin/home/Chris/SVG2/svg2/master/propidx.html line -1.
>> xsltproc --novalid --stringparam publish '/home/Chris/SVG2/svg2/build/publish' --stringparam chapters 'toc intro concepts render struct types styling coords paths shapes text painting color pservers masking filters interact linking script animate fonts metadata backward extend svgdom idl java escript implnote conform access i18n minimize refs eltindex attindex propidx feature mimereg changes' /home/Chris/SVG2/svg2-tools/single-page.xsl /home/Chris/SVG2/svg2/build/publish/index.html > /home/Chris/SVG2/svg2/build/publish/single-page.html
>> rsync -auC /home/Chris/SVG2/svg2/master/style /home/Chris/SVG2/svg2/master/images /home/Chris/SVG2/svg2/master/svg.idl /home/Chris/SVG2/svg2/build/publish
>> sh: rsync: command not found
>> Makefile:9: recipe for target `all' failed

CM> The failure is that you haven't got rsync installed (which it uses to 
CM> copy a few things around).  

Its installed now.

CM> But the warning about the property you can
CM> fix by adding something to definitions.xml.  I think just add a new 
CM> <property> element pointing to the definition in the css3-text spec.


All seems to make correctly now.

CM> BTW, for some of the section rewriting I've been doing for properties 
CM> that we are just borrowing from CSS, like in 
CM> https://svgwg.org/svg2-draft/painting.html#VisibilityControl, I've 
CM> removed the blue boxes altogether and just referenced the relevant CSS
CM> spec.  I guess we should do the same for white-space here, or I should
CM> add back in the blue boxes for display/visibility.

I will have a look and see what you did. I think its easier though to have the blue box summary, then point to the relevant spec for the meaning of the values etc.

 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups
Received on Tuesday, 24 July 2012 18:17:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:15 UTC