|
PAGE FIELDS (PAGES, BROKPG, PAGEL)
brokpg
| What should the field look like? |
Syntax: fixed position, or [brokpg:xxx]. If [brokpg:xxx] is used, the fixed position may contain a '+' as well, as an extra indication.
|
| |
| What does the field contain? |
| The amount of broken pages in a story. |
| |
| Which checks are done? |
The field can contain:
- nothing
- a number followed by a "/" followed by a number
- 'h' = 1/2 page.
- 'd' = 1/3 page.
- 'q' = 1/4 page.
- '+' = an unspecified part of a page.
If the field has a value, the pages field should also have a value (that value can be 0).
Do not use spaces in this field. |
| |
| Which log messages are related to this field? |
Log1 (serious)
242: brokpg <...> should be digits/digits or one of +hdq
Log2 (error)
241: brokpg <...> specified while pages is empty (should be 0)
841: Cannot handle brokpg with different denominators in substories
Log3 (info)
442: Pages (...) differ from story file (...) while changes/cut/origpg/part/includedin fields are empty
443: Pages (... ...) differ too much from story file (...) while changes/cut/origpg/part/includedin fields are empty
- In a reprint, we allow a difference of less than 1 page without [changes:] or [cut:], for example: story = 5 7/8 pages and reprint = 6 pages is OK.
490: Unnoticed drastic changes: panels=..., orig panels=... (...)
|
| |
| Which CSV field(s) use this field? |
Table inducks_storyversion, field brokenpagedenominator
Table inducks_storyversion, field brokenpagenumerator
Table inducks_storyversion, field brokenpageunspecified
Table inducks_storyversion, field estimatedpanels
|
| |
| How is the data used in the rest of Inducks? |
| See pages. |
| |
|
pagel
| What should the field look like? |
Syntax: fixed position, or [pagel:xxx]
In FSB files: The value given in the file header: default strisce=xxx. Or on line 5 (or subsequent): [strisce:xxx]
|
| |
| What does the field contain? |
The layout of the page(s) of a story.
The field can contain one or more of the following:
- the number of tiers (1 or 2 digits);
- the number of tiers plus the average number of panels per tier (a letter from 'a' to 'l': a=1, b=2, etc.)
- special layout, one of the following:
- 'i' = illustration
- 'c' = cover
- 'f' = centerfold
- 't' = text
- 'a' = article
- 'g' = game or puzzle
- 's' = strange layout
- 'L' = landscape painting
- 'P' = portrait painting
- '=' = printed sideways (only possible in DBI files)
- '?' = uncertain
The average number of panels per tier is for people who want to be very exact. It is not mandatory.
You could ask the following questions:
- Isn't a cover simply a 1-page illustration ("i") that happens to be on the cover of a comic? (Answer: it is, strictly speaking.)
- What's the difference between a center fold ("f") and a 2-page illustration? (Answer: there is no real difference.)
- What's the difference between "i" and "t"? (Answer: that's a matter of taste. If the illustration is dominant, it's an "i", otherwise it's a "t".
To be decided by the indexer.)
- What's the difference between "a" and "t"? (Answer: an article is about something, while a text piece contains a story with a plot. The distinction is arbitrary, sometimes.)
- What to do with the irregular layouts? (Answer: Sometimes we use "3" if the number of tiers is usually 3. But normally we use "s", meaning "strange layout".)
- What about a single (daily) strip, printed on a text or game page? (Answer: we index it as "0q" pages, with the default-layout (= 4-tier).)
|
| |
| Which checks are done? |
Possible contents:
- ? (= unknown)
- s, c, i, f, g, a, t, L, P (see above)
- = (printed sideways), can also occur behind any of the other options
- 1 to 99, optionally followed by a letter between 'a' and 'l'
By default, the number of tiers per page is assumed 4, the number of panels per tier 2.
If an item has more than 99 tiers per page and/or more than 12 panels per tier, it is to be regarded a "strange" layout ('s'). |
| |
| Which log messages are related to this field? |
Log1 (serious)
243: invalid page layout <...>
Log3 (info)
490: Unnoticed drastic changes: panels=..., orig panels=... (...)
|
| |
| Which CSV field(s) use this field? |
Table inducks_entry, field sideways
Table inducks_storyversion, field columnsperpage
Table inducks_storyversion, field estimatedpanels
Table inducks_storyversion, field kind
Table inducks_storyversion, field rowsperpage
|
| |
|
pages
| What should the field look like? |
Syntax: fixed position, or [pages:xx]
In FSB files: Fourth line, before the 1st '/'.
|
| |
| What does the field contain? |
The number of entire pages of a story (can be zero).
If the page count is not an entire number, the field brokpg should be used for the broken part.
For example, if a story has 3 and three quarters of a page: [pages:3] [brokpg:3/4]. |
| |
| Which checks are done? |
The field must be all numbers, optionally followed by a '?'.
The field should not be empty.
In issue indexes, the field can contain a single '?'. |
| |
| Which log messages are related to this field? |
Log1 (serious)
251e: pages <...> non-digit
- In an issue index, pages must be a number or empty or '?'
253: field <...> non-digit
- The field (in a story index) must be a number or empty or '?'.
Log3 (info)
442: Pages (...) differ from story file (...) while changes/cut/origpg/part/includedin fields are empty
443: Pages (... ...) differ too much from story file (...) while changes/cut/origpg/part/includedin fields are empty
- In a reprint, we allow a difference of less than 1 page without [changes:] or [cut:], for example: story = 5 7/8 pages and reprint = 6 pages is OK.
444: Pages is empty, use '?' or ...
490: Unnoticed drastic changes: panels=..., orig panels=... (...)
|
| |
| Which CSV field(s) use this field? |
Table inducks_storyversion, field entirepages
Table inducks_storyversion, field estimatedpanels
|
| |
| How is the data used in the rest of Inducks? |
| An estimate of the total number of panels of a story is made, also using brokpg and pagel.
This is used to determine whether a reprint of this story was very much changed. |
| |
|
|
|
|
