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,ASCII-7-bit Received: by 10.204.152.217 with SMTP id h25mr1314135bkw.3.1337072077963; Tue, 15 May 2012 01:54:37 -0700 (PDT) Path: e27ni4170bkw.0!nntp.google.com!news2.google.com!goblin1!goblin3!goblin.stu.neva.ru!news.tu-darmstadt.de!news.belwue.de!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Tue, 15 May 2012 10:54:36 +0200 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Suggestion for RM HTML formatter extension References: <82aa1ud0l3.fsf@stephe-leake.org> <20120509131736.63c924c8@vostro> <82lil0gxbm.fsf@stephe-leake.org> <20120511040710.52bbc3fd@vostro> <87obpv17gd.fsf_-_@adaheads.sparre-andersen.dk> In-Reply-To: Message-ID: <4fb219cc$0$6574$9b4e6d93@newsspool3.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 15 May 2012 10:54:36 CEST NNTP-Posting-Host: 99119ed8.newsspool3.arcor-online.net X-Trace: DXC==dB0lk@DXj1n`gW2MTm]<3McF=Q^Z^V384Fo<]lROoR18kFejV8a0JEmighd<6X=:jk>7Jif8 X-Complaints-To: usenet-abuse@arcor.de Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: 2012-05-15T10:54:36+02:00 List-Id: On 15.05.12 09:02, Randy Brukardt wrote: > "Manuel Collado" wrote in message >> 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 > ... > 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). Just for reference, the production for [VC:ID] of XML includes '.' and '-' in the suffix of NameStartChar (NameChar)*.[1] The CSS grammar, however, doesn't include '.' in its nmchar.[2] Otherwise one couln't write style sheet rules that select with elementname.classsname. But there is a workaround in CSS for incorrect elementname#id.with.dots. One writes elementname[id="id.with.dots"]. So a combination of '.' and '-' would be standards compliant, and still practical. __ [1] http://www.w3.org/TR/REC-xml/#NT-Name [2] http://www.w3.org/TR/css3-syntax/#grammar