author replacement

CSL Development
1

OK, how’s this …

   <bibliography author-as-sort-order="all">

———.

… ?

Bruce

2

Seems good to me!

Here is another “problem” that you might want to think about (or perhaps
already have done, but I missed it). Sometimes in articles one refers to a
citation in different ways. For example when one wants to mention the name
of the authors in the main text.

Lignin is a big molecule (Boon et al., 1993).

vs.

The size of lignin was reported by Boon et al. (1993) to be big.

Or we might want to refer the reader a bit more specific way, indicating
Boon based his work on that of others.

Lignin is a big molecule (see Boon et al., 1993 and references therein).

I’d say these surrounding texts and such are to be specified in OpenDocument
(or whichever fileformat is used) and to be passed to Citeproc when the
citations have to be rendered. Now, shouldn’t some of the markup information
needed for that rendering be known already? E.g. a journal may require the
extra text to always be italic (I don’t know if any journal does, seems
reasonable though).

Also, shouldn’t there be an attribute for citation to say wether it has to
be superscript or not?

Johan________________________________________________
Message sent using
Mailophalen 0.2.7.2

3

Lignin is a big molecule (Boon et al., 1993).

vs.

The size of lignin was reported by Boon et al. (1993) to be big.

This handled by local citation classes in the document. In docbook,
for exammple, you’d give a role of “year”. However, that just renders
(1993) and author would type the name. The reason is that sometimes
this gets complicated and author is not immediately preceding citation.

In any case, it’s a detail of citeproc, not CSL. Author-year citations
are the only ones that have this issue.

Or we might want to refer the reader a bit more specific way,
indicating
Boon based his work on that of others.

Lignin is a big molecule (see Boon et al., 1993 and references
therein).

Same.

I’d say these surrounding texts and such are to be specified in
OpenDocument
(or whichever fileformat is used) and to be passed to Citeproc when the
citations have to be rendered.

There are two options.

-	All of this is just text (captions).
-	it is a local style type, where chooses a "see" checkbox, for example

I tend to prefer the latter, and I guess you do too? It does suggest
config in CSL.

Now, shouldn’t some of the markup information
needed for that rendering be known already? E.g. a journal may require
the
extra text to always be italic (I don’t know if any journal does, seems
reasonable though).

Also, shouldn’t there be an attribute for citation to say wether it
has to
be superscript or not?

Wouldn’t that be a font-style?

Bruce

4

In any case, it’s a detail of citeproc, not CSL. Author-year citations
are the only ones that have this issue.

Agreed.

I’d say these surrounding texts and such are to be specified in
OpenDocument
(or whichever fileformat is used) and to be passed to Citeproc when the
citations have to be rendered.

There are two options.

  • All of this is just text (captions).
  • it is a local style type, where chooses a “see” checkbox, for example

I tend to prefer the latter, and I guess you do too? It does suggest
config in CSL.

I don’t exactly understand what you mean by these two options. I tend to
think that it would be good to have a
font-attributes-style/weight/family-to-use-for-text-around-a-citation-within-the-citation.
But then worded perhaps a bit shorter… :wink:

Also, shouldn’t there be an attribute for citation to say wether it
has to be superscript or not?

Wouldn’t that be a font-style?

Formatting.Attributes =
attribute font-family { text }?,
attribute font-style { “italic” | “small caps” | “normal” }?,
attribute font-weight { “normal” | “bold” | “light” }?

Making that a font-style option could work, but doesn’t that limit the
choice to just one style. So no italic, small caps in my superscript
citation?

Johan________________________________________________
Message sent using
Mailophalen 0.2.7.2

5

There are two options.

  • All of this is just text (captions).
  • it is a local style type, where chooses a “see” checkbox, for
    example

I tend to prefer the latter, and I guess you do too? It does suggest
config in CSL.

I don’t exactly understand what you mean by these two options. I tend
to
think that it would be good to have a
font-attributes-style/weight/family-to-use-for-text-around-a-citation-
within-the-citation.
But then worded perhaps a bit shorter… :wink:

To be consistent, what you are wanting suggests:

....

Indeed, the citation proposal that I wrote for OD has caption elements.

What I was saying is you could also think about something like:

see ....

… where a user chooses the local-styling type and rendering
(including grouping) is handled automatically by citeproc.

Also, shouldn’t there be an attribute for citation to say wether it
has to be superscript or not?

Wouldn’t that be a font-style?

Formatting.Attributes =
attribute font-family { text }?,
attribute font-style { “italic” | “small caps” | “normal” }?,
attribute font-weight { “normal” | “bold” | “light” }?

Making that a font-style option could work, but doesn’t that limit the
choice to just one style. So no italic, small caps in my superscript
citation?

Question: how is this handled in CSS, LaTeX, FO, etc.?

Also, when would you need to indicate superscripting, other than in a
footnote style?

Bruce