W3C home > Mailing lists > Public > public-svg-wg@w3.org > January to March 2013

Re: Broken links in SVG2, problems building

From: Erik Dahlstrom <ed@opera.com>
Date: Thu, 21 Mar 2013 18:04:05 +0100
Cc: "public-svg-wg@w3.org" <public-svg-wg@w3.org>
To: "Chris Lilley" <chris@w3.org>, "Dirk Schulze" <dschulze@adobe.com>
Message-ID: <op.wua203r9geuyw5@gnorps>
On Thu, 21 Mar 2013 16:52:15 +0100, Dirk Schulze <dschulze@adobe.com>

> On Mar 21, 2013, at 8:35 AM, Chris Lilley <chris@w3.org> wrote:
>> Hello Erik,
>> Thursday, March 21, 2013, 4:25:38 PM, you wrote:
>>> On Wed, 20 Mar 2013 14:59:31 +0100, Chris Lilley <chris@w3.org> wrote:
>>>> Hello folks
>>>> Firstly, apologies for taking a long time to get a build environment
>>>> going. Cygwin sucks and my new laptop seems incompatible with every
>>>> linux distribution I have tried (videocard and ssd hard disk).
>>>> While I continue to work on that, I could use some help in fixing then
>>>> rebuilding SVG2 spec to make it ready for publication.
>>>> validity:
>>>>  easy, change <acronym> to <abbr> in the copyright statement (three
>>>>  places) for HTML5 validity.
>>> I've now fixed that in svg2-tools. Note that it was the pubrules  
>>> checker
>>> that suggested the <acronym> markup in the first place :)
>> Yes (for HTML4 and XHTML1). But the html5 validator complains.
>> Thanks for fixing the tools.
>>>> broken links:
>>>>  a lot, especially to the masking chapter. List of broken links
>>>>  attached.
>>> Let's try to get that sorted out as quickly as possible.
>> I suspect that some edits have changed IDs in the masking chapter,
>> causing most of the broken fragment links. If that was inadvertent,
>> restoring the IDs would fix them. If spec text has been removed
>> however, then all the other sections that link to it need to be
>> edited.
> Everything that points to the masking section, may should point to the  
> masking spec instead. How many references are there?

Quite a number of them.

Editor's drafts may change at any time (and break links). We can't have
such references in a WD.

In light of that I'd like to get a status update on all of the specs we
reference in this fashion. Do we want to publish updated versions of those
specs at the same time, or not?

In any case we should update the SVG2 spec so that it only links to  
specific working drafts, like  
http://www.w3.org/TR/2012/WD-compositing-20120816/ for example.

Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Thursday, 21 March 2013 17:04:44 UTC

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