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=0.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA 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,UTF8 Received: by 10.68.241.7 with SMTP id we7mr6144202pbc.4.1336995359146; Mon, 14 May 2012 04:35:59 -0700 (PDT) Path: pr3ni24733pbb.0!nntp.google.com!news2.google.com!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail From: Manuel Collado Newsgroups: comp.lang.ada Subject: Re: Suggestion for RM HTML formatter extension Date: Mon, 14 May 2012 13:36:00 +0200 Organization: Aioe.org NNTP Server 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: nhcAheode0bihPZaNcUxIQ.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120312 Thunderbird/11.0 X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: 2012-05-14T13:36:00+02:00 List-Id: 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 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. -- Manuel Collado - http://lml.ls.fi.upm.es/~mcollado