DBI

Fields in a DBI file:

entry lines: app - hero - xapp - changes - cut - idc - minorchanges - mirrored - missing - part - comment - diznicomment - hiddencomment - art - creatorref - ink - plot - writ - desc - desc-xx - col - isscol, isslet, isstrans - let - trans - brokpg - pagel - pages - enddate - pubdate - startdate - storycode - title - entrycode - includedin - lang - names - phero - re - storycomment - storyitem - xref - creationdate - printedcode - ser - superref - xref - xref
h1 header lines: comment - diznicomment - hiddencomment - locked - maintenanceteam - inxforbidden - isslang - numbersarefake - pages (of an issue) - price - printrun - publ - size - title - altnames (of a publication) - category - circulation - publicationcode
h2 header lines: comment - diznicomment - hiddencomment - locked - maintenanceteam - inxforbidden - isslang - numbersarefake - pages (of an issue) - price - printrun - publ - size - title - circulation - issuerangecode - notinoutput
h3 header lines: comment - diznicomment - hiddencomment - locked - maintenanceteam - col - isscol, isslet, isstrans - let - trans - inxforbidden - isslang - numbersarefake - pages (of an issue) - price - printrun - publ - size - title - attached - collecting - equiv - inx - issdate - issuecode - translating
story lines: app - hero - xapp - comment - diznicomment - hiddencomment - art - creatorref - ink - plot - writ - desc - desc-xx - brokpg - pagel - pages - enddate - pubdate - startdate - storycode - title - keywords - part (in storyitems) - storyparts - usedifferentcode - creationdate - printedcode - ser - superref - xref - xref

Short description:

DBI files

Description:

Below, "positions" are number of characters on a line (including spaces), counting from 1.

This format is used for most issue indexes. A DBI file contains header lines, entry lines, and comment lines.

A header line has the letter 'h' on position 14. A comment line is empty, or starts with a space, or contains two carets next to each other (^^). All other lines are entry lines.

The header and entry lines in a DBI file should be in strict alphabetical order. This means, if you "sort" a DBI file, the output should be exactly like the input, except for the comment lines.

Header and entry lines in a DBI file should not contain TABs or carets (^).
The number of '[' and ']' on a line should be equal.
The number of ')' on a line should be greater than or equal to the number of '('.

Header lines:

After the 'h', the level of the header is given (on position 15). Possible values are 1, 2, or 3. We call these header lines "h1", "h2", and "h3" lines.
"h1" describes an issue series (publication). "h2" describes a subrange of the issue series (for instance a volume of issues). "h3" is the header for one issue.

Fixed position fields:

on position 15: level (1, 2, or 3)
starting on position 1, length 12: publicationcode, issuerangecode, or issuecode (depending on the level)

The title starts on position 17. Other fields (or the above fields, if they don't fit) are behind the title.

Entry lines:

Fixed position fields:

starting on position 1, length 12: entrycode
starting on position 13, length 14: storycode
starting on position 27, length 2: pages
position 29: brokpg
starting on position 30, length 2: pagel
position 32 is ignored
starting on position 33, length 4: plot
starting on position 37, length 4: writ
starting on position 41, length 4: art
starting on position 45, length 4: ink
starting on position 49, length 4: hero

The title starts on position 53. Other fields (or the above fields, if they don't fit) are behind the title.

Log messages:

100: unknown field prefix <...>
101: field ... is defined twice, 2nd value <...> ignored
101a: field desc-... is defined twice
102: strange layout, data will be lost!
103: brokpg specified twice
104: One or more characters are not printable ascii in [...] - This check is not done for header lines, because header lines are spotted because of an 'h' on a specific position. The chance that an 'h' is spotted while the line contains non-printable characters before that is minimal. The check is also not done for legend files (persons/characters).
105: Strange UTF-8 character(s) somewhere in one of the input files
106: Too many or too few brackets or caret or TAB used
107: Unexpected record type in file - This is probably a programming error
108: There is a syntax error in one of the fields

DBI_western

Fields in a DBI_western file:

Short description:

w.dbi

Description:

Below, "positions" are number of characters on a line (including spaces), counting from 1.

This format is used in the file w.dbi. Because most Western comics from before 1985 contain original comic stories, we have a special format for both story data and issue data.

A header line has the letter 'h' on position 11. A comment line is empty, or starts with a space. A reprint line starts with an 'r'. All other lines are story lines.

Header lines:

After the 'h', the level of the header is given, just like in the DBI format.

Fixed position fields:

position 1 ('r' or 'W') and 2 (a space) are skipped.
on position 12: level (1, 2, or 3)
starting on position 3, length 8: publicationcode, issuerangecode, or issuecode (depending on the level)

The title starts on position 14. Other fields (or the above fields, if they don't fit) are behind the title.

Reprint lines and story lines:

Fixed position fields:

In case of a reprint line, positions 1 ('r') and 2 (a space) are skipped.
starting on position 3, length 12: entrycode
In case of a story line, starting on position 1, length 14: storycode
In case of a story line, starting on position 20, length 10: creationdate
In case of a reprint line, starting on position 20, length 13: storycode
starting on position 15, length 2: pages
position 17: brokpg
on position 18: pagel
starting on position 33, length 4: writ
starting on position 37, length 4: art
starting on position 41, length 4: ink
starting on position 45, length 4: hero

The title starts on position 49. Other fields (or the above fields, if they don't fit) are behind the title.

Log messages:

100: unknown field prefix <...>
101: field ... is defined twice, 2nd value <...> ignored
101a: field desc-... is defined twice
102: strange layout, data will be lost!
103: brokpg specified twice
104: One or more characters are not printable ascii in [...] - This check is not done for header lines, because header lines are spotted because of an 'h' on a specific position. The chance that an 'h' is spotted while the line contains non-printable characters before that is minimal. The check is also not done for legend files (persons/characters).
105: Strange UTF-8 character(s) somewhere in one of the input files
107: Unexpected record type in file - This is probably a programming error
112: Line should start with r+space <...>

<< Previous page

(This page was generated by AweGen 5.15 on 2021-03-07)

Next page >>