Graphic technology--Prepress digital data exchange--Monochrome image data on magnetic tape
Some standard content:
GB/T 17156.1 1997
This standard is equivalent to 15010759:1994 Printing Technology—Prepress Digital Exchange
. The equivalent conversion work follows the principles of fidelity, limited scope and inheritance. The purpose of this standard is to specify a unified exchange format when exchanging monochrome image data on tape between electronic prepress processing systems produced by different manufacturers, so that different devices can be connected or networked. This standard is proposed by the Press and Publication Administration of the People's Republic of China and approved by the National Printing Standardization Technical Committee. The originating unit of this standard: China Printing Science and Technology Research Institute. The main drafter of this standard: Li Jiayang.
GB/T 17156. 1---1997
ISO Foreword
[ISO (International Organization for Standardization) is a global standardization specialized organization composed of national standardization bodies (ISO member bodies). The work of developing international standards is done by technical committees of ISO. All member bodies have the right to participate in the work of a committee if they are interested in a standard established by a technical committee. International organizations (official or non-official) that maintain liaison with ISO can also participate in the work: ISO maintains a close working relationship with the International Electrotechnical Commission (IEC) in the field of electrotechnical standardization: draft international standards proposed by technical committees are submitted to member bodies for voting. International standards must be approved by at least 75 member bodies participating in the vote before they can be formally adopted.
International Standard ISO107J9 was developed by the National Standards Association (US Standard Code ANSIIT8.5-1990): It uses the fast track review method and was adopted by the ISO/T130 Printing Technical Committee and approved by the ISO member body. ISO
This international standard has the same technical content as the American Standard 118.5*-1990. At the request of the 1989 ISO/T130 plenary meeting, the ANSI document was distributed to 1ISO members as a fast-track document for comments. After comments were solicited, the text was adjusted based on the second part of the ISO/IECT Working Guide. T8.5 is the result of the joint efforts of an international industry organization including all the major prepress equipment manufacturers in the world. The industry organization was originally called the IDI>ES (Digital Data Exchange Standards) Committee and later became the founding committee of the ANSI T8 (Image Technology) Standards Committee. It is responsible for the prepress industry electronic data exchange standards. The data formats in this standard refer to international standards ISO 010755 and JS 0107561 Scope
National Standard of the People's Republic of China
Graphic technology ---Prepress digital dataexchangt--Monochrome image data on magnetic tape
Graphic technology ---Prepress digital dataexchangt--Monochrome image data on magnetic tape GB/T 17156.1—1997
idtISO 10759:1994
This standard specifies a magnetic tape recording format that can transmit monochrome image data between color and monochrome electronic prepress systems produced by different manufacturers.
2 Conformance requirements
All DIFF standards that meet the requirements of Chapters 6-8, except for the specifically specified No-TIFF and ELJEF requirements, shall be consistent with this international standard. If NonUEF and EUEF are used, they should be written in the specified manner for selective reading. Cited Standards
The following standards contain clauses and constitute the clauses of this standard through reference in this standard. When this standard is used, the versions shown are valid. All standards will be revised. All parties using this standard shall discuss the possibility of using the latest versions of the following standards: GB1988-89 Information Processing Information Interchange - 1-bit Coded Character Set (eVIS) 646: 1983) GB6550-86 Information Processing Interchange 9 Track 12.7mm Width 63 Lines/mm Phase Modulation Recording Magnetic Tape (elVIS)/IHC:3788:1976)
GB 7571-87
Information processing exchange tape label and text structure (mIS) 100]: [979GB9715-88 Information processing information exchange microtrack, 12.7mm (0.in) end-recording tape 32ftpmm (800 (pi) NR21, 12 (iftpmm (3200fipi) phase modulation 356fipmm (9u42ftpi) NRz1 (idtIS01864:19853
Information processing information exchange 9 track, 12.7mm (0.5im) tape period encoding method 216:pmmm) (G3 936388
(6250epi) format and record requirements (-v15) 5652:1984) 4 Definitions
This standard adopts the following definitions
4.1 Digital Data Exchange Standard (T)FS: A method of digitally encoding information shared between cooperating systems. 4.2 User Exchange Format (UEF) A system's native format for implementing the requirements of this standard. 4.3 Extended User Exchange Format (EuUEF) An optional format that a system can implement beyond the features of UUEF. 4.4 Non-User Exchange Format NotI-LEF
Approved by the State Administration of Technical Supervision on December 16, 1997 and implemented on August 1, 1998
GR/T 17156. 1 -- 1997
Formats not defined in this standard but defined by the manufacturer: 4.5 Decimal Point Numbering The nolaion is in the form of a string of digits in a numeric field (positions 3/0 to 3/9 in GB 1988), with an optional decimal point (positions 2/14 in CGB 1988).
5 Symbols and abbreviations
This standard uses the following symbols and abbreviations:
BP: byte position in the label, to be consistent with (7574), the byte position starts at 1. I Field length in byte position:
Format or h: coded character in position 0 of GB 1988-892. 0. coded character in position 3/0 of GB 198889 6 General requirements
6.1 Basic requirements
IEF3 version is the basic condition for the exchange of monochrome images 6.1. 1 Monochrome images
Single packets of image data exchanged as defined in EF03 shall consist of a rectangular array of picture elements ("picture patterns"), where the pixels have different intensities and are coded as specified in 7.3.1. The intended effect is to create a monochrome image using different intensities of the specified image colors.
6.1.2 Binary images
Binary image data exchanged as defined in LFF(3) shall consist of a rectangular array of picture elements ("picture patterns"). Each pixel shall be coded as specified in 7.3.1. 3.2 Definition: It is a solid, transparent image, or background color. Note: The source and characteristics of binary images have many prerequisites. Typical examples include photos that have been screened, line drawings, certain digital text or geometric graphic data:
6.1.3 Binary line images
Binary line data exchanged according to EF3 definition consists of a rectangular array of image elements (\pixels). Each pixel should be encoded as specified in 7.3.3. It can be a solid, transparent image or background color. Method: Binary line image data is further summarized by continuous areas of both graphics and color images. Use \spatial information (dlithering) or \error diffusion\ (errordiffusion) techniques without simulating the range of measured values (single tone value). Therefore, the spatial information (satial information) is suitable for \spatial information encoding (lu run lernglh enuding) lechairues), these techniques can reduce file size and allow for faster processing. 6.2
DDESOO tape
The tape is identified as DLES (BP44~47) version 00 (1P50-51) by the volume header mark of volume 1. The tape should be written as specified in this standard. No other values are allowed in the 1EF or EUEF fields. The only fields that can be used for undescribed purposes are the "system reserved fields (for manufacturers) and the manufacturer's UHL% (RP0480). All other fields should be written as specified in this standard or GB757. The fields defined in this standard are written as (B 7574) and the media as specified in B9716. D[ES microstrip should be written as 1600hpi phase coding according to GB6550 or 6250bpi group coding according to GB9363.
6. 3. The use of ELUJEF format (Extended User Interchange Format) is optional, but the codes specified in the technical standard should be used. 6.4 Non-UEF (Non-UEF Interchange Format)
Non-UEF segments are also specified in TIFS. The use restrictions of these fields and values are the same as those of EUEF segments. 6.5 Specification of UEF, ELUFF and Non-UEF formats CB/T 17156.1
BP05 to 10 of the user header identifier (UHL1) are used as UIEF markers. These fields are encoded in other ways as described in 7.2.4. 6.6 Segment padding www.bzxz.net
All numeric fields should be right-aligned and filled with "0", and any character fields should be right-aligned and filled with "zero". 6.7 Use of user header identifiers
UHL1, UHL2, UHL3, and UHL4 have been defined in this standard. and UHI.4, there are 24 additional IIH1s reserved for use in UJHL2: 6 for future use by IDES (BP31), 9 for other purposes that will be completed (BF32), and 9 for commercial use (BP33). The values of IESUHL (BP04) are unique and ordered, and the numbers are from 1 to g, and "A" and "B" are reserved for TT>FS: 6.8 Mixed tape formats
There can be different UEF tape file formats in a standard DIES tape or a volume group, and a DDES tape can contain FUEF and Non-EUFF file formats
7ESO0's tape header identifier
The following case describes how to use the GB7574 tape format: 7.1 General tape format
Table 1 shows the format of two monochrome image files on a tape. Table 2 shows the format of two monochrome image files on two tapes. This standard supports the use of redundant tapes for a file group, including the decomposition of an image file onto multiple tapes, which is described in HIR!.
Table 1 The format of two single image files on a tape HOT
Physical tape mark (start of tape)
Capture mark
File mark of next file|
File mark of next file
File mark of next file 2
Next file user tape mark 1
Next file user tape mark 2
Next file user tape mark
Next file user tape mark 1
File mark of next file 5
Can be specified in Appendix III of UII.2(1~3)
Logical tape mark
End of file mark 1
End of file mark 2
User tape mark:
CB/T 17156. 1—1997
Table 1 (end)
Physical tape mark (beginning of tape)
Volume header mark
\Tape tail mark4
User tape tail mark5
The TF (user tail) corresponding to each TJHI (user header) is on the tape. These labels do not need to be read out. UT1, followed by EOF1 and EOF2, which are copied from the previous LHL (dead 8. 1
File name of next file 2
User band identifier of next file 2
User band identifier of next file 3
User band identifier of next file 4
User band identifier of next file 5
Transition tape mark
Image data
Logical section mark
End of file identifier 1
End of file Bundle identifier 2
Yawen tape tail identifier 1
User tape tail identifier 2
User tape tail identifier 3
User tape tail identifier 4
User tape tail identifier 5
Remote tape mark
Tumeng file 2
Transparent tape mark (logical tape knot)
Physical tape mark (tape bundle)
Table 2 Format of two monochrome image files on two tapes The first tape
Physical tape mark (microstrip start)||tt| |Volume header mark
File header mark of the next file 1
Next File identifier of the file 2
G/T17156.1-1997
Table 2 (continued)
First ether band
Physical magnetic non-mark (band start)
Old header mark
User band mark of the next file 1
Next User band header mark of the file 2
Next User band header mark of the file 3
Next File uses...band mark
Next A file's tape identifier 5
Reverse track tape mark
Image data
Edit tape mark
File end mark 1
Text end mark 2
User tape identifier 1
Application tape identifier 2
Application tape end mark 3
Application tape layer mark 4
User tape identifier 5
Logical tape mark
Next file segment file start mark 1
Next file segment file start mark?
User band identifier of next file segment 1
User band identifier of next file segment 2
User band identifier of next file segment 3
User band identifier of next file segment 4
User band identifier of next file segment 5
Edition band mark
Image data
Image file 2 part
Physical micro-transmission mark (band end request)
Arrangement tape mark
End of volume identifier 1
Volume end identifier?
User tape identifier 1
User tape header identifier 2
User tape header identifier 3
User tape end identifier 4
GB/T 17156. 1
Table 2 (end)
First tape segment
Physical tape mark (tape start)
Beginning of volume identifier
User tape identifier 5
Logical tape mark
Reverse tape mark (logical tape end)
Second tape segment
Physical node mark (tape start)
Beginning of volume identifier
Next file segment file header identifier 1
File header identifier of next file segment 2
User tape header identifier of a file segment!
User band head identifier 2 of next file segment
User band head identifier 3 of next file segment
User band head identifier 4 of next file segment
User band identifier 5 of next file segment
Logical tape mark
Data
Logical tape mark
End of file identifier 1
End of file identifier 2
User band tail identifier 1
And user band identifier?
Used Band Identifier 3
Used Band End Marker 4
User Band Identifier 5
Logical Tape Marker
Image File 2 Part 1
Logical Tape Marker (Logical End of Tape) Physical Tape Marker (End of Tape)
7.2 Beginning of Tape Marker
The following 1 specifies the beginning of tape marker for [[ES00 UEF03 tape. Except as specified here, there shall be no optional formats or fields in DDES00.
7.2.1V0L1
Table 3 specifies the byte position, field name, field length and content of the ticket header identifier 1. GB/T17156.1
The tape sequence in the same volume group is specified by RP48~19, starting from \1\ and increasing by 1 for each tape Table 3 Volume header identification 1 (VO1.1)
01--04
05--16
12~-37
38--43
44~-47
52--79
Field name
Identifier and serial number of the label
Identifier
Volume accessibility
Reserved for GB 7571 use
Date of establishment (G 7574 format)
[)J)FS error identifier
Serial number of the tape in the volume group
131ES Version
Book(7574 7.2.2 File header identifier 1 (HDR1) Table 4 shows the byte position, field name, field length and content of file header identifier 1: Contents: *VOLIt "DDES" "00" The contents of the file identifier (BP0521), generation number (BP36~39) and generation version number (LBP40~41) can be different in different operating systems. These fields do not take into account the communication between manufacturers' systems. The file group identifier (BP22--27) does not include the job name of DDES. The job name is included in the user header identifier 1 (see Table 6). When the phase II is not defined, the corresponding field is followed by five or six zeros with a space. (See BP48~53 in Table 4). Table 4 File header identifier 1 (FHILRI) 05 --21
22--27
32~-35
40-*41
28-~53
Field name
Identifier and sequence number
File identifier
File assembly identifier
Segment number
File sequence number
Generation number
Generation version number
File creation period
File expiration date (optional)
File accessibility
Block count
Reserved for the system (for manufacturer use)
Guaranteed for GB 7571
7.2. 3 File Header Identifier 2 (HDR2)
Table 5 specifies the byte position, field name, field length and content of File Header Identifier 2 (HIR2). P1650 (System Use/Vendor Use) is for each manufacturer to use, not for communication between manufacturer systems. Content
01--04
(16-11)
11--15
1G-~50
53--80
GB/T 17156.1—1997
Table 5 File identifier 2 (HD) R2)
Segment name
Identifier and sequence number
Record format - Fixed length
Block K (UEF specified)
Record length (UEF specified)
Reserved for system use (manufacturer use)
Record length
Reserved for GB 7574
7. 2. 4 User header identifier 1 (UHI1)
Table 6 specifies the byte configuration, field name, field length and content of user header identifier 1: BP05~10 is the identifier of LUFF, there are several different cases; UEF b 03
\ELEF03"
\bhbho3\
User exchange format for monochrome images
Extended UEF file
Non-LUEF file
All other names should be reserved for future use. BP11~30 are used for the name of the manufacturer who issued this tape. Each manufacturer should use a dedicated name. Table 6 User tape header 1 (UHL.1)
01--02
05 ~-10
-~ 301
31--40
Field name
Identifier and sequence number
UEF identifier
"Trade name
Program name
Job name
Image name
7.2.5 User Band Header 2 (UHL2)
7 specifies the byte position, segment name, field length and content of the User Band Header 2. BP25-28 specifies the type of file on the tape. Label type:
"{000*0002\—Reserved for other uses of other DDES—Monochrome image (UEF):
*0003"
0004\—
Binary image ( UEF);
\0005\.~\0099\ reserved for future use by DDES;s*00997
Manufacturer's list
*HTR2"
\08102\
\08162"
BP3I, BP32 and BP33 specify the number of UHIs on the tape, the order is first all TDIESUHIs, then all "other future use" UIILs, and finally all manufacturers' UJHIs. This order is related to the identification number of each UHL: the numbers or letters in the identification number field (HP04) have no special meaning, and there is no specific order (except T)DESUFII. defined in 6.7). BP34~35 specify the number of blocks before the first line of image data in the image file. Manufacturers can use this area for special months. The values of BP36~80 are usually spaces.
65~-24
25~-28
29~~30
Identifier and sequence number
Department name
File type
GB/T 17156. 1-1997
Table 7 User header identifier 2 (LHIL2)
Field name
System use (general use)
Additional ES LIIL number
:-3CUHL3 to UHL5)
Other IHIs to be used in the future
Number of IHIs (determined by the manufacturer)
Offset to the start of data (number of blocks)
(determined by the manufacturer)
Reserved for [2]>1-5 Will not be used
7.2. Table 8 of the User Broadband Header Identity 3 (UHL3) (Parameter Area) specifies the slice location, field name, field length and content of the User Broadband Header Identity 3. Table 8 User Band Identifier 3 (UIIL3)
t:1~-t4
25--28
20---32
33--42
53-~~58
59--64
G9·--74
75~80
7.2.6.1 Data Specification
Identifier and Number
Data Format
Color Separation Number
Field Name
Color Sequence (First Part)
Color Sequence (Second Part), Always Space for LIEF, Can Also Be EUJFF Use
Byte value of center dot
Byte value of 100% dot
Line length (pixel line) (decimal, mm)Field width (seventh decimal, m)
Number of pixels per line (length)
Number of lines (width)
Orientation (positive or negative)
Line resolution units (optional)
\I\_Pixels per inch, \M\_Meters Unit of image width resolution (optional)
\I"He Ying} number of pixels, "M\=meter number of pixels Line resolution expressed in decimal points (optional) Width resolution expressed in decimal points (optional) HP05~6 of LIHI.3 contains the following values: ";?20\-monochrome image format:
binary graphic format;
\22". Binary line format.
7. 2. 6.2 Color sequence
The color sequence specified for the color components controlled by UHI.4 should be "YMCK\ or "CMYK\, as specified in HP09~12 of UHI.3 For UEF, BP13-- 24 is always a space. HUJEF is optional and can be based on L:HI.3P07-24 of 3 can handle up to 16 colors in various color sequences. The valid input values of the color plate number field BP07-08 are from "01\ to "16\, representing 1 to 16 colors. Valid input to the color sequence field may be any of the following sequences: yellow, magenta, cyan and black colors,
\Y\\M\\C\\K\
\R\\G\\R\
red, green, green brightness,
U\"V\\[.\—CIE I976 starting chromaticity U, V and attenuation (Y>\}\ to\g\
user defined color or color separation version. For example, pink, etc. "Q" ... are on the tape but ignored.
Color descriptors shall be consecutive, left-justified, and padded with spaces. 7.2.6.3 Color Values
Color values used to describe image and background colors shall be determined using unsigned data values. These data values are in the digital format C:B 1988 in IJHL4 and (HI.5) and range from 0 to 255. The relationship between the data value and the actual color component value should be linear and should be determined by the creator of the file. However, in the same file, all colors and color components are the same. The size of the gradient, the slope and the distance between the two points are specified in this way, that is, the data related to the color component value (0% to 100% points) are expressed by the numerical symbols in HP25~28 and 13P29~32 of UHL3 (according to GB1988).
Figure 1 shows the conversion relationship of color values. Here the value of 0% dot is 20, and the value of 00% dot is 220. 100
7.2.6.4 Maximum direction of monochrome image
(8%- 20)
(100%-220
Data value
Example of color value conversion
Monochrome image length and width are defined in BP33~-54 of HL3. Figure 2 shows the relationship between these parameters (13P6$~66). The position and direction of the arrows indicate the order of the pixels in the first row of the tape file (monochrome or binary images) or the pixel encoding row in the first row (binary line images). The length refers to the length of the first row of data in the image file. , the width refers to the distance of the data line distribution, alun:
Figure 2 The relationship between the first line of data, image acquisition time and IIEF orientation code UEF slope is specified in the following way (see Figure 2): "O0\. Load horizontally from the upper left corner (UEF) \OI" - load vertically from the upper left corner (UFF) "02" - load horizontally from the lower left corner (UFF) *03\ - load vertically from the lower left corner (UEF) UEF requires that it can be loaded in one orientation, but can be read in all orientations. 03
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.