Skip to content

Make appearance of co-authors a bit more configurable #20

@gkthiruvathukal

Description

@gkthiruvathukal

@klaeufer Great work to get the author annotations working. It works nicely.

I put my HCI hat on and think we may want to refactor author annotations just a bit.

Basically, there seem to be two "hooks" for mkbibnamegiven and mkbibnamefamily.

Could we use \renewcommand to create macros that perform the desired emphasis for each of the categories. That is, in our current design, there would be macros named highlight<category>, e.g. highlight_undergrad, highlight_graduate, and highlight_myself. That way, you don't need to hard-code the specific emphasis into the preceding hook macros.

We may still need to debate this, but I find highlighting ourselves using asterisk a bit too understated. I feel like "underline" should be the default for emphasizing ourselves, if we are going to use asterisk as a default.

The next decision comes down to whether to give more emphasis to undergrad or graduate. I feel like both are immensely--and equally--valuable and should be recognized. Perhaps we could use italics to emphasize grad students and bold for grads as defaults. I also wonder whether we need a special case for 4+1 students, who inhabit dual roles (often from early on).

Another possibility is to have NO emphasis. One asterisk for undergrad, two asterisks for graduate, and underline or bold for self. (But see below.)

Regardless of what we decide, it should be configurable based on our tastes.

Let me know what you think.

Beyond undergrad, graduate, and myself, please consider:

  • collaborator - defaults to no emphasis
  • industry - defaults to no emphasis
  • postdoc - defaults to no emphasis

Given that our template is in color, we could highlight all of these (by default) with some standard colors but use regular text otherwise.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions