X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~yarrgweb/git?a=blobdiff_plain;f=pctb%2FREADME.charset;h=65aa51aee70e1cf85be1be3229ed8d3dd54df4cb;hb=cfc4716fb0471f32a63072527dc4a462fe73ca99;hp=25eb5d88feb9e6d8ad603533610219eb34c682b5;hpb=c7280e7f26a6fd3685fe96d94c1d76ec77812e57;p=ypp-sc-tools.web-live.git diff --git a/pctb/README.charset b/pctb/README.charset index 25eb5d8..65aa51a 100644 --- a/pctb/README.charset +++ b/pctb/README.charset @@ -50,8 +50,8 @@ We maintain separate dictionaries for the following types of glyph Digits and the greater than sign `>' (which can also appear in the quantity field in the commodity display) Word: - Words (or initial parts of words) which start with `l' - or `I'. + Words (or unambigous initial chunks of words) starting with + `l' or `I' - see the note, below. When you add an entry, you should add it to the appropriate dictionary for its matching context. You can do this by selecting the @@ -140,17 +140,17 @@ errors. If you think you have made mistakes answering OCR queries (for example, the recognised data is wrong), you should delete the file -#local-char*#.txt, which contains your local updates. It will then +_local-char*.txt, which contains your local updates. It will then only use the centrally provided (and vetted) master file (which is automatically updated when you run the PCTB client, by default). It is also possible to have the OCR system reject particular strings. -If you put a regexp in #local-reject#.txt, any OCR result which +If you put a regexp in _local-reject.txt, any OCR result which matches this string will instead cause an OCR failure, invoking the -OCR dictionary editor if appropriate. #master-reject#.txt is the +OCR dictionary editor if appropriate. _master-reject.txt is the centrally maintained version of this file. -Alternatively you can edit #local-char15#.txt with a text editor. The +Alternatively you can edit _local-char*.txt with a text editor. The format is not documented at the moment. @@ -161,7 +161,7 @@ Now that you have read this document, you should rerun your OCR job with the --edit-charset option. So run ./ypp-commodities --edit-charset In future, this option is not usually needed, because it is the -default if there is a local character set dictionary #local-#.txt +default if there is a local character set dictionary _local-.txt for the relevant character height. With --edit-charset, when the OCR finds characters it does not