- From: Martynas Jusevičius <martynas@atomgraph.com>
- Date: Wed, 5 Apr 2017 23:30:30 +0200
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: Shane McCarron <shane@spec-ops.io>, Gregg Kellogg <gregg@greggkellogg.net>, Marcos Caceres <w3c@marcosc.com>, "spec-prod@w3.org Prod" <spec-prod@w3.org>
I'm not familiar with Bikeshed and just learning to use ReSpec. Gregg's suggestion seems to work -- at least I get the right links. Are you saying it's bad practice? If so, what is the solution for case-sensitive terms? On Wed, Apr 5, 2017 at 9:42 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > On Wed, Apr 5, 2017 at 12:38 PM, Shane McCarron <shane@spec-ops.io> wrote: >> For whatever reason the ReSpec community wanted to roll the text into the >> collection as well. You can override that behavior with the additional >> attribute data-lt-noDefault. If this is present then it WILL NOT roll the >> text into the collection of aliases for the term. > > Given that the purpose of adding data-lt to ReSpec was to be compliant > with Bikeshed for the purpose of scraping, gratuitous changes kinda > defeat the point, particularly when the maintainer of Bikeshed was > never informed of them. Specs relying on this feature will *not* be > scraped correctly by Shepherd, and will *not* be linkable in the same > way from a Bikeshedded spec. > > ~TJ
Received on Wednesday, 5 April 2017 21:31:04 UTC