You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
-
This Repo contains the master testbed for Ximera development.
1
+
This Repo contains the test documents for Ximera development.
2
2
It also contains minimal examples and syntax for the Ximera commands, environments, etc.
3
3
However, for a much in-depth treatment of Ximera commands, environments, etc you should
4
-
refer to the Ximera manual, which explains things in more detail and in a more user friendly way.
4
+
refer to the [Ximera User Manual](https://github.com/XimeraProject/ximeraManuals/releases), which explains things in more detail and in a more user friendly way.
5
5
6
6
## Vocabulary:
7
7
**In this repo we use the following terminology**
@@ -92,9 +92,7 @@ test files. To submit a new test file, see the section on ``Creating a New Test
92
92
# Naming Schemes
93
93
94
94
## Each test xourse is named after a dtx file.
95
-
Since all development work must be implemented via dtx file (as per CTAN standards) and most development work
96
-
tends to involve only a few dtx files (usually just one or two), it is often easiest to test the new code by testing
97
-
everything that is implemented by the newly changed dtx code. This testing bed makes that easy to accomplish by merely
95
+
Since development work is implemented via dtx file, we can test new code by
98
96
pulling up the relevant dtxTestXourse(s) and loading the test bed xourse(s) that correspond to your changed dtx file.
99
97
These in turn load all the relevant test files that correspond to the individual elements implemented by that dtx file.
0 commit comments