Browse Source

- fixed typos

tags/v0.2.4
Jakub Wilk 2 years ago
parent
commit
ce282c45c5
5 changed files with 5 additions and 5 deletions
  1. +1
    -1
      README.1st_checkit
  2. +1
    -1
      README.TIFFrisks
  3. +1
    -1
      README.TIFFspecification
  4. +1
    -1
      README.grammar
  5. +1
    -1
      README.regex

+ 1
- 1
README.1st_checkit View File

@@ -7,7 +7,7 @@ hardcoded rule set with predefined values, you are able to define tags and
corresponding values more fine granulary. The rulesets are human readable and
could be adapted to own needs.

The "checkit_tiff" works on commandline and therefore it is embedable in scripts
The "checkit_tiff" works on commandline and therefore it is embeddable in scripts

The tools are developed for purposes of curation and longterm preservation


+ 1
- 1
README.TIFFrisks View File

@@ -14,7 +14,7 @@ Each tag in the array is 12 Bytes long. The first 4 bytes indicate the tag itsel
In the TIFF specification, there are some hints which help us to repair broken TIFFs.

The first hint is that all offset-addresses must be even.
The second importand rule is that the tags in an IFD must be sorted in an ascending order.
The second important rule is that the tags in an IFD must be sorted in an ascending order.

At last, the TIFF spec defines different areas in the tag range. This is to guarantee that the important values are well defined.


+ 1
- 1
README.TIFFspecification View File

@@ -5,7 +5,7 @@ This affects also the tags used for EXIF data. Our interpretation is, if you hav

== offsets on word boundary ==

The specification is very clear. Offsets should only point to odd adresses. We think this is important for longterm preservation, because it makes the TIFF format more robust and repairable if some bit flipping occurs.
The specification is very clear. Offsets should only point to odd addresses. We think this is important for longterm preservation, because it makes the TIFF format more robust and repairable if some bit flipping occurs.

== tags in ascending order ==


+ 1
- 1
README.grammar View File

@@ -3,7 +3,7 @@ About general function

The checkit-tool validates TIFF-files against a set of rules (see below). The
set of rules works as a whitelist. This means that TIFF tags that are used in
the file but not explicitely checked by a specific rule (not considering if
the file but not explicitly checked by a specific rule (not considering if
successful or not) are not allowed. In cases where a rule is executed only
if a predicate is set, the tag is only allowed if the predicate check succeeded.


+ 1
- 1
README.regex View File

@@ -1,6 +1,6 @@
= RegEx =

the program uses the pcre-library for regular expressions in ascii mathcing
the program uses the pcre-library for regular expressions in ascii matching
rules (in config file).

If you use a regex similar to "^[:print:]*$" it does not match on

Loading…
Cancel
Save