You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ocrd_utils/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,12 +9,12 @@ See https://github.com/OCR-D/core
9
9
10
10
File-based control over logging facilities is done with standard [Python 3 logging module configuration files](https://docs.python.org/3.6/howto/logging.html#configuring-logging). This way, the level, format and destinations of log messages can be customized for all OCR-D modules individually and persistently, in the usual syntax.
11
11
12
-
A template configuration file (with commented examples) is included in [ocrd_logging.conf](./ocrd_logging.conf). This is meant as an example, and should be **customized**.
12
+
A template configuration file (with commented examples) is included in [ocrd_logging.conf](./ocrd_logging.conf). This is meant as an example, and should be **customized**.
13
13
14
14
To get into effect, you must put a copy (under the same name) into:
15
-
1. your current working directory,
15
+
1. your current working directory,
16
16
2. your user directory, or
17
-
3.`/etc`.
17
+
3.`/etc`.
18
18
These directories are searched in said order, and the first find wins. When no config file is found, the default logging configuration applies (which uses only stdout and the `INFO` loglevel for most loggers, cf. [here](./ocrd_logging.py)).
19
19
20
20
Thus, a configuration file will override *all* settings from the default configuration, and from configuration files in lower-priority directories.
@@ -23,7 +23,7 @@ For more information about logging, handlers and formats, see [Python documentat
23
23
24
24
#### Docker containers
25
25
26
-
In the Dockerfiles used to build `ocrd/core` (and subsequently `ocrd/all`), the above mentioned template is directly copied to `/etc/ocrd_logging.conf` within the container image. This cofiguration is thereby also the default configuration for OCR-D containers.
26
+
In the Dockerfiles used to build `ocrd/core` (and subsequently `ocrd/all`), the above mentioned template is directly copied to `/etc/ocrd_logging.conf` within the container image. This configuration is thereby also the default configuration for OCR-D containers.
27
27
28
28
Thus, if you want to customize logging rules in one of these Docker containers, you can create a custom configuration file and either:
29
29
- place it into your local workspace directory when running the OCR-D container.
Copy file name to clipboardExpand all lines: ocrd_validators/ocrd_validators/mets.xsd
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -211,7 +211,7 @@
211
211
3. Add an MDTYPEVERSION attribute as a companion to the MDTYPE attribute in the mdRef and mdWrap elements.
212
212
4. ID and STRUCTID attributes on the behavior element made optional. Depending on whether the behavior applies to a transformFile element or div elements in the structMap, only one or the other of the attributes would pertain.
213
213
5. Documentation aligned with the METS Primer, and corrected.
214
-
6. xml:lang="en" atttribute value added to every <documentation> element
214
+
6. xml:lang="en" attribute value added to every <documentation> element
215
215
7. xlink:extendedLink support added to the <structLink> element by means of a new <smLinkGrp> element, and its child <smLocatorLink> and <smArcLink> elements.
0 commit comments