JPH0481894A - Outline data processing device - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

DETAILED DESCRIPTION OF THE INVENTION Field of the Invention The present invention relates to an outline data processing device that stores outline data of a plurality of characters such as letters, numbers, symbols, etc., and outputs the outline data as necessary. In particular, it relates to a technique for reducing the storage capacity required to store outline data.

2. Description of the Related Art The outline data processing device described above is used, for example, in a character output device that prints characters on a print medium or displays them on a display screen.

An example of this character output device includes (a) an outline data memory that stores, for each character, outline data of a plurality of characters each defined by one or more outlines (one closed line); and (b) (C) data conversion means for converting each outline data into dot data; (d) outline data supply means for supplying outline data corresponding to the character to the data conversion means;
The apparatus includes a character output means for outputting a character to an output medium based on the dot data converted by the data conversion means.

In traditional character output devices, each outline of each character consists of multiple segments (straight or curved).
In the outline data memory, segment data defining each segment belonging to each outline is stored for each segment. Characters were always stored in segments.

However, through research conducted by the present applicant, it has been found that it is not always desirable to store characters in units of segments, and there are cases where it is desirable to store characters in units of segment rows. Based on this knowledge, the applicant has devised an outline data processing device that includes an outline data memory, data generation means, and outline data output means. Outline data memory stores segment column data that defines a specific segment column among multiple segments into which each outline of a character is divided, and stores segment column data that defines that segment column for each segment column. , the segment data that defines each segment is stored for each segment I, and the data generating means is configured to generate data corresponding to each segment column based on the segment column data stored in the outline data memory. Generates segment data,
The outline data output means outputs outline data consisting of the segment data generated by the data generation means and the segment data stored in the outline data memory.

Problems to be Solved by the Invention The present applicant subsequently conducted research on reducing the storage capacity for storing outline data with respect to the outline data processing device devised above (hereinafter simply referred to as the devised device), and as a result, the following results were obtained. The following facts were discovered. Among the multiple segments that make up each outline of a character, there are specific segment rows that are connected to each other with a certain relative positional relationship.
It has been found that it is possible to compress a plurality of segment data defining a plurality of segments constituting the segment data using the above-mentioned fixed relative positional relationship, that is, the graphical property regarding the specific segment column, and If the above-mentioned compressed segment data (this is the form of "r segment string data in the devising device") is stored in the outline data memory instead of segment data, the storage capacity for storing the outline data can be reduced. It has also become clear that savings can be made.

Based on the above findings, the present invention provides an outline data processing device that is an embodiment of the devising device and is capable of reducing the storage capacity required to store outline data by using graphic properties. This was done with the goal of doing so.

Means for Solving the Problems The gist of the present invention is to, as shown in FIG. For those that store compressed segment data for each segment column, the segment data that defines each segment belonging to that segment column is compressed using the graphical properties related to that segment column, while for other segments, (b) an outline data memory 1 that stores segment data that defines each segment; and (b) the outline data memory 1.
(C) data restoration means 2 for restoring each compressed segment data stored in the memory 1 into segment data using graphical properties; and (C) segment data restored by the data restoration means 2 and outline data stored in the memory 1. and outline data output means 3 for outputting outline data consisting of segment data.

Function: In the outline data processing device according to the present invention,
Of the multiple segments that make up each outline, for those that make up a specific segment column, compressed segment data in which the segment data is compressed using the graphical properties is stored for each segment column, while other segments , segment data is stored for each segment. When outputting outline data, compressed segment data is read from the outline data memory for those that constitute a specific segment among multiple segments, and the compressed segment data is The segment data is restored, and outline data consisting of the restored segment data and the segment data stored in the outline data memory is output.

Effects of the Invention Therefore, according to the present invention, segment data defining a specific segment string is compressed using graphic properties and stored in an outline data memory, so that the storage capacity for storing outline data is reduced. This has the effect of being done.

