Re: Case-sensitive <dfn> in ReSpec

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.

On Wed, Apr 5, 2017 at 2:21 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:

> On Tue, Apr 4, 2017 at 5:51 PM, Gregg Kellogg <gregg@greggkellogg.net>
> wrote:
> >> On Apr 4, 2017, at 7:35 AM, Martynas Jusevičius <martynas@atomgraph.com>
> wrote:
> >>
> >> Hey all,
> >>
> >> now I had time to try Shane's suggestion to use data-lt. I don't think
> >> it works. I have defined
> >>
> >>  <dfn data-lt="iri-set">IRI</dfn>
> >>
> >>  <dfn data-lt="iri-function">iri</dfn>
> >>
> >> yet when I reference using <a data-lt="iri-function">iri</a>, the link
> >> that gets generated is #dfn-iri.
> >>
> >> If I use a some other link text such as <a
> >> data-lt="iri-function">wtf</a>, then the link is correctly generated
> >> as #dfn-iri-function. But that is of no use for me.
> >>
> >> Can you suggest a workaround?
> >
> > I believe this effectively creates “iri-function” as an alias for
> #dfn-iri. If you don’t wan’t “iri” defined, you can use @data-lt-noDefault
> as follows:
> >
> > <dfn data-lt=“iri-function” data-lt-noDefault>iri</dfn>
> >
> > This defines #dfn-iri-function, but not #dfn-iri.
>
> :/ This isn't compliant with the Bikeshed Definition Model. If you
> have a data-lt, that defines *all* of the linking texts; in
> particular, if you still want the visible text to be a linking text,
> you have to move it into the data-lt as well.
>
> ~TJ
>
>


-- 
Shane McCarron
Projects Manager, Spec-Ops