Multiple fixes to titles

[GeeLaw]

Issue 1. The name "Turing" should always have a capitalized "T".

A quick search over crypto.bib reveals the following cases: Turing (47 not followed by s), Turings (1), {Turing} (7), "Turing (3). According to Tame the BeaST, the correct encoding is {T}uring, regardless of where this word appears. The recommended fix is to do the following regular-expression replacements:

1. title =(.*?) Turing (leading space is significant to avoid replacing booktitle) replaced by title =$1 {T}uring repeatedly until there are no more occurrences (the word "Turing" might appear multiple times in a title). The replacement count should be 47+1.
2. \{Turing\} replaced by {T}uring. The replacement count should be 7.
3. title =(\s*)"Turing replaced by title =$1"{T}uring. The replacement count should be 3.

Issue 2. The first word after colons are often misencoded. For example, ACISP:LMOQ22 is currently encoded as {TIDE}: {A} Novel Approach to Constructing Timed-Release Encryption, but {A} should really be A. BibTeX "t" change.case$ (title casing) will not change the first letter after a colon followed by a space (see @<Perform the case conversion@>= in bibtex.web).

I am not sure if there is a compatibility reason for forcing the case after a colon (maybe some users use a BibTeX style that does not handle the word after a colon correctly). Also, it seems to require an enormous amount of effort to fix this, because one has to determine whether the first word following the colon is a proper phrase (e.g., {TM}: {T}uring Machine and {UTM}: Universal {T}uring Machine are correct). Therefore, currently I do not have a fix proposal.

Issue 3. The title of ICALP:Harel12 is misencoded. It should be (capitalization of "A" and "M", in addition to capitalization of "T")

Standing on the Shoulders of a Giant - One Persons Experience of {T}urings Impact (Summary of the {A}lan {M}. {T}uring Lecture - Invited Talk)

The work, as published by Springer, indeed writes "Persons" and "Turings" instead of "Person’s" and "Turing’s". I am also not sure whether hyphen-minus (-) or en dashes (--) or em dashes (---) should be used.

The title of CCS:Hellman16 is also misencoded. It should be (capitalized "A")

Cybersecurity, Nuclear Security, {A}lan {T}uring, and Illogical Logic

Issue 4. The title of EC:JLMS19 has a typo. The word is "over", not "overa".

Issue 5. The titles of some works jointly authored by me (Ji Luo). In the following, it is normal that different versions of the same work have different abbreviation/capitalization of certain parts.

• EPRINT:LinLuo20a should preserve lowercase "k" and capital "L" in "k-Lin":

Compact Adaptively Secure {ABE} from {k}-{L}in: Beyond {NC1} and towards {NL}

• AC:LinLuo20 should preserve capital "L" in "k-Lin":

Succinct and Adaptively Secure {ABE} for {ABP} from {$k$}-{L}in

• EPRINT:LinLuo20b should preserve lowercase "k" and capital "L" in "k-Lin":

Succinct and Adaptively Secure {ABE} for Arithmetic Branching Programs from {k}-{L}in

• EC:GonLuoWee23 should preserve capital "N", and lowercase "k" and capital "L" in "k-Lin".

Traitor Tracing with ${N}^{1/3}$-Size Ciphertexts and ${O}(1)$-Size Keys from {$k$}-{L}in

• EPRINT:GonLuoWee23 should use math for "O(1)", and preserve capital "L" in "k-Lin".

Traitor Tracing with {${N}^{1/3}$}-size Ciphertexts and ${O}(1)$-size Keys from {$k$}-{L}in

Updates

2023-07-24. Corrected a typo in suggested fix, improved suggested fix.

[GeeLaw]

Since there are 2 logical groups of issues, I created two separate pull requests. I've tested that both can be merged into the current master branch in arbitrary order for the same final result.