BD layout language application guidance (a)

BD typesetting language has basically been able to meet actual production needs, but it is not perfect. Due to the flaws in the software and the operator's understanding of the functions of the commentary instructions, there are some minor problems that sometimes take half a day or even one day to resolve. Here are some of the software bugs we found in practice and how to overcome them, as well as some of the functions that we usually do not pay attention to, but are very practical.

1. BG annotation

(1) Solve the problem of misalignment between header and table rows

When the number of rows in the table is more than 10 columns, the phenomenon of misalignment between the header and the table can sometimes occur, as shown in Figure 1. This problem is caused by the defects of the typesetting software itself.

As an operator, this encryption software cannot be changed and can only be adjusted as much as possible. For tables with low requirements, it is still possible to adjust the column width parameters of the next header; for tables with higher requirements, it is difficult to adjust with this method. Since the table with a small number of columns can align the header and the table row, we can use the entire table height as a table row height, divide the table into several columns, and then divide each column into multiple table rows. Child table.

The row sample is "[BG(!)[ BHDFG16mm, FK18mm, K24mm, K18mmF][ZB(][BHDWG6mm,K18mmW][BHDG5mm,K9mm,K3mm.3W][BH][ZB)][][ZB(] [BHDWG6mm, K24mmW] [BHDG5mm, K3mm. 8W] [BH]ZZ)[][ZB(][BHDWG6mm,K18mmW][BHDG5mm,K3mm.6W][BH][ZB)][BG)F]" .

It is also possible to divide the multi-column table row corresponding to each column of the head table into one column and sub-tables to divide the small column.

The row sample is "[BG(!][BHDFG7mm,FK18mm,K24mm,K18mmF][BHDG5mm][ZB(][BHDWG5mm,WK9mm,K3mm.3][ZB)][][ZB()[BHDWG5mm,WK3mm, K3mm.7W][ZB)][][ZB(][ BHDWG5mm,WK3mm,K3mm.5W][ZB)][BH][ZB(][BHDWG5mm,WK9mm,K3mm.3][ZB)][][ ZB (] [BHDWG5mm, WK3mm, K3mm. 7W] [ZB)] [ZB () [BHDWG5mm, WK3mm, K3mm. 5W] [HJ1] [ZB)] [BG] F] [HJ]".

(2) Positional relations between [ZB(],[ZB)] and [HT],[HJ] in the table comments

Tables with sub-tables have a row height and a column width that are often referred to as the font size of the core text, and the text in the table is often smaller than the text of the layout. In this case, when the sub-table is annotated, the font size of the core should be restored. [HT] cannot be placed before [ZB(], but before the interval []. That is, when the sample is "...[][HT][ZB(]..." When the sample is "...[HT][][ZB(]...", it is swept; if the font size is changed within [ZB(], the font size is restored before [ZB]), such as "[HT][ZB] ]" Otherwise it is invalid, such as "[ZB]] [HT]".

In particular, it is not possible to have [HT], [HJ], etc. annotations after [ZB]. Although these commentators can be passed through, they will appear in the form sample. Many people cannot find the cause of this phenomenon and have to scrape it off with a blade.

(3) The distance between the quantitative adjustment form and the lower text

After the form is finished, the result of using the word wrap function is that the space between the form and the next line of text is smaller. If you add a line break "", the spacing is too large, and by adjusting the small size to adjust, but also more trouble, it is not easy to adjust to meet the layout requirements. In practice, it is found that the line spacing of the automatic line feed after the form ends is half of the line spacing before the [BG], and accordingly, the line spacing after the automatic line feed of the form can be adjusted quantitatively. For example, if the row spacing after requesting the table to wrap automatically is 2mm, the line spacing is [HJ4mm] before [BG]. The sample is "...[HJ4mm][BG]F][HJ2mm]..."; if the line spacing after the table wrap is required to be half the size of the plate core, the sample is "...[HT][HJ1][BG]F][ HJ]...".

(4) There are vertical rows of texts around the form

The vertical texts on the left and right of the table can be implemented by partitions, columns, or post-process imposition, but it is time consuming to adjust the distance between the text and the table. The simple method is to consider the text on the left and right of the form as a wireless table column up and down, and use the original table body as a table with a child table.

(5) Multi-page form table with table name and header

For multiple pages, the table with the same table name and header is generally set to be copied later. However, if the header is more complex, it will take up more disk space and the modification will be more troublesome. Using the table scrolling function with automatic header, the table name and table header are regarded as a table row, where the table name serves as a wireless sub table row up, down, left, and right. In doing so, after making changes and saving time, the sample will take up less space.

(6) Arrangement of tables with more than 30 columns

For this form, the form can be divided by the method described in (1) above, and the sub-table can be further nested within the sub-table.

(7) Processing method in which the height and width dimensions of the form are a few millimeters zero

For tables with high dimensional accuracy requirements, line (X) can be replaced as a basic unit. The conversion relationship is 1mm=29.2X. If it is required to equally divide 20 table rows within 150.5mm, first convert the total height 150.5mm to 4394.6X (150.5x29.2), and divide it by 20 (4394.6X/20=2197.3X), taking the integer 2197X as Table row height, the error of the entire table is 0.204mm.

2. KG annotations

The typesetting system font (version 6.0) does not have characters, and the spaces are annotated in the negative direction (letters overlap), that is, "â—‹[KG-*6/7]R" can be generated. The generation method is similar to this.

(to be continued)