|
MINOR CREDIT FIELDS (TRANS, LET, COL)
| Which fields are explained on this page? |
col
isscol, isslet, isstrans
let
trans
|
| |
| What are these fields about? |
These field indicate persons who contributed to a publication of a story (translating, lettering, colouring).
These credits are often different for different publications of a story.
Every person name or abbreviation can be mentioned in the persons legend, but that is not mandatory.
The persons legend contains alternative names for the same person (like pseudonyms, misspellings) to make sure the person has the same name everywhere, as much as possible.
If a person was not in the legend, it is added with status "unknown". |
| |
| In which input files are these fields used? |
On entry lines: in DBI files, w.dbi.
On h3 header lines: in DBI files, w.dbi.
|
|
col
| What should the field look like? |
Syntax: [col:xx(xx),xx(xx)] or [col:b/w] or on a h3 line: [isscol:xx(xx),xx(xx)] or [isscol:b/w]
|
| |
| What does the field contain? |
Name of the colo(u)rist of a story, or b/w = black and white.
More than one person can be mentioned.
In cases where the credit is not known for the separate items in the issue, the field is used on the h3 header line. |
| |
| Which log messages are related to this field? |
Log1 (serious)
287: Field ... contains an item (...) more than once
- Every name or abbreviation should occur only once.
299: ... <...> is not in the dbl file and suspiciously short
Log3 (info)
293: ... <...> is an ambiguous name
294: ... <...> should be indicated as <...>
298: ... <...> should be spelled as <...>
- The field is almost right: some spaces or capital letters differ.
|
| |
| Which CSV field(s) use this field? |
Table inducks_entryjob, field doubt
Table inducks_entryjob, field entryjobcomment
Table inducks_entryjob, field personcode
Table inducks_entryjob, field transletcol
Table inducks_issuejob, field doubt
Table inducks_issuejob, field inxtransletcol
Table inducks_issuejob, field issuejobcomment
Table inducks_issuejob, field personcode
|
| |
|
isscol, isslet, isstrans
| What does the field contain? |
| see col, let, trans. |
| |
| Which log messages are related to this field? |
|
None.
|
| |
| Which CSV field(s) use this field? |
|
|
| |
|
let
| What should the field look like? |
Syntax: [let:xx(xx),xx(xx)] or on a h3 line: [isslet:xx(xx),xx(xx)]
|
| |
| What does the field contain? |
Name of the letterer of a story.
More than one person can be mentioned.
In cases where the credit is not known for the separate items in the issue, the field is used on the h3 header line. |
| |
| Which log messages are related to this field? |
Log1 (serious)
287: Field ... contains an item (...) more than once
- Every name or abbreviation should occur only once.
299: ... <...> is not in the dbl file and suspiciously short
Log3 (info)
293: ... <...> is an ambiguous name
294: ... <...> should be indicated as <...>
298: ... <...> should be spelled as <...>
- The field is almost right: some spaces or capital letters differ.
|
| |
| Which CSV field(s) use this field? |
Table inducks_entryjob, field doubt
Table inducks_entryjob, field entryjobcomment
Table inducks_entryjob, field personcode
Table inducks_entryjob, field transletcol
Table inducks_issuejob, field doubt
Table inducks_issuejob, field inxtransletcol
Table inducks_issuejob, field issuejobcomment
Table inducks_issuejob, field personcode
|
| |
|
trans
| What should the field look like? |
Syntax: [trans:xx(xx),xx(xx)] or on a h3 line: [isstrans:xx(xx),xx(xx)]
|
| |
| What does the field contain? |
Name of the translator of a story.
More than one person can be mentioned.
In cases where the credit is not known for the separate items in the issue, the field is used on the h3 header line. |
| |
| Which log messages are related to this field? |
Log1 (serious)
287: Field ... contains an item (...) more than once
- Every name or abbreviation should occur only once.
299: ... <...> is not in the dbl file and suspiciously short
Log3 (info)
293: ... <...> is an ambiguous name
294: ... <...> should be indicated as <...>
298: ... <...> should be spelled as <...>
- The field is almost right: some spaces or capital letters differ.
|
| |
| Which CSV field(s) use this field? |
Table inducks_entryjob, field doubt
Table inducks_entryjob, field entryjobcomment
Table inducks_entryjob, field personcode
Table inducks_entryjob, field transletcol
Table inducks_issuejob, field doubt
Table inducks_issuejob, field inxtransletcol
Table inducks_issuejob, field issuejobcomment
Table inducks_issuejob, field personcode
|
| |
|
|
|
|