Embodiment Hereinafter, an embodiment suitable for applying the present invention to a data conversion device for converting outline data into dot data among laser printers will be described in detail with reference to the drawings.

FIG. 2 is a diagram mainly showing the portion related to data conversion of the control circuit of the laser printer.

The computer 10 that forms the main body of this control circuit is a CPU
12. Character ROM14. Program ROM16
Text memory 18 Working memory 20. It is equipped with a dot data memory 22 and the like. These CPUs 12 and the like are connected to each other by a bus 26, and an input device 30 and a printing section 32 are connected to this bus 26. The input device 30 supplies necessary data to the computer 10, and the printing section 32 is a section that performs printing using a laser printing method based on signals from the computer 10.

The program ROM 16 stores various control programs including data conversion routines shown in flowcharts in FIGS. 3 and 4.

The character ROM 14 stores original outline data for defining outlines of a plurality of kanji characters in association with index code data.

Each of the one or more outlines defining a Kanji is divided into a plurality of segments, each of which is a straight line or a Bezzer curve.

When a kanji is defined by one outline, the original outline data of the kanji is a set of unit outline data that defines that one outline and a kanji end flag, and when a kanji is defined by multiple outlines. In this case, the original outline data of a kanji is a set of a plurality of unit outline data defining each outline and a kanji end flag. Further, each unit outline data is composed of start data, straight line data, Bezier curve data, compressed vertical character data, compressed tank vertical character data, compressed rectangular data, and an outline end flag.

The start data is the starting point S (hereinafter referred to as
This defines the outline starting point S). Therefore, as shown in Fig. 5, the start data consists of a flag lSl indicating that it is the start data, and start point data indicating the Xy coordinates (hereinafter simply referred to as coordinates) of the outline start point S. There is.

On the other hand, straight line data is used when each segment is a straight line to define that straight line. Therefore, as shown in FIG. 5, the straight line data consists of a flag L1 indicating that it is straight line data, and end point data indicating the coordinates of the end point E of the straight line. Note that the straight line data does not include starting point data representing the coordinates of the starting point S of the straight line. This is based on the fact that the starting point S of this straight line is defined by the starting data or coincides with the ending point E of the segment preceding the straight line, so that the ending point E is the starting point of the straight line in question. This is because it is used as S.

This situation also applies to Bezier curve data, compressed vertical glyph data, compressed vertical glyph data, and compressed rectangular data.

A Bezier curve has its starting point S, ending point E, and control point Q.
, , Q2 and a predetermined Bezier curve function. Therefore, as shown in FIG. 5, the Bezier curve data includes a flag B° indicating that it is Bezier curve data, first control point data indicating the coordinates of the control point Q, and coordinates of the control point Q2. It consists of second control point data representing the end point E and end point data of the end point E. Note that the Bezier curve function described above is stored in the program ROM1.
6 is stored. That is, in this example,
The start data, straight line data, and Bezier curve data are each segment data.

A portion of each outline of a kanji character may include a column of vertical glyph-shaped segments shown in FIG. 6 and a string of horizontal glyph-shaped segments shown in FIG. 9. In each of these segment rows, straight line segments extending in the X-axis direction and straight line segments extending in the y-axis direction are connected to each other. Specifically, the vertical glyph segment row is as shown in FIG.
■ A straight line extending from the segment row starting point S in the positive or negative y-axis direction (vertical direction) to the ending point E! L, and ■extend from the end point E in the positive or negative X-axis direction (lateral direction) to the end point Ez (
On the other hand, as shown in FIG. 9, the horizontal segment line extends from the segment line start point S in the positive or negative X-axis direction and reaches the end point. A straight line L2 extends from the end point E1 in the positive or negative y-axis direction to the end point E2 (which is also the end point of the segment row).

Therefore, a plurality of segment data (hereinafter simply referred to as dead line glyph data) defining the ML glyph segment string
is a straight line, as shown in Figure 7.

Straight line data [flag L', coordinates of end point E (x
o, )'+)) and the straight line data [flag 'L'', coordinates (x+, y+) of the end point E2] that define the straight line L2. S
However, the segment preceding the vertical segment string is character ROM1.
4, the end point of the preceding segment is used as the start point of the vertical segment string.

