Benjamin W. Bohl
Benjamin W. Bohl
Is there a need of controlling elision direction otherwise I would consider to close this issue?
as closing marks issues as completed and moves them "out of sight" I reopened this and Moved it to the MEI 5.x Milestone backlog instead.
As `@color` does not seem to be restricted to, e.g., transcriptional matters, I don't see a reason not to add it. Consequently, I wonder if there is a reason not...
I was rather thinking in the direction of: * getting rid of `@color` everywhere * making `@rend` or another attribute capturing such information globally available and extending its data model...
Or even introduce something like `tei:rendition` that is used to define a rendition style centrally and is referenced with `@rendition` where applicable.
Can we agree on @pe-ro's proposal?
Adding the following line to the steps: * Checkout SCHEMA_REPO into SCHEMA_DIR * Check git status before commit * Configure git * Commit files * Push changes to SCHEMA *...
Issuing the build process on PRs without checkout of the guidelines and schema repositories and without the push actions to the respective repos would do the job. The build artifacts...
I guess having all of them would be the right thing to do, but then again the action should also be triggered on `synchronize` to rerun each time new changes...