public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Sebastian Karcher <karcher@u.northwestern.edu>
To: development discussion for xbiblio
	<xbiblio-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Cc: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Problem with "a.k.a." abbreviation in citeproc titles
Date: Thu, 12 Oct 2017 11:19:58 -0400	[thread overview]
Message-ID: <CAOSYSD47a9WBJsn74adu0n9L7PuytQDA0r+_6qXt89=fb0Gkwg@mail.gmail.com> (raw)
In-Reply-To: <20171012145527.GA39195-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 4154 bytes --]

John's interpretation of the specification looks clearly correct to me,
i.e. pandoc-citeproc is behaving according to the specification.
citeproc-js (i.e. Zotero, Mendeley, etc.) actually keeps a.k.a in
lowercase, though, when title casing, i.e. goes beyond/against (depending
on your view) the spec here -- it'd be great if Frank could point to the
exact test or rule he uses and we could consider that for the next
iteration of the specifications. It may just be what John suggests, but I'd
want to see if it captures additional conditions/cases.

(Joseph -- you're aware of the <span class="nocase">a.k.a.</span> wrapper
you can use to disable title-casing? I'm pretty sure that works in pandoc)


On Thu, Oct 12, 2017 at 10:55 AM, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:

> Pandoc follows the CSL docs:
>
> "Title case conversion (with text-case set to “title”) for English-language
>> items is performed by:
>>
>> For uppercase strings, the first character of each word remains
>> capitalized.
>> All other letters are lowercased.
>> For lower or mixed case strings, the first character of each lowercase
>> word
>> is capitalized. The case of words in mixed or uppercase stays the same.
>> In both cases, stop words are lowercased, unless they are the first or
>> last
>> word in the string, or follow a colon. The stop words are “a”, “an”,
>> “and”,
>> “as”, “at”, “but”, “by”, “down”, “for”, “from”, “in”, “into”, “nor”, “of”,
>> “on”, “onto”, “or”, “over”, “so”, “the”, “till”, “to”, “up”, “via”,
>> “with”,
>> and “yet”.
>>
>
> As far as I can see, this says that "a.k.a." should be
> capitalized (even though obviously that's not a good
> outcome).
>
> It seems to me that a good rule would be that any word
> containing an internal period should have its case left
> alone, but it would be good to get feedback from the
> CSL/Zotero side.
>
> +++ Joseph Reagle [Oct 12 17 10:00 ]:
>
>> I'm not sure if the problem is my data, citeproc, or the CSL. The problem
>> is the awkward casing of "A.k.a." when `--style-csl
>> chicago-fullnote-bibliography.csl`:
>>
>> Paul Buchheit, “Applied Philosophy, A.k.a. ‘Hacking’,” Web log message,
>> (October 13, 2009), http://paulbuchheit.blogspot.c
>> om/2009/10/applied-philosophy-aka-hacking.html.↩
>>
>>
>> My data:
>>
>> ---
>> - id: Buchheit2009apk
>>  type: post-weblog
>>  genre: Web log message
>>  abstract: "Developer of Gmail discusses hacking of systems"
>>  author:
>>  - family: "Buchheit"
>>    given: "Paul"
>>  custom2: "lh.mm"
>>  issued:
>>    year: 2009
>>    month: 10
>>    day: 13
>>  title: "Applied philosophy, a.k.a. \'hacking\'"
>>  URL: "http://paulbuchheit.blogspot.com/2009/10/applied-philosophy
>> -aka-hacking.html"
>>  accessed:
>>    year: 2015
>>    month: 07
>>    day: 23
>> ...
>>
>> Should I be somehow escaping punctuated initialisms?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "pandoc-discuss" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/pandoc-discuss/5ae63233-a3d4-79c7-ba13-6ffa62a99d0b%40reagle.org.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> xbiblio-devel mailing list
> xbiblio-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
>



-- 
Sebastian Karcher, PhD
www.sebastiankarcher.com

[-- Attachment #1.2: Type: text/html, Size: 6272 bytes --]

[-- Attachment #2: Type: text/plain, Size: 202 bytes --]

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

[-- Attachment #3: Type: text/plain, Size: 198 bytes --]

_______________________________________________
xbiblio-devel mailing list
xbiblio-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

  parent reply	other threads:[~2017-10-12 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 14:00 Joseph Reagle
     [not found] ` <5ae63233-a3d4-79c7-ba13-6ffa62a99d0b-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2017-10-12 14:55   ` John MacFarlane
     [not found]     ` <20171012145527.GA39195-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-10-12 15:19       ` Sebastian Karcher [this message]
     [not found]         ` <CAOSYSD47a9WBJsn74adu0n9L7PuytQDA0r+_6qXt89=fb0Gkwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-13 13:26           ` Joseph Reagle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOSYSD47a9WBJsn74adu0n9L7PuytQDA0r+_6qXt89=fb0Gkwg@mail.gmail.com' \
    --to=karcher@u.northwestern.edu \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=xbiblio-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).