1. Change `add-acmart-styles` to add an element WITHOUT the `pretitle` style
for the collects phase. With this, an empty `#lang scribble/acmart` document
builds an empty PDF.
2. Add documentation for a "minimal" `scribble/acmart` document.
Moving the contracts to the original exports ensures that the bindings
from both modules are the same. In particular, making the bindings
different caused the documentation to have missing links.
Change LaTeX implementation of `@title` to just use `\title` --- don't try to extract a subtitle.
- - -
This fixes a bug, where the `Title` meta-data in the PDF for a document titled
"Foo" was "oo" (same title with first letter missing). So, e.g., Google chrome
would show "oo" as the tab title for the document.
- - -
Why not try to fix subtitle extraction?
1. I don't think we need it in `scribble/acmart`, because there's a separate `@subtitle` command
2. Not sure how to extract a subtitle without using `\let` inside `\title`, but doing so generates 2 LaTeX warnings:
```
Package hyperref Warning: Token not allowed in a PDF string (PDFDocEncoding):
(hyperref) removing `\<let>-command' on input line 674.
Package hyperref Warning: Token not allowed in a PDF string (PDFDocEncoding):
(hyperref) removing `\SSubtitle' on input line 674.
```
The "visual" bug was probably due to this warning; after removing the `\let`
and `\SSubtitle` then only `\SubtitleDrop` and the actual title are left.
I guess `\SSubtitleDrop` removed the first character of the title.
(Why only the first character? I don't know.)
The LaTeX warning from `hyperref` is probably because acmart expects the
argument to `\title` to be a raw string. Though, the docs don't explicitly
say this. They only say "It is expected that this command [`\title`] is inserted
by the author of the manuscript."
add contracts to location-formatting functions,
and make sure those functions convert their inputs to strings,
and fix a documentation bug in `techrpt-location`
Handle comma-separated Last,First and Last,Jr,First format for names in bibtex, as well as "von", "de la", "van de", and other separators that start with lowercase letters
These commands work like natbib's citeauthor and citeyear commands,
and facilities making possessive citations. For example:
> Thanks to @(cite-author foo)'s (@(cite-year foo)) paper on stuff...
These identifiers are added with `define-cite` as keywords, and thus
can be omitted with no downside for backwards compatibility.
@(define-cite cite citet generate-bib
#:cite-author cite-author
#:cite-year cite-year)
Also in this commit:
* Add documentation.
* Add tests for autobib
* Bump version and add history.
Fixes an incompatibility between jfp1.cls and the 'relsize' package.
Justification for the fix:
1. `pdflatex` fails on this document
```
\documentclass{jfp1}
\begin{document}
\maketitle
hello {\Large world}
\end{document}
```
2. `pdflatex` succeeds on this document
```
\documentclass{jfp1}
\renewcommand\Large{\@setfontsize\@xvpt{18}}
\begin{document}
\maketitle
hello {\Large world}
\end{document}
```
I do not know why (1) fails.
The new line in (2) is copied from `jfp1.cls`.
In places where module names are typeset, such as `racketmodname`,
there's no way to disable the special treatment of `_` as an
identifier prefix as in `racket`. Even using
`make-element-id-transformer` doesn't work, because the module-name
datum is explcitly disconnected from binding withing `racketmodname`.
* Prevent hyphens from appearing in @racket[...] identifiers when they overflow.
* Add SHyphen command.
A style file can redefine SHyphen to toggle how they want to
hyphen their text
* Add documentation
* Add a pretitle style property for nested flows.
This allows us to raise nested flows above the title. So that we do
things like raise the abstract above the title:
```
\begin{abstract}
Abstract text
\end{abstract}
\titleCommand{...}
```
This style is required by the acmart style guide.
* Paragraphs and nested flows extracted in the same order
* Fix `scribble/acmart`'s abstract form so that it gets lifted above `maketitle`, where it should be.
The relative-path computation assumed that a relative path was
always possible, but a relative path can't go from one drive
to another.
Also, the relative-path computation didn't take into account
case-insensitivity, so it failed in a different-drive way
when the drive case was different between two paths.
Closesracket/racket#1625
While done as a tex hack, macros in latex can have multiple optional
arguments. As such, we should support it with command-optional.
Meaning that the type of command-optional-arguments is now (Listof String)
The existing scribble/acmart language in this repo felt more like latex than Scribble. This package brings scribble/acmart more inline with the existing `scribble/acmart` package that was already on the package server. In particular, this commit:
* Remove maketitle from scribble/acmart
* Extends the title form to also have the fields in `scribble/base`'s title.
* Support author information. (Like scribble/sigplans authorinfo)
* Removed unneeded functions now redundant due to the author function. Namely, affiliation based ones.
* Factor out common functions to scribble/acmart and scribble/base into private module.
These functions might make sense to be public, but since they were already private in base
I thought it made sense to leave them that way. Additionally, it might make sense to have the
file be something other than private/tag, as private/tag currently requires tag, which is
different than the normal way where its tag that requires private/tag.
* Add short-title to scribble/latex-properties
* Adds an `command-optional` property which is like `command-extras`, but is a single
optional argument placed before the mandatory ones.
* Create email, affiliation, and institution structs so that authors can have multiple of each.
* Add/improve documentation and history (and bump version number).
Just like the 10pt option in `scribble/sigplan`,
putting @9pt @10pt @11pt or @12pt on the #lang line of a `scribble/acmart`
document passes to corresponding string to `\documentclass[....]`
And just like TeX, it's ok to give multiple font sizes. All but the last
are ignored.
The function bound to `make-my-notes` by `define-footnote` (as in:
```
(define-footnote my-note make-my-notes)
```
) now produces a part with the `unnumbered` style.
This way, footnote sections can go between any two sections on a page
without upsetting the section numbers.
