Skip to content

Conversation

@Alex-Jordan
Copy link
Contributor

@Alex-Jordan Alex-Jordan commented Jul 1, 2023

This pairs with openwebwork/webwork2#2099 that refactors hardcopy themes.

Part of that refactor is cleanly separating:

  • tex packags and macros that supports PG directly
  • tex packags and macros that webwork2 uses for hardcopy production
  • tex packags and macros that a particular theme needs

This PR moves everything of the first flavor over to the pg repo. Now in theory something other than webwork2 can fully process individual problem files via tex to PDF, without needing something from the webwork2 repo.

@Alex-Jordan
Copy link
Contributor Author

I was wondering if it makes sense to move the contents of PGML.tex and CAPA.tex into pg.sty to make sure that file is closer to self-contained.

Copy link
Member

@drgrice1 drgrice1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good (paired with openwebwork/webwork2#2099 of course).

@drgrice1 drgrice1 merged commit 53d6365 into openwebwork:PG-2.18 Jul 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants