LISTSERV mailing list manager LISTSERV 16.5

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  June 2016

TEI-L June 2016

Subject:

Re: cRef usage

From:

Thierry Pellé <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Sun, 12 Jun 2016 14:25:54 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (34 lines)

Hello,
	short, fast and lousy but useful ! ;-)

Hence, if I understand well, I may define
<prefixDef ident="cref:"
 matchPattern="(.+?), (.+?)"
 replacementPattern="#$1-$2">
 <p>
	Replaces cRef references.
 </p>
</prefixDef>

and then use
<quote ref="cref:Virgile, Enéide">
 ...
</quote>

That sounds good.

Thank you!
Thierry

Le dimanche 12 juin 2016 à 08:00 -0400, Syd Bauman a écrit :
> [Fast-and-lousy response from an airport.]
> 
> The @cRef mechanism has essentially been superceded by the
> <prefixDef> mechanism, which can be used on any pointer.
> 
> >     Guidelines specifies that @cRef "specifies the destination of
> >     the pointer by supplying a canonical reference". I wonder why
> >     only gloss, ptr, ref, term provide such a canonical forme for a
> >     pointer. For instance, why is it not possible to specifies the
> >     @souce attribute of a quote as a canonical pointer?

Top of Message | Previous Page | Permalink

Advanced Options


Options

Error during command authentication.

Error - unable to initiate communication with LISTSERV (errno=104). The server is probably not started.

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager