-
Notifications
You must be signed in to change notification settings - Fork 769
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Pull all macros into a custom documentclass #2256
Comments
For what it's worth, most proposals are probably easier to process (and live-edit in session) as HTML than in LaTeX, and our Standard LaTeX environment isn't really suited to formatting diffs and edit instructions. Finally, I hate "finished proposals" that are "incorrekt and incomplet"! |
Baseline assumption:
So the people who'd be benefitting from this would largely be the people maintaining the draft itself. @godbyk, what advantages are there to us of converting from .tex files to a document class? How does that affect the maintenance of our macros and style rules? |
@zygoloid The primary advantage is just in the organization. All the formatting/style code then lives in a single file instead of being scattered across half a dozen files. It also helps us separate content from presentation. I did some initial work consolidating the files and code into a (Note that the |
Editorial meeting:
|
I propose consolidating much of the preamble of
std.tex
and the contents of thelayouts.tex
,styles.tex
,macros.tex
, andtables.tex
files (and perhaps a few others) into a newstd.cls
document class.This would make it easier for proposals to reuse the same macros and format as the standard and streamline integration of accepted proposals into the standard.
I'm happy to do the work on this if it sounds like a good idea.
Thoughts?
The text was updated successfully, but these errors were encountered: