This is Bolderbast.Inducks.org, part of the inducks.org website.

On this page:
DBS
DBS_newspaper
DBS_feuilleton
DBS_movies
DBS_newspaperissue
 

DBS

Fields in a DBS file:
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
story header lines: comment - diznicomment - hiddencomment - storyheadercode - storyheadercountry - title
 
Short description:
DBS files
 
Description:
Below, "positions" are number of characters on a line (including spaces), counting from 1.

This format is used for most story indexes.

A header line has the letter 'h' on position 15 and a '0', '1', or '2' on position 16.
A comment line is empty, or starts with a space.
All other lines are story lines.

Header and story lines in a DBS 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:
Fixed position fields:

The title starts on position 18.
 
Story lines:
Fixed position fields:
  • starting on position 1, length 14: storycode
  • starting on position 15, length 2: pages
  • position 17: brokpg
  • starting on position 18, length 2: pagel
  • position 20 is ignored
  • starting on position 21, length 4: plot
  • starting on position 25, length 4: writ
  • starting on position 29, length 4: art
  • starting on position 33, length 4: ink
  • starting on position 37, length 4: hero


The title starts on position 41. 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

DBS_newspaper

Fields in a DBS_newspaper file:
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
story header lines: comment - diznicomment - hiddencomment - storyheadercode - storyheadercountry - title
 
Short description:
y.dbs and z.dbs
 
Description:
Below, "positions" are number of characters on a line (including spaces), counting from 1.

This format is used in the story files y.dbs and z.dbs, where newspaper strips are stored.
The format is like the DBS format, except the positions of the fixed fields on the story lines are different.

Fixed position fields on story lines:
  • starting on position 1, length 12: storycode
  • starting on position 4, length 8: pubdate (yy-mm-dd, the century is assumed to be "19")
  • starting on position 13, length 8: enddate (yy-mm-dd, the century is assumed to be "19")
  • starting on position 22, length 4: writ
  • starting on position 26, length 4: art
  • starting on position 30, length 4: ink
  • starting on position 34, length 4: hero
Note that pubdate and storycode are partly obtained from the same positions.
The title starts on position 38.
 
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!
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

DBS_feuilleton

Fields in a DBS_feuilleton file:
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
story header lines: comment - diznicomment - hiddencomment - storyheadercode - storyheadercountry - title
 
Short description:
yzsuper.dbs
 
Description:
Below, "positions" are number of characters on a line (including spaces), counting from 1.

This format is used in the story file yzsuper.dbs, where newspaper sequence strips ("feuilletons") are stored.
The format is like the DBS format, except the positions of the fixed fields on the story lines are different.

Fixed position fields on story lines:
  • starting on position 1, length 8: storycode
  • starting on position 10, length 8: pubdate (yy-mm-dd, the century is assumed to be "19")
  • starting on position 20, length 8: enddate (yy-mm-dd, the century is assumed to be "19")
  • starting on position 29, length 4: writ
  • starting on position 33, length 4: art
  • starting on position 36, length 4: ink
  • starting on position 41, length 4: hero
The title starts on position 45.
 
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!
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

DBS_movies

Fields in a DBS_movies file:
movies.dbs lines: app - hero - xapp - comment - diznicomment - hiddencomment - storycode - title - special date fields for movies - special fields for movies - special people fields for movies
 
Short description:
movies.dbs
 
Description:
Below, "positions" are number of characters on a line (including spaces), counting from 1.

This format is used in the file movies.dbs.
The format is like the DBS format, except the positions of the fixed fields on the story lines are different.

Fixed position fields on story lines:
  • starting on position 1, length 13: storycode
  • starting on position 15, length 4: hero
The title starts on position 19.
 
Log messages:
100: unknown field prefix <...>
101: field ... is defined twice, 2nd value <...> ignored
102: strange layout, data will be lost!
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

DBS_newspaperissue

Fields in a DBS_newspaperissue file:
 
Short description:
reprint lines in y*.dbs and z*.dbs
 
Description:
Below, "positions" are number of characters on a line (including spaces), counting from 1.

This format is used in the newspaper story files, to read lines that indicate reprints of newspaper strips.
These lines are indicated by:
  • A space on position 1 (so in this exceptional case there are NOT comment lines!);
  • Two = (so "==") somewhere on the line;
  • Any fields starting at position 15.


Fixed position fields:
  • on position 1: a letter (char1) that is used in the entry code;
  • starting on position 3, length 8: pubdate
  • on position 11: another letter (char2) that is used in the entry code;
The actual entry code is derived automatically, like it is also done for other newspaper entries in the same files. Publication date and char1/char2 are used for this.
 
Log messages:
   
<< Previous page (This page was generated by AweGen 5.7 on 2017-11-12) Next page >>