ticket #3 fix, and #1

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

ticket #3 fix, and #1

Bruce D'Arcus
The ticket 3 fix address most of the problem.  However, strickly
speaking, this:

Some more citations: (Thrift, 1990; Tilly, 2000, Tilly, 2002; Times, 2001).

... should be:

Some more citations: (Thrift, 1990; Tilly, 2000, 2002; Times, 2001).

In other words, the second author name in a group gets left off.

Also, for ticket #1, here's the current rendering with the test doc:

(C.S., 2001)

It should be:

(Tremblay v. Quebec, 2001)

So the question is:

a) what should be the markup in CSL to indicate this, and...
b) how to modify the code to use CSL for this sorting

Bruce


Reply | Threaded
Open this post in threaded view
|

Re: ticket #3 fix, and #1

Bruce D'Arcus
Bruce D'Arcus wrote:

> So the question is:
>
> a) what should be the markup in CSL to indicate this, and...

Here's my thoughts:

The sorting logic should just use the first child of a cs:reftype as the
first option on sort.  The second option ought to be indicated via an
attribute on that element.

So, for the legal case example in the sample, it might be:

<reftype name="legal case">
   <title/>

... while for an article, it might be:

<reftype="article">
   <creator alternate-sort-key="container-title">

The above key would then map to an xpath expression, where the options
would be defined in the schema.

The trick, though, is how to then handle plain text.  For example, a
book without an author name might have a rule that says it must be
replaced by "Anonymous" (as in current code).

So how to handle this?

Bruce