Package: xmedcon / 0.25.1-gtk3+dfsg-1

typos.patch Patch series | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
Description: fix typos caught by lintian
Author: Étienne Mollier <emollier@debian.org>
Forwarded: no
Last-Update: 2022-02-11
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- xmedcon.orig/libs/dicom/README
+++ xmedcon/libs/dicom/README
@@ -23,7 +23,7 @@
  - without jpeg-6a lib dependency
  - use GNU's automake/autoconf/libtool (= libtools convenience library)
  - prevent rescaling of pixel values
- - using define MEDCON_INTEGRATED for a splitted library which: 
+ - using define MEDCON_INTEGRATED for a split library which:
       - enables  to set file stream from outside the lib
       - disables closing of the file stream 
  - changes to use original OFFIS DCMTK dicom.dic dictionary
--- xmedcon.orig/man/m-acr.4
+++ xmedcon/man/m-acr.4
@@ -8,7 +8,7 @@
 We are absolutely lost in standards, versions and ACR/NEMA dialects. Here you can only read how we handle this format. The format is written in one file with extension `.ima'.
 .PP
 .in 0.2i
-The format consists of a group of fields with different elements, in a serie of tags. Does that explain you something? The image data is stored from left to right and from top to bottom.
+The format consists of a group of fields with different elements, in a series of tags. Does that explain you something? The image data is stored from left to right and from top to bottom.
 .PP
 .in 0.2i
 The basic defines for the format:
@@ -326,7 +326,7 @@
 "corkscrew-rule": You must turn from THE AXIS towards THE VECTOR (=angle)
 the same direction so a corkscrew should proceed in the direction
 of an axis orthogonal on the plane formed by THE AXIS and THE VECTOR.
-Well, thats what it should be I think. If your images are tilted, it
+Well, that's what it should be I think. If your images are tilted, it
 will be a bit harder, isn't it?
 
 For the above ECAT 931 acquisition an example value should be:
--- xmedcon.orig/man/m-gif.4
+++ xmedcon/man/m-gif.4
@@ -282,8 +282,8 @@
 .B delay
 The delay in 1/100ths of a second to dispose the present graphic.
 .TP
-.B transparant_color
-This fields represents the color index of the transparant color.
+.B transparent_color
+This fields represents the color index of the transparent color.
 .TP
 .B terminator
 Any clues on this?
--- xmedcon.orig/man/m-intf.4
+++ xmedcon/man/m-intf.4
@@ -63,7 +63,7 @@
 ===========================================================================
 Color Map     : grayscale                                  -
 File Endian   : little or big                              -
-Pixeltypes    : 1-bit, all intergers                       -
+Pixeltypes    : 1-bit, all integers                        -
                 float, double, ASCII
 ===========================================================================
 Scaling factors  : quantify & calibrate factors/image  are NOT supported,
--- xmedcon.orig/man/medcon.1
+++ xmedcon/man/medcon.1
@@ -339,7 +339,7 @@
 
 .TP
 .B \-mosaic, \-\-enable\-mosaic
-Enable mosaic file support in DICOM or Acr/Nema format. The *stamps* will be splitted into separate slices according to values found in the file. This autodetect routine will always fix the voxel sizes. To support other type of mosaic files, see option \-fmosaic.
+Enable mosaic file support in DICOM or Acr/Nema format. The *stamps* will be split into separate slices according to values found in the file. This autodetect routine will always fix the voxel sizes. To support other type of mosaic files, see option \-fmosaic.
 
 .TP
 .B \-n, \-\-negatives
@@ -600,7 +600,7 @@
 
 .TP
 .B \-weu, \-\-write\-encap\-uncomp
-Write DICOM files in "Encapsulated Uncompressed Explicit VR Little Endian" transfer syntax. Instead of all images dumping in one fragment which is limited by a 32-bit length; each image will be written in a seperate encapsulated uncompressed fragment.
+Write DICOM files in "Encapsulated Uncompressed Explicit VR Little Endian" transfer syntax. Instead of all images dumping in one fragment which is limited by a 32-bit length; each image will be written in a separate encapsulated uncompressed fragment.
 
 .in 0.2i
 .SH NOTES
@@ -673,7 +673,7 @@
 .PP
 In case of dual file formats such as Analyze or InterFile, the header information will be send to stderr. The reference to the image file in the header of an InterFile will ofcourse be wrong (since the program is not capable of knowing the resulting filename).
 .PP
-In case of RAW or ASCII output, the program will print the content of the internal FILEINFO struct to stderr as well. Please note that the (t)csh shells do not allow to catch stderr or stdout separately. In case of the bash shell, it is possible to say:
+In case of RAW or ASCII output, the program will print the content of the internal FILEINFO struct to stderr as well. Please note that the (t)csh shells do not allow one to catch stderr or stdout separately. In case of the bash shell, it is possible to say:
 .PP
 .B medcon \-f inputfile \-c - intf \-b16.12 \-qc   1>image  2>header
 .PP
--- xmedcon.orig/source/m-acr.c
+++ xmedcon/source/m-acr.c
@@ -1263,7 +1263,7 @@
            break;
 /* MARK BEGIN: GE DISCOVERY */
        case 0x1001:
-           MdcPrintTag(fi,tag,"Implentation Name            : %s\n",ps);
+           MdcPrintTag(fi,tag,"Implantation Name            : %s\n",ps);
            break;
        case 0x1002:
            MdcPrintTag(fi,tag,"Suite ID                     : %s\n",ps);
@@ -2524,7 +2524,7 @@
            MdcPrintTag(fi,tag,"Laterality                   : %s\n",ps);
            break;
        case 0x0070:
-           MdcPrintTag(fi,tag,"Image Geometrie Type         : %s\n",ps);
+           MdcPrintTag(fi,tag,"Image Geometry Type          : %s\n",ps);
            break;
        case 0x0080:
            MdcPrintTag(fi,tag,"Masking Image                : %s\n",ps);
--- xmedcon.orig/source/m-conc.c
+++ xmedcon/source/m-conc.c
@@ -1898,7 +1898,7 @@
         MdcPrntScrn("     min/max gate cycle:\t%5.3f/%5.3f\n", temp_float, temp_float2);
       }
       if (fi->gdata == NULL)
-        return("CONC gate_inputs line must preceed gate_bins line");
+        return("CONC gate_inputs line must precede gate_bins line");
       if (temp_int >= fi->gatednr)
         return("CONC more gates found then specified in gate_inputs line");
       gd = &(fi->gdata[temp_int]);
--- xmedcon.orig/source/m-files.c
+++ xmedcon/source/m-files.c
@@ -1042,7 +1042,7 @@
   }
 
   if (MDC_FILE_SPLIT != MDC_NO) {
-    /* special naming for splitted files */
+    /* special naming for split files */
     switch (MDC_FILE_SPLIT) {
       case MDC_SPLIT_PER_FRAME:
           sprintf(prefix,"%sf%04u-",cprefix,MdcGetNrSplit() + 1);
@@ -1136,7 +1136,7 @@
 
 }
 
-/* make alias in opath, splitted ipath assumed */
+/* make alias in opath, split ipath assumed */
 void MdcEchoAliasName(FILEINFO *fi)
 {
   MDC_ALIAS_NAME = MDC_YES; prefix[0]='\0';
--- xmedcon.orig/source/m-png.c
+++ xmedcon/source/m-png.c
@@ -252,7 +252,7 @@
       /* copy image rows */
       if (rowbytes != width) {
         png_destroy_read_struct(&png_ptr, &info_ptr, (png_infopp)NULL);
-        return("PNG  Unexpeted number of bytes per row");
+        return("PNG  Unexpected number of bytes per row");
       }
       for (i=0; i<height; i++) {
          pbuf = id->buf + (i*rowbytes);