In any case, the starting point 5 (
xo, yo) are stored in the character ROM 14. Further, this situation is the same for horizontal glyph segment rows and rectangular segment rows to be described later.

As is clear from FIG. 6, the coordinate X must be used to uniquely determine the vertical segment string. .

It is sufficient to know the values of X+, yo and yl.

However, when storing a vertical 15-character segment string in the character ROM 14 as segment data, the coordinates x0
and y are stored redundantly, which is wasteful. Therefore, in this embodiment, for the vertical glyph segment string, as shown in FIG.
The compressed vertical glyph data (the dead line glyph data is compressed), which is a set of The coordinate X of the end point E of the segment string. The coordinate X0 of the starting point S of the segment row is used as the coordinate yI of the end point E1, and the coordinate yI of the end point E2 is used as the coordinate yI of the end point E1. In this way, by using the properties of a rectangle, it is possible to compress dead line glyph data into compressed vertical glyph data with a smaller amount of data.

On the other hand, the plurality of segment data (hereinafter simply referred to as the original horizontal glyph data) defining the horizontal glyph segment string are the first
As shown in FIG.
Straight line data defining straight line L2 (flag 'L°, end point E
Coordinates of t □ (Xl.

y, )]. As is clear from Figure 9,
In order to uniquely determine the horizontal glyph segment string, it is sufficient to know the coordinates X6 + XI + yo and y, but when storing the horizontal glyph segment string as segment data in the character ROM 14, are the coordinates X, and y.

are stored redundantly, which is wasteful. Therefore, in this embodiment, for the horizontal glyph segment string, as shown in FIG.
The compressed i is a set of end point data (x+y,) of 2.
The L-shaped data (the original horizontal character data compressed) is stored in the character ROM 14, and the horizontal 1
The coordinate X of the end point E2 is used as the coordinate X of the end point E of the single-character segment string, and the coordinate y of the end point E is used. The coordinate y0 of the segment row starting point S is used in the following. In this way, by using the properties of a rectangle, it is possible to compress the original horizontal glyph data into compressed board glyph data with a smaller amount of data.

Further, each outline of a kanji may be composed of four sides of a rectangle. An example of this is the two outlines that define the kanji ``口''. Each outline may be a series of rectangular segments. In addition, the direction in which multiple segments are traced for each outline is, in principle, counterclockwise, but if there is another outline inside one outline, such as the kanji ``mouth'', the inner outline is set to follow in a clockwise direction. Examples of rectangular segment rows are shown in FIGS. 12 and 13, respectively. 12th
The figure is an example of a rectangular segment sequence that is traced in a counterclockwise direction, and FIG. 13 is an example of a rectangular segment sequence that is traced in a clockwise direction.

In this embodiment, a certain rule is provided for the position of the starting point S of the rectangular segment sequence so that the rectangular segment sequence is traced in a predetermined direction. This rule is that if you want the rectangular segment sequence to be traced counterclockwise, select the starting point S as the lower left point among the four vertices of the rectangle, and if you want the rectangular segment sequence to be traced clockwise, The starting point S is selected as the upper left point among the four vertices of the rectangle.

Both of the two rectangular segment rows, which are traced in different directions, extend from the starting point 5 (xo, yo) in the positive or negative X-axis direction to the ending point E, (x,).

yo); ■ A straight line L2 extending from the end point E1 in the positive or negative y-axis direction to the end point Ez (X+, y+); and ■ A straight line L2 extending from the end point E2 in the positive or negative y-axis direction. , extends in the opposite direction to the end point Eff (χ
. , y, ); and (2) a straight line L4 extending from the end point E3 in the direction opposite to the straight line L2 among the positive and negative X-axis directions and reaching the starting point S. The reason why the format of the segment data for defining a rectangular segment string can be the same regardless of the direction in which it is traced is due to the above-mentioned rule for selecting the starting point S. Therefore, as shown in FIG. 14, the segment data that defines a rectangular segment string (hereinafter simply referred to as redundant rectangular data) is: - Straight line data that defines straight line L1 [flag L", coordinates of end point E (x+, yo )) and ■ straight line L2
Linear data that defines [flag L°, coordinates of end point E2 (
χy+)), ■straight line data that defines straight line [flag °L'', coordinates (xo, y) of end point E3], and ■straight line 1a
It is a set of straight line data [flag ゛L゛9 coordinates of starting point S (xo, yo)] that define L.

As is clear from FIGS. 12 and 13, in order to uniquely determine the rectangular segment row, the coordinates XO,
Although it is sufficient to know each edge of 1+ yo and yl, when storing a rectangular segment string as segment data in the character ROM 14, the coordinates Xo r
X+ + yo and yl are each stored redundantly, which is wasteful. Therefore, in this embodiment, for a rectangular segment string, as shown in FIG. End point data (x,.

y+) is stored in the character ROM 14, and the coordinates of the end point E1
1, the coordinate X+ of the diagonal end point E2 is used, the coordinate y0 of the start point S is used as the coordinate y0 of the end point E1, and the coordinate X of the end point E3 is used. The coordinate x0 of the starting point S is used as the coordinate yI of the end point E3, and the coordinate y1 of the diagonal end point E2 is used as the coordinate yI of the end point E3. In this way, by using the properties of rectangles, it is possible to compress original rectangular data into compressed rectangular data with a smaller amount of data.

As is clear from the above description, in this example, [
The L-shaped segment string, the horizontal glyph segment string, and the rectangular segment string are not the dead line glyph data, the original horizontal glyph data, and the original rectangular data, which are segment data, but the compressed vertical glyph data, which is compressed segment data. Since the compressed tank rectangular data and the compressed rectangular data are stored in the character ROM 14, the storage capacity required to store these segment strings in the character ROM 14 is small.

The outline end flag *'' indicates the end position of each outline in the original outline data of each kanji, and the kanji end flag 1!9 indicates the end position of the original outline data of each kanji. .

Therefore, for example, for the kanji character "A" shown in FIG. 16, the original outline data shown in FIG. 17 is stored in the character ROM 14.

The text memory 18 stores text data (including a set of a plurality of index code data) supplied from the input device 30, and the working memory 2
0 is where data necessary for program execution is temporarily stored.

The dot data memory 22 stores dot data converted by the data conversion routine.

Next, a description will be given of how the original outline data is converted into dot data by executing the data conversion routine.

The CPU 12 sequentially reads the index code data one by one from the text memory 18, and executes the data conversion routine of FIGS. 3 and 4 only once for the index code data. In this routine, first, in step SL (hereinafter simply referred to as SL; the same applies to other steps), the first flag of the original outline data stored in the character ROM 14 corresponding to the current index code data is is read out.

After that, in S2, it is determined whether the flag is 9*(end of outline)''. If so, the result of the determination is YES, the process returns to Sl, and a new flag following the previous flag is created in Sl. The flag is read, but
Otherwise, the determination result in S2 becomes No, and in S3, the current flag is set to °! (end of kanji) It is determined whether or not it is °.

If we assume that this is not the case this time, the result of the determination will be NO, and in S4, the current flag will be set to °T (vertical shape) °
It is determined whether or not. If so, the result of the determination is YES, and in S5, the compressed vertical glyph data related to the current flag is read from the character ROM 14, and then the compressed vertical glyph data is restored to the dead line glyph data. . Using the coordinates Xo, yo (these do not exist in the compressed IL shape data but are stored in the character ROM 14) and the coordinates X++ y+ of the end point E2, the straight line data of the straight line and the straight line data of the straight line L2 are calculated. The set is obtained as dead line glyph data. After that, it moves to SIO.

On the other hand, if the current flag is not T°, S
The determination result in step 4 is NO, and in S6, the flag is set to “
It is determined whether or not it is Y (horizontal character)°. If so, the result of the determination is YES, and in S7, the compressor glyph data corresponding to the current flag is the character R.
After being read from the OM 14, the compressed glyph data is restored to the original glyph data. Coordinates xo, yo (these do not exist in the compressor glyph data but are stored in the character ROM 14) and the coordinates Xl+ of the end point E2
y+, the straight line data of straight line L1 and straight line L
The set with the straight line data of 2 is obtained as the original board shape data. After that, the process moves to S10.

If the current flag is not “Y”, the determination result in S6 is NO, and in S8 it is determined whether the flag is “0°”. If so, the judgment result is YES
In S9, the compressed rectangular data corresponding to the current flag is read from the character ROM 14, and then the compressed rectangular data is restored to the original rectangular data. Using the coordinates Xo, yo (these do not exist in the compressed rectangle data but are stored in the character ROM 14) and the coordinates xl+y+ of the diagonal end point E2, the straight line data of the straight line L1, the straight line data of the straight line L2, and the straight line A set of straight line data of L3 and straight line data of straight line L4 is obtained as original rectangular data. After that, it moves to SIO.

If the current flag is not '0', the determination result in S8 is NO, and the process immediately moves to S10.

In SIO, ■After executing S5, the restored original NL shape data (a set of two straight line data) is stored in the segment data buffer 20a provided in the working memory 20, and the number N of straight line data in it (this time The data representing 2) is stored in the counter 2 provided in the working memory 20.
0b, and after executing S7, the restored original board glyph data (a set of two straight line data) is stored in the segment data buffer 20a, the number of straight line data N (in this case 2). The data representing the straight line data is stored in the counter 20b, and after the execution of ■S9, the restored original rectangular data (a set of four straight line data) is stored in the segment data buffer 20a, the number N of straight line data (this time The data representing 4) is stored in the counter 20b, and
■If after the NO decision in S8, the start data, straight line data, or Bezier curve data is stored in the segment data buffer 2.
0a, and data representing the number N (1 in this case) of that data is stored in the counter 20b. After that, 311 in Figure 4
to move to.

At 311, the flag of any segment data (start data, straight line data, or Bezier curve data) is read from the segment data buffer 20a, and S
At step 12, it is determined whether the flag is 'S (start)°. If so, in S13, the start point data stored following the flag in the segment data buffer 20a is read out, and in 314, the start point data is scaled (the printing point size of the kanji is set by the operator). (adapting to the desired size) one rotation, transformation processing such as font conversion from normal to italic is performed. After that, the process moves to S23.

On the other hand, since the flag this time is not S゛, 31
If the determination result in step 2 is NO, it is determined in S15 whether or not the flag is "B (Bezier curve). If so, in 316, the current flag is stored from the segment data buffer 20a. Out of the corresponding Bezier curve data, the end point data and the first and second control point data are read out, and in S17, the end point data, etc. are subjected to the deformation process, and then in 318, the Bezier curve is It is expanded into short vectors. The Bezier curve is approximated by a plurality of short straight lines. Thereafter, the process moves to 323.

Also, if the current flag is not l B +, S
The determination result in step 15 is NO, and in step 319 it is determined whether or not the flag is at °L°. If so, the result of the determination is YES, and in S20, the end point data is read out of the straight line data corresponding to the current flag from the segment data buffer 20a, and then in 321, the end point data is modified as described above. Processing takes place. Thereafter, the process moves to 323.

Also, if the current flag is not “L”, S19
The determination result is NO, and after error handling is performed in S22, one execution of this routine ends.

In S23, the start point data, end point data, etc. obtained as described above are stored as changed outline data in the changed outline data memory 20c provided in the working memory 20, and then in S24,
It is determined whether the number of times n of execution of this step is smaller than the number N of segment data stored in the counter 20b. If so, the determination result is YES and Sl
Otherwise, the result of the determination is No, and in 325, the segment data buffer 20a and the counter 20b are cleared. Thereafter, the process returns to 81 in FIG.

For example, if the original glyph data is currently stored in the segment data buffer 20a and counter 20b, the number of stored segment data is 2, so the execution of steps 311 to S24 is repeated twice, and , when redundant rectangular data is currently stored, the number of segment data is 4, so the execution of SL1 to S24 is repeated four times, and when straight line data is currently stored, segment data Since the number of is 1, Sll
- S24 will be executed only once.

While the steps explained above are executed repeatedly, 33
If the determination result is YES, each modified outline data stored in the modified outline data memory 20c is converted into dot data in S26. Note that this data conversion is explained in detail in Japanese Patent Application No. 1-52524 previously filed by the present applicant, so the explanation will be omitted here. The converted dot data is stored in the dot data memory 22.

This completes one execution of this routine.

When this routine is executed for all the index code data stored in the text memory 18, the dot data creation for the text data stored in the text memory 18 is completed. Thereafter, when the operator issues a printing command via the input device 30, the printing unit 32 is controlled based on the dot data, and as a result,
Text is printed on print media.

As is clear from the above explanation, in this example,
The character ROM 14 constitutes the outline data memory 1, the part of the computer 10 that executes steps 84 to S9 in FIG. 3 constitutes the data restoration means 2, and the parts 810 in FIG. The portion that executes steps S24 to S24 constitutes the outline data output means 3.

Although the above embodiment is an example in which the present invention is applied to an outline data processing device for a laser printer, the present invention can also be applied to an outline data processing device for other types of printers. It may be applied to an outline data processing device for.

Although one embodiment of the present invention has been described above in detail based on the drawings, various modifications and variations may be made based on the knowledge of those skilled in the art.
The invention can be practiced in modified forms.

[Brief explanation of the drawing]

FIG. 1 is a block diagram conceptually showing the configuration of the present invention. FIG. 2 is a block diagram showing a data conversion device that is an embodiment of the present invention. Figures 3 and 4 are, respectively,
3 is a flowchart showing a portion of the control program stored in the program ROM in FIG. 2 that is closely related to the present invention. FIG. 5 is a diagram for explaining the structure of the original outline data used in the above embodiment. FIG. 6 is a diagram showing an example of the vertical character segment string used in the above embodiment, FIG. 7 is a diagram showing the L-shaped segment string as segment data, and FIG. 8 is a diagram showing the vertical character segment string being compressed. It is a figure shown by segment data. FIG. 9 is a diagram showing an example of a horizontal glyph segment string used in the above embodiment, FIG. 10 is a diagram showing the horizontal glyph segment string as segment data, and FIG. 11 is a diagram showing the horizontal glyph segment string compressed. It is a figure shown by segment data. 12 and 13 are diagrams showing an example of a rectangular segment string used in the above embodiment, FIG. 14 is a diagram showing the rectangular segment string as segment data, and FIG. 15 is a diagram showing the rectangular segment string being compressed. It is a figure shown by segment data. FIG. 16 is a diagram showing the kanji ``A'', and FIG. 17 is a diagram for explaining how the ``A'' is stored in the character ROM in FIG. 2 in the above embodiment. 10: Computer 14 :Character ROM22:Dot data memory

Claims (1)

[Scope of Claims] An outline data memory that stores outline data of a plurality of characters, each defined by one or more outlines, for each character, wherein each outline is divided into a specific segment from among a plurality of segments. For those forming a column, compressed segment data in which segment data defining each segment belonging to the segment column is compressed using the graphical properties of the segment column is stored for each segment column;
For other segments, segment data that defines each segment is stored for each segment, and each compressed segment data stored in the outline data memory is restored to the segment data using the graphical properties. Outline data processing characterized by comprising a data restoring means, and an outline data outputting means for outputting outline data consisting of segment data restored by the data restoring means and segment data stored in the outline data memory. Device.