Pikchr

A few typos I spotted in the docu and elsewhere
Login

A few typos I spotted in the docu and elsewhere

(1) By anonymous on 2023-07-23 11:14:07 [source]

Hi,

thanks for providing Pikchr, very useful.

I spotted a few typos in the project which I would like to report. Hopefully they can be fixed:

diff --git a/doc/macro.md b/doc/macro.md
index 73017a7..0c8e72e 100644
--- a/doc/macro.md
+++ b/doc/macro.md
@@ -33,7 +33,7 @@ an identifier that is the name of the macro and then the body of
 the macro contained within (possibly nested) curly braces.
 
 After a macro is defined, the body of the macro is substituted in
-place of any subsquent occurrence of the identifier that is the
+place of any subsequent occurrence of the identifier that is the
 macro name.  The macro name can occur anywhere.  The substitution
 is performed by the lexical analyzer, before tokens are identified
 and sent into the parser.  Note this distinction:  The "`define`"
diff --git a/doc/pathattr.md b/doc/pathattr.md
index 454173b..76ab5cf 100644
--- a/doc/pathattr.md
+++ b/doc/pathattr.md
@@ -132,12 +132,12 @@ line invis color gray from X.start to 2nd vertex of X \
     "1cm below Obstacle.s" aligned small
 line invis color gray from 2nd vertex of X to 3rd vertex of X \
     "right until even with Destination.s" aligned small above
-line invis color gray from 3nd vertex of X to 4rd vertex of X \
+line invis color gray from 3rd vertex of X to 4th vertex of X \
     "to Destination.s" aligned small above
 
 # Evidence that the alternative arrow is equivalent:
 assert( 2nd vertex of X == (Origin.s, 1cm below Obstacle.s) )
-assert( 3nd vertex of X == (Destination.s, 1cm below Obstacle.s) )
+assert( 3rd vertex of X == (Destination.s, 1cm below Obstacle.s) )
 ~~~
 
 The "**(** *position* **,** *position* **)**" syntax can be used
diff --git a/pikchr.c b/pikchr.c
index c0050c3..c21f3a2 100644
--- a/pikchr.c
+++ b/pikchr.c
@@ -236,7 +236,7 @@ struct PRel {
 
 /* A variable created by the ID = EXPR construct of the PIKCHR script 
 **
-** PIKCHR (and PIC) scripts do not use many varaibles, so it is reasonable
+** PIKCHR (and PIC) scripts do not use many variables, so it is reasonable
 ** to store them all on a linked list.
 */
 struct PVar {
@@ -6884,7 +6884,7 @@ static void pik_after_adding_attributes(Pik *p, PObj *pObj){
     ** center of a line is the center of its bounding box. In PIC, the
     ** center of a line is halfway between its .start and .end.  For
     ** straight lines, this is the same point, but for multi-segment
-    ** lines the result is usually diferent */
+    ** lines the result is usually different */
     for(i=0; i<pObj->nPath; i++){
       pik_bbox_add_xy(&pObj->bbox, pObj->aPath[i].x, pObj->aPath[i].y);
     }
diff --git a/pikchr.y b/pikchr.y
index 555e644..a584f7e 100644
--- a/pikchr.y
+++ b/pikchr.y
@@ -235,7 +235,7 @@ struct PRel {
 
 /* A variable created by the ID = EXPR construct of the PIKCHR script 
 **
-** PIKCHR (and PIC) scripts do not use many varaibles, so it is reasonable
+** PIKCHR (and PIC) scripts do not use many variables, so it is reasonable
 ** to store them all on a linked list.
 */
 struct PVar {
@@ -4277,7 +4277,7 @@ static void pik_after_adding_attributes(Pik *p, PObj *pObj){
     ** center of a line is the center of its bounding box. In PIC, the
     ** center of a line is halfway between its .start and .end.  For
     ** straight lines, this is the same point, but for multi-segment
-    ** lines the result is usually diferent */
+    ** lines the result is usually different */
     for(i=0; i<pObj->nPath; i++){
       pik_bbox_add_xy(&pObj->bbox, pObj->aPath[i].x, pObj->aPath[i].y);
     }

Thanks for considering my input.

Andreas

(2) By Stephan Beal (stephan) on 2023-07-23 11:58:20 in reply to 1 [link] [source]

I spotted a few typos ...

These have been fixed. Thank you for the report.