-
Notifications
You must be signed in to change notification settings - Fork 2
1st crack at re-writing rationale section of TCW31 (update p5subset in Styleseets) #28
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
base: master
Are you sure you want to change the base?
Conversation
TCW/tcw31.xml
Outdated
| bar*</code>, the test would fail.</p> | ||
| </div> | ||
| <div> | ||
| <head>solution</head> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Capitalize: “Solution”
| in the TEI repository does <hi rend="italics">not</hi> put a | ||
| new copy of p5subset.xml into the | ||
| <code>Stylesheets/source/</code> directory. The file needs | ||
| to be manually copied over, hence these instructions for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(At least that is the state of things right now. It really seems strange that we don’t have an automatic process that either moves the built file to Stylesheets or just looks for the built P5 in place. The more I think of it, the more sensible it seems to find a way to automate this with no need for manual copying of files.)
That is just a comment looking forward to yet another revision of this documentation, not suggesting any change here—unless some brief mention of discussions to change all this for the better.
No description provided.