W3C home > Mailing lists > Public > public-webauthn@w3.org > March 2017

Re: editorial: fixup all '<a>...</a>' to be '[=...=]' ?

From: =JeffH <Jeff.Hodges@KingsMountain.com>
Date: Thu, 2 Mar 2017 15:30:51 -0800
To: Vijay Bharadwaj <vijaybh@microsoft.com>, W3C WebAuthn WG <public-webauthn@w3.org>
Message-ID: <9b27c031-94d6-fc4f-087c-25f3faf1972f@KingsMountain.com>

 >> From: =JeffH [mailto:Jeff.Hodges@KingsMountain.com]
 >> Sent: Wednesday, March 01, 2017 4:00 PM
 >> should we fixup all occurrences of '<a>...</a>' to be the new hotness
 >> '[=...=]' ?

On 3/2/17 7:18 AM, =JeffH wrote:
 > vijay replied:
 >> I was thinking the same thing. Also <em>foo</em> to *foo* maybe?
 > sure.

well, I've attempted a blanket change of all occurrences of '<a>...</a>' 
to be '[=...=]' and bikeshed got the flu and impressively projectile 
barfed to the extent that it was not at all clear what caused it.

So doing the '<a>...</a>' to be '[=...=]' thing will take some work 
beyond a simple-minded blanket find-n-replace (sigh).

Also, bikeshed ignores the emphasis portion of '*[=...=]*' and renders 
the '*'s which seems..uh..suboptimal.

So for now some '<em>...</em>' constructs need to stay around -- 
'<em>[=...=]</em>' works correctly.

Received on Thursday, 2 March 2017 23:38:10 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:24 UTC