default, when this happens, the program will stop with a fatal error
and refer you to this document.
-It is possible to fix this by editing the character set database used
+It is possible to fix this by editing the character set dictionary used
by the OCR algorithm. But, it is important to get these inputs right
or your client may misrecognise text in future. You *must* read the
documentation here first.
table. We match from left to right.
We do not insist that each glyph is followed by whitespace, and nor do
-we insist that glyphs do not contain whitespace. Our glyph database
+we insist that glyphs do not contain whitespace. Our glyph dictionary
can contain entries which are strict prefixes of other entries - that
is, a glyph for (say) `v' which is the leftmost part of another glyph
for (say) `w'. We resolve these ambiguities by taking the longest
left-hand half of some letter and thinks it is a different letter. If
the part that it did recognise does look like the letter in question,
that isn't wrong. All you need to do is insert the whole of the
-actual letter in the database - move the LH cursor to the start of the
+actual letter in the dictionary - move the LH cursor to the start of the
letter, and the RH cursor to its end, and hit `return' and enter the
correct character. The longest match rule will mean it will prefer
the entry you have just made.
Upper vs lower case - important note regarding `l' and `I'
----------------------------------------------------------
-We maintain separate databases for upper and lower case. At the
+We maintain separate dictionaries for upper and lower case. At the
beginning of each cell in the table, we expect uppercase; in the
middle of a word we expect lowercase; and, unfortunately, after an
inter-word gap, we are not sure.
So any time we see a word starting with `l' or `I', the program has to
ask about it.
-*Do not* make an entry in the character set database mapping `vertical
+*Do not* make an entry in the character set dictionary mapping `vertical
stick' to `l' or `I'. Instead, select enough of the whole word in
question that no word would start with the other letter, and enter the
whole word or part of it as a new glyph.
-For example, in the supplied database there is already a glyph for
+For example, in the supplied dictionary there is already a glyph for
`Iron'; this is OK because there are no words which start `lron'.
Do not make an entry for a string more than 7 characters long;
*You should check the alleged context before entering a character*.
If it is wrong, you should fix it, rather that just making an entry
-for the uppercase letter in the lowercase database.
+for the uppercase letter in the lowercase dictionary.
Instead, make a new glyph for the last letter of the previous word
plus the (unusually narrow) inter-word space, and end that entry with
Fixing mistakes
---------------
-The OCR query UI allows you to delete things from the glyph database.
+The OCR query UI allows you to delete things from the glyph dictionary.
However since you are not guaranteed to actually get an OCR query at
-all if the database contains errors, you shouldn't rely on this.
+all if the dictionary contains errors, you shouldn't rely on this.
If you think you have made mistakes answering OCR queries (for
example, the recognised data is wrong), you should download a fresh
With --edit-charset, when the OCR finds characters it does not
understand, it will put up an OCR resolution query window. This will
display the part of the text it is having trouble with, showing where
-it has got to, and allow you to edit the character set database it
+it has got to, and allow you to edit the character set dictionary it
uses for recognising the text.
*This is subtle* and it is important to understand the way the
~yarrgweb / ypp-sc-tools.db-test.git / blobdiff