From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,6487f59679c615d8 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Received: by 10.68.125.201 with SMTP id ms9mr937217pbb.3.1337065382196; Tue, 15 May 2012 00:03:02 -0700 (PDT) MIME-Version: 1.0 Path: pr3ni560pbb.0!nntp.google.com!news2.google.com!goblin2!goblin1!goblin.stu.neva.ru!news.tornevall.net!news.jacob-sparre.dk!munin.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Suggestion for RM HTML formatter extension Date: Tue, 15 May 2012 02:02:54 -0500 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: References: <82aa1ud0l3.fsf@stephe-leake.org> <20120509131736.63c924c8@vostro> <82lil0gxbm.fsf@stephe-leake.org> <20120511040710.52bbc3fd@vostro> <87obpv17gd.fsf_-_@adaheads.sparre-andersen.dk> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: munin.nbi.dk 1337065379 27276 69.95.181.76 (15 May 2012 07:02:59 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Tue, 15 May 2012 07:02:59 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Date: 2012-05-15T02:02:54-05:00 List-Id: "Manuel Collado" wrote in message news:joqqmr$ki4$1@speranza.aioe.org... > El 11/05/2012 17:32, Simon Wright escribi�: >> Jacob Sparre Andersen writes: >>>... >>> If I could write and people would >>> end up at paragraph 6 in section 9.7.3 of the Ada05 reference manual, it >>> would be much easier than linking to the whole section and then writing >>> that people have to scroll down to paragraph 6. >> >> I'd have thought that would be straightforward enough .. the paragraph >> numbers are in a div with class paranum. A simple patch means I can >> write for para 13/2 of the 2005 manual (I'm not at >> all sure of the legality of that slash, but Safari and Chrome are >> happy!!). > > Is seems that p13/2 as a "name" target is legal in HTML, but not in XHTML. > In addition, IIUC the use of the "name" attribute is deprecated in favor > of the "id" one, and XHTML5 even has dropped it. > > "id" values don't allow slashes. But slashes could be easily converted to > hyphens or underscores, if browser standard compliance really matters. So > we could write , for instance We don't need the slashes at all, since that just a version indicator, and the root path specifies the version of the document anyway. I was just going to strip them when I added them to ARM_Form. That's especially valuable since these versions are much more likely to change than the paraagraph numbers themselves, so it would make the links more resilient to change (important for working versions of the Standard). I was more worried about the periods (which are not optional). They could be converted to something else, but then the correspondence between the anchor name and the paragraph number would not be as obvious, which would possibly hurt the usage (when people want to hand-create these links - which seems to be the main benefit of the idea). > In addition, if old and new browsers have to be supported, I believe it is > also possible to have both "id" and "name" target attributes with exactly > the same, duplicated value. That would seem to be necessary (I've only used "name" because older browsers don't support "id" - I rather doubt any browsers are going to be dropping support for it anytime soon because it is widely used). Randy.