JP2009140063A - File management module, printing device, file management method, file management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a new file reading/writing framework in which it is not necessary to have any conversion table every code system. <P>SOLUTION: A file management module inputs a table in which any uni-code is assigned to each of one byte codes so as not to be duplicate and uni-codes for one character, and stores hash functions to output one byte codes of the range of 00 to 7F assigned to ASCII characters. The file management module converts the local code string of the file name of a file in a storage medium into a uni-code string by the table when providing file information, and converts the instructed uni-code string into a local code string by the table, and retrieves the file in the storage medium in the case of reading the file, and converts the instructed uni-code string into a local code string by the hash functions, and writes it in the storage medium when writing the file. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a file management technique for reading / writing a file via a file system in response to a request from a client terminal.

  Conventionally, file management in a storage medium such as a memory card or a hard disk is often performed by a FAT file system that describes a file name (short file name) using a local code (SJIS or the like). As an extension of the FAT file system, there is a VFAT (Virtual FAT) file system that can set a long file name as an option in addition to a short file name. Long file names are described in Unicode and up to 255 characters are allowed, while short file names are described in local code and limited to the so-called 8.3 format (8 characters + 3 extension characters). Is done.

  Consider a situation in which a file in a memory card inserted into a memory slot of a device such as a printer is read from a client terminal or written to a memory card via a network.

  In this case, the communication protocol between the client terminal and the printer stipulates that the file is specified using a file name described in Unicode, while the file in the memory card is short-circuited by a local code such as FAT. When managed by a file system that describes file names, a printer or the like needs the following code conversion.

  That is, when providing file information for selecting a read target to the client terminal, it is necessary to create a file information by converting the short file name of the file in the memory card into that described in Unicode.

  In addition, there is a possibility that the client terminal may request a file read by specifying a short file name described in Unicode. In addition to comparing the specified file name with the long file name of the file in the memory card, , Convert the short file name of the file in the memory card to the one written in Unicode and compare (or convert the specified file name to the one written in the local code and short file of the file in the memory card (Compared with name).

  Furthermore, since the file name specified by the write request from the client terminal is described in Unicode, the specified file name is used as a long file name, and the file name is converted into a local code (if necessary) It is necessary to create a short file name and write it to the memory card.

  However, when such code conversion is performed in a printer or the like, the following points are problematic.

  That is, it is necessary to specify in advance the code system of the local code adopted by the file in the memory card for the printer or the like (in other words, specify the conversion table used for code conversion in advance). There is. If there are multiple files that use different code systems in the memory card, it is cumbersome to make such designation for each file, and if the file in the memory card was created by someone else, In the first place, it is difficult to determine what kind of code system is used to create a file.

  Also, in order to be able to deal with a plurality of local code systems, a conversion table is required for each code system, which causes a problem that a large amount of memory resources are required. Further, in order to correspond to the new code system, localization work such as introducing a corresponding conversion table into a printer or the like is necessary, and this work places a heavy burden on the user or the like.

  Therefore, the present invention eliminates the need for having a conversion table for each local code system, and provides a new framework that can read / write files via the file system without specifying the local code system in advance. The purpose is to provide.

  The file management module of the present invention reads a file from a storage medium via a file system in response to a file read request from the client terminal, transmits the file to the client terminal, and responds to a file write request from the client terminal. A file management module for writing a file to a storage medium via a storage unit, storing a 1-byte code conversion table in which any Unicode is assigned to each 1-byte code 00 to FF without duplication; For each stored file, obtain a local code string of the file name, and apply the 1-byte code conversion table to each 1-byte code when the obtained local code string is regarded as a 1-byte code string. The acquired local code string is A file name conversion unit that converts the file name into a code string and sets the file name after conversion of the file by the converted Unicode string; and receives a request for file information of each file stored in the storage medium from the client terminal In this case, for each file stored in the storage medium, means for transmitting file information including the converted file name set by the file name converting means to the client terminal, and the converted file name from the client terminal Is applied to each Unicode string of the specified converted file name Unicode string, and the converted file name Unicode string is converted to a local code string. And converting the converted local code string into the storage medium. And a means for reading a file having a matching local code string from the storage medium via the file system and transmitting it to the client terminal, and a unicode for one character. Means for storing a Unicode hash function that outputs a 1-byte code in a range of 00 to 7F assigned to an ASCII character as an input, and a write request for a file X specifying a file name Y described in Unicode from the client terminal If accepted, it is determined whether or not non-ASCII characters are included in the file name Y. If not included, a file name composed of ASCII characters is created and included based on the file name Y. In the Unicode string of the file name Y By applying a de-hash function, the Unicode string of the file name Y is converted into a 1-byte code string in the range of 0 to 7F, and a file name composed of ASCII characters is converted based on the converted 1-byte code string. Means for creating and writing the file X to the storage medium via the file system using the created file name.

  According to such a configuration, the 1-byte code conversion table functions as a common conversion table that does not depend on the local code. Therefore, it is not necessary to have a conversion table for each local code system for reading a file. Even if the system is not designated in advance, the file can be read through the file system.

  Further, according to such a configuration, the Unicode hash function functions as a hash function that outputs a code common to the local code, so there is no need to have a conversion table for each code system of the local code for writing the file. The file system can be written through the file system without specifying the code system in advance. In addition, the file X written under such a configuration has a short file name composed only of ASCII characters. Therefore, in any file system employing any local code system, the file X is correctly written as the same character string. Can be read.

  The file management module of the present invention reads a file from a storage medium via a file system in response to a file read request from the client terminal, transmits the file to the client terminal, and responds to a file write request from the client terminal. A file management module for writing a file to a storage medium via a system, a means for storing a 1-byte code hash function that inputs 1-byte code 00 to FF and outputs a single-character unicode, and the storage medium For each stored file, obtain a local code string of the file name, apply the 1-byte code hash function to each 1-byte code when the obtained local code string is regarded as a 1-byte code string, The acquired local code string is converted to a Unicode string. When the file name conversion means for setting the file name after conversion of the file by the converted Unicode string and the file information request of each file stored in the storage medium from the client terminal are received, the storage For each file stored in the medium, means for transmitting file information including the converted file name set by the file name converting means to the client terminal, and a file designating the converted file name from the client terminal When a read request is received, for each file stored in the storage medium, the converted file name Unicode string set by the file name conversion means is compared with the specified converted file name Unicode string, Files with matching Unicode strings are stored in the file system. A means for reading out from the storage medium via the network and transmitting it to the client terminal, and storing a Unicode hash function that outputs a 1-byte code in the range of 0 to 7F assigned to an ASCII character, with the Unicode for one character as an input When a file X write request specifying the file name Y described in Unicode is received from the client terminal and the client terminal, it is determined whether or not the file name Y includes a non-ASCII character. In this case, a file name composed of ASCII characters is created based on the file name Y. If included, the Unicode hash function is applied to each Unicode of the Unicode string of the file name Y, and the file name Convert the Unicode string of Y to a 1-byte code string in the range of 0 to 7F, and the conversion Means for creating a file name composed of ASCII characters based on the one-byte code sequence and writing the file X to the storage medium via the file system using the created file name. It is characterized by.

  Preferably, the 1-byte code conversion table is configured by assigning ASCII character Unicodes to each of the 1-byte codes 00 to 7F without duplication.

  Preferably, the 1-byte code hash function outputs Unicode of ASCII characters when 1-byte codes 00 to 7F are input.

  The file management module of the present invention is a file management module that reads a file from a storage medium via a file system and transmits it to the client terminal in response to a file read request from the client terminal. Means for storing a 1-byte code conversion table in which any Unicode code is assigned without duplication; a local code string of a file name is acquired for each file stored in the storage medium; and the acquired local code The 1-byte code conversion table is applied to each 1-byte code when the sequence is regarded as a 1-byte code sequence, the acquired local code sequence is converted to a Unicode sequence, and the converted Unicode sequence File name conversion to set the file name after conversion And the file name after conversion set by the file name conversion means for each file stored in the storage medium when a request for file information of each file stored in the storage medium is received from the client terminal. When receiving a file read request designating the converted file name from the client terminal and means for transmitting the file information including the file information to the client terminal, each Unicode of the Unicode string of the specified converted file name Applying the one-byte code conversion table to convert the Unicode string of the converted file name into a local code string, and converting the converted local code string into a local code string of the file name of each file stored in the storage medium And the file whose local code string matches is Via the filesystem is read from the storage medium, characterized in that it comprises, means for transmitting to said client terminal.

  The file management module of the present invention is a file management module that reads a file from a storage medium via a file system and transmits it to the client terminal in response to a file read request from the client terminal. And a means for storing a one-byte code hash function that outputs a unicode for one character, a local code string of a file name is obtained for each file stored in the storage medium, and the obtained local code string Is converted to a Unicode string by applying the 1-byte code hash function to each 1-byte code when the file is regarded as a 1-byte code string, and the file is converted by the converted Unicode string. A file name conversion means for setting a subsequent file name, and When receiving a request for file information of each file stored in the storage medium from an client terminal, the file information including the converted file name set by the file name conversion means for each file stored in the storage medium Is sent to the client terminal and the file name conversion means sets each file stored in the storage medium when receiving a file read request designating the converted file name from the client terminal. Means for comparing the Unicode string of the converted file name with the specified Unicode string of the converted file name, reading out the file having the matched Unicode string from the storage medium via the file system, and transmitting the file to the client terminal And.

  The file management module according to the present invention is a file management module that writes a file to a storage medium via a file system in response to a file write request from a client terminal. Means for storing a Unicode hash function for outputting a 1-byte code in the range of 0 to 7F to be allocated; and when a write request for a file X specifying a file name Y described in Unicode is received from the client terminal, the file It is determined whether or not a non-ASCII character is included in the name Y. If not included, a file name composed of ASCII characters is created based on the file name Y, and if included, the file name is included. The Unicode hash for each Unicode string in Y Apply a number to convert the Unicode string of the file name Y into a 1-byte code string in the range of 0 to 7F, and create a file name composed of ASCII characters based on the converted 1-byte code string And means for writing the file X to the storage medium via the file system using the created file name.

  The printing apparatus of the present invention includes the file management module of the present invention, the file system, an interface for accessing the storage medium via the file system, and an interface for communicating with the client terminal.

  According to the file management method of the present invention, in response to a file read request from the client terminal, a file read step of reading the file from the storage medium via the file system and transmitting it to the client terminal, and in response to the file write request from the client terminal A file writing step of writing a file to a storage medium via a file system, wherein the file reading step uses a local code string of a file name for each file stored in the storage medium. 1 byte code in which any Unicode is assigned to each 1 byte code 00 to FF without duplication to each 1 byte code when the acquired local code string is regarded as a 1 byte code string Apply the conversion table to A step of converting the obtained local code sequence into a Unicode sequence, a step of setting a file name after conversion of the file by the converted Unicode sequence, and file information of each file stored in the storage medium from the client terminal If the request is received, for each file stored in the storage medium, the file information including the converted file name set by the file name conversion means is transmitted to the client terminal; When a file read request specifying a converted file name is received, the 1-byte code conversion table is applied to each Unicode string of the specified converted file name, and the Unicode string of the converted file name is A step of converting into a local code string and the converted code A step of comparing a calcode string with a local code string of a file name of each file stored in the storage medium, and a file whose local code string matches as a result of the comparison is read from the storage medium via the file system And a means for storing a unicode hash function that receives a unicode for one character as input and outputs a 1-byte code in a range of 00 to 7F assigned to an ASCII character, A step of determining whether or not a non-ASCII character is included in the file name Y when the write step receives a write request for the file X specifying the file name Y described in Unicode from the client terminal; As a result of the determination, if it is not included, AS is determined based on the file name Y. A step of creating a file name composed of CII characters, and, if included as a result of the determination, the Unicode hash function is applied to each Unicode of the Unicode string of the file name Y, and the Unicode of the file name Y is applied. Converting the sequence into a 1-byte code sequence in the range of 0 to 7F, creating a file name composed of ASCII characters based on the converted 1-byte code sequence, and using the created file name And writing the file X to the storage medium via the file system.

  The file management method of the present invention can be implemented in a printing apparatus or information processing apparatus, and the whole or a part of the program therefor is through various media such as a CD-ROM, a magnetic disk, a semiconductor memory, and a communication network. Can be installed or loaded.

  In the present invention, the term “means” does not simply mean a physical means, but includes a case where the functions of the means are realized by software. Also, the functions of one means or device may be realized by two or more physical means or devices, or the functions of two or more means or devices may be realized by one physical means or device.

  As described above, according to the present invention, it is not necessary to have a conversion table for each local code system, and it is possible to read / write a file through the file system without specifying the local code system in advance. Become.

  Embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram illustrating an appearance of a printer 1 according to the present embodiment. FIG. 1A is a perspective view of the printer 1 according to the present embodiment as viewed from the front, and FIG. 1B is a schematic rear view of the printer 1 according to the present embodiment.

  As shown in FIG. 1A, an operation panel 3 is provided on the upper right side of the main body 2 of the printer 1. The user can give various instructions such as a print instruction to the printer by operating the operation panel 3. A paper supply device 4 is provided on the back side of the main body 2 of the printer 1, and the paper set in the sheet feeder 5 or the roll paper set in the roll paper support unit 6 is fed into the main body 2. A printing mechanism (not shown) is mounted below the cover 7 provided in the center of the main body 2 of the printer 1, and when the printing mechanism executes a printing process, the printed paper 8 is placed on the lower front side of the main body 2. The paper is discharged from the paper discharge port 9.

  The operation panel 3 includes a display device 11 having a setting screen 10 and an operation unit 12 as an operation unit including a plurality of operation buttons 13a to 13c, and constitutes a user interface. The setting screen 10 displays, for example, a screen for setting the paper type, paper size, layout, photo selection, number of printed sheets, and the like. The operation unit 12 includes a power switch 13a for turning on the printer 1, a maintenance switch 13b that is pressed when an error occurs, and a roll paper switch 13c that is pressed when operating the roll paper.

  Also, slots 17 to 19 are provided on the front right side of the main body 2 of the printer 1, and these provide a hardware interface for accessing storage media 14 to 16 (compact flash (registered trademark), smart media, memory stick, etc.). It is composed. Further, LEDs 17a to 19a are arranged beside the slots 17 to 19, respectively, and the LEDs of valid slots (slots that are permitted to access the inserted storage medium) are lit.

  A display device (monitor) 20 for displaying images read from the storage media 14 to 16 is attached to the upper part of the main body 2 of the printer 1. The monitor screen 21 of the monitor 20 displays a screen for confirming an image and a print layout.

  On the other hand, as shown in FIG. 1B, ports 22 and 25 are provided on the lower back side of the main body 2 of the printer 1, and these constitute a hardware interface for communicating with (connecting to) an external device. is doing.

  The port 22 is for the printer 1 to communicate with the external storage device 23 (for example, MO) via the cable 27. The user inserts a storage medium (for example, an MO disk) 24 into the external storage device 23 and operates the operation panel 10 to instruct the printer 1 to directly print the print target data stored in the storage medium 24. Can be given.

  The port 25 is for the printer 1 to communicate with the client terminal 26 via the communication network 28. The client terminal 26 accesses the storage media 14 to 16 inserted in the slots 17 to 19 and the storage media 24 inserted to the external storage device 23 via the port 25. The user can give the client terminal 26 an instruction to read a predetermined file from the storage media 14 to 16 and 24 or an instruction to write a predetermined file to the storage media 14 to 16 and 24.

  FIG. 2 is a block diagram showing the configuration of the printer according to this embodiment.

  FIG. 2A shows the main hardware configuration of the printer 1. As shown in the figure, the printer 1 has the same hardware configuration as a normal printer device.

  For example, the printer 1 includes a print processing unit 40 including hardware such as a paper feed mechanism that supplies paper into the printer, a print engine that performs printing, and a paper discharge mechanism that discharges paper outside the printer. A print engine usually includes a paper feed mechanism, a carriage mechanism, a print head, and the like. A serial printer that prints in units of one character, such as an inkjet printer or a thermal transfer printer, a line printer that prints in units of lines, and a page Various print engines corresponding to a page printer or the like for printing can be used.

  For example, the printer 1 includes an information processing unit 41 configured by hardware such as a CPU, a ROM, a RAM, a user interface, and a hardware interface. The information processing unit 41 controls the print processing unit 40 to execute print processing.

  FIG. 2B shows the main functional configuration of the printer 1.

  When the slot control units 30 to 32 detect that the storage media are inserted into the corresponding slots 17 to 19, the slot control units 30 to 32 execute initialization processing to enable access to the storage media, and to that effect Is notified to the file system 36.

  When the external storage device control unit 33 detects that the storage medium has been inserted into the external storage device 23 via the port 22, the external storage device control unit 33 executes an initialization process to enable the access to the storage medium. This is notified to the file system 36.

  When the access control unit 34 receives an access request from the client terminal 26 to the file system 36 via the port 25, the access control unit 34 notifies the file management module 35 to that effect. Here, in this embodiment, it is assumed that the communication protocol between the client terminal 26 and the printer 1 specifies that a file is specified using a file name described in Unicode. Therefore, when a file name is included in the access request received by the access control unit 34, it is assumed that the file name is described in Unicode.

  In response to the access request from the access control unit 34, the file management module 35 converts the file name specified in the access request and uses the converted file name from each storage medium via the file system 36. Read file / write file to each storage medium. Specifically, as shown in FIG. 3, the file management module 35 includes a storage unit that stores a 1-byte code conversion table 100, a Unicode hash function 101, a file name conversion function, a file information transmission function, a file reading function, A function unit for executing a file writing function and the like is provided. In FIG. 3, each function of the functional unit is illustrated as functional means. The operation of the file management module 35 will be described in detail later.

  The file system 36 is a conventional file system that describes a file name (short file name) in a local code, such as FAT, and provides file access means to the file management module 35 and the print control unit 37. Manage file information on storage media.

  The print control unit 37 acquires print target data stored in each storage medium via the file system 36 in accordance with a user instruction, and notifies the print processing unit 40 of a print request for printing the print target data. . Further, the print control unit 37 manages the status of the printer 1 such as whether the printer 1 is printing or whether a printing error has occurred according to the information from the print processing unit 40.

  Each of these means is functionally realized in the information processing unit 41 when the CPU executes an application program stored in the ROM or RAM. These application programs may be configured to be installed or loaded into the information processing unit 41 through various recording media such as a CD-ROM, a magnetic disk, and a semiconductor memory, or via a communication network. desirable.

  Hereinafter, with reference to the flowcharts shown in FIGS. 4 and 5, file access processing (file read processing, file writing) in the printer 1, taking as an example the case of accessing a file stored in the storage medium 14 via the file system 36. Processing) will be described. In addition, in this specification, each process shown in a flowchart etc. (including a partial process to which no reference numeral is assigned) is arbitrarily changed or executed in parallel within a range that does not contradict the processing contents. Can do. Also do.

(File read processing: FIG. 4)
When reading a file from the storage medium 14, the client terminal 26 first creates a file information request for the file stored in the storage medium 14 and transmits it to the printer 1 based on a user instruction.

  When receiving a request for file information related to the storage medium 14 from the client terminal 26, the access control unit 34 notifies the request to the file management module 35 (S100).

  When receiving the file information request, the file management module 35 acquires a local code string of a short file name for each file stored in the storage medium 14 via the file system 36 (S101).

  Next, for each file stored in the storage medium 14, the file management module 35 applies the 1-byte code conversion table 100 to each 1-byte code when the acquired local code sequence is regarded as a 1-byte code sequence. Then, the acquired local code string is converted to a Unicode string, and a short file name after conversion of the file is set by the converted Unicode string (S102).

  The 1-byte code conversion table 100 is a table in which any Unicode is assigned to each of the 1-byte codes 00 to FF without duplication. In the 1-byte code conversion table 100, if Unicodes (unicodes of general characters other than control characters) are assigned to all 1-byte codes 00 to FF without duplication, which Unicode is assigned to each 1-byte code? It can be determined according to the design. Therefore, the 1-byte code conversion table 100 does not have to be a local code conversion table adopted by the short file name to be converted (in other words, the 1-byte code conversion table 100 is a common conversion independent of the local code). Function as a table).

  However, it is desirable to assign ASCII character Unicode to each of the 1-byte codes 00 to 7F without duplication. By setting the 1-byte code conversion table 100 in this way, the short file name after conversion can be composed of only ASCII characters, as will be described later, and has a commonality with the short file name created when writing the file. be able to.

  FIG. 6 conceptually shows an example of the 1-byte code conversion table 100. The upper 4 bits of 1 byte are assigned to rows, and the lower 4 bits are assigned to columns. In each element in the table, characters represented by Unicode are shown in the upper row, and Unicode is shown in the lower row. For example, when the short file name of the file X is “specification” and the local code is SJIS, the local code string is “96BE: 8DD7: 8F91”. In this case, when the 1-byte code conversion table 100 shown in FIG. 6 is applied, the Unicode string of the short file name after the conversion of the file X becomes “00D6: 00FE: 00CD: 0117: 0CF: 00D1”.

  As can be seen from this example, when the file name is converted by applying the 1-byte code conversion table 100, the characters of the file name may not match before and after the conversion. However, since the 1-byte code conversion table 100 has Unicode assigned to all the 1-byte codes 00 to FF, there is a possibility that a local code to which no Unicode is assigned may exist. Unlike the case where is applied, the short file name after conversion written in Unicode can always be set.

  Next, the file management module 35 creates file information including the set converted short file name for each file stored in the storage medium 14, and transmits it to the client terminal 26 (S103). The file information may include a Unicode string of the long file name for the file for which the long file name is set. Also, information such as file size and creation date / time may be included.

  When the file information is received, the client terminal 26 displays a list of converted short file names and the like on the display unit based on the file information. The user can instruct file reading by referring to the list. When the client terminal 26 receives a file read instruction from the user, the client terminal 26 creates a file read request in which the specified file is designated by a short file name after conversion, and transmits the file read request to the printer 1.

  When the file management module 35 receives a file read request from the client terminal 26, first, the file name specified in the file read request and the long file name of each file stored in the storage medium 14 (when set) ) Is compared (S104).

  If there is a file whose long file name matches, the file is read from the storage medium 14 via the file system 36 (S105) and transmitted to the client terminal 26 (S106).

  On the other hand, if there is no file with the long file name matching, the file management module 35 acquires the Unicode string of the specified file name, and reverse-converts the 1-byte code conversion table 100 to each Unicode of the acquired Unicode string. (Ie, so as to obtain a one-byte code from the Unicode string), and converts the Unicode string of the designated file name into a local code string (S107).

  If such conversion is possible, the file management module 35 determines that the specified file name is the short file name after conversion. In this case, a local code string of a short file name is acquired for each file stored in the storage medium 14 via the file system 36, and the converted local code string is used for the short file name of each acquired file. Compared with the local code string (S108), the file with the matched local code string is read from the storage medium 14 via the file system 36 (S109) and transmitted to the client terminal 26 (S106).

  Thereby, the client terminal 26 can acquire the file instructed by the user.

  If the conversion cannot be performed in S107, the file management module 35 determines that the specified file name is not the converted short file name. In this case, the file management module 35 determines that there is no file corresponding to the storage medium 14 and transmits a message to that effect to the client terminal 26.

  As described above, in this embodiment, when transmitting file information for each file stored in the storage medium 14, the short file name described in the local code is converted into the Unicode using the 1-byte code conversion table 100. When the file information is created by converting into the described short file name after conversion, and when the file read request specifying the post-conversion short file name specified from the client terminal 26 is received, the 1-byte code conversion table 100 Is used to convert the converted short file name described in Unicode into a short file name described in local code and compare it with the short file name of each file stored in the storage medium 14. ing.

  According to this configuration, as described above, the 1-byte code conversion table 100 functions as a common conversion table that does not depend on a local code. Therefore, it is not necessary to have a conversion table for each local code system for reading a file. In addition, the file can be read through the file system 36 without specifying the code system of the local code in advance. In addition, as a result of eliminating the need for a conversion table for each code system, consumption of memory resources required for the conversion table can be suppressed, and localization work for adapting to a new code system is also unnecessary.

(File writing process: FIG. 5)
When writing the file X to the storage medium 14, the client terminal 26 creates a file write request including the main data of the file X, the file name Y described in Unicode, and the like based on the user's instruction, and transmits it to the printer 1. .

  When receiving a file write request from the client terminal 26, the file management module 35 acquires a Unicode string of the file name Y specified in the file write request (S200).

  Next, the file management module 35 determines whether or not a non-ASCII character is included in the file name Y based on the acquired Unicode string (S201).

  If the non-ASCII character is not included, the file management module 35 creates a short file name composed of ASCII characters based on the file name Y composed of only ASCII characters (S202), and then the process of S205 Migrate to

  The short file name can be created in the same manner as before. For example, when the file name Y satisfies the 8.3 format, a short file name is created using the Unicode string of the file name Y as it is as a local code string. On the other hand, if the file name Y does not satisfy the 8.3 format, the file name Y is omitted / modified so as to satisfy the 8.3 format and consist only of ASCII characters. Create a short file name using the Unicode string as the local code string. As an omission / deformation method, for example, when the file name Y is “abcdefghijk.txt”, it may be omitted / deformed as “abcdef˜1.txt”.

  On the other hand, when a non-ASCII character is included, the file management module 35 applies the Unicode hash function 101 to each Unicode string of the file name Y, and converts the Unicode string of the file name Y to a range of 00 to 7F. Conversion into a 1-byte code string (S203).

  The Unicode hash function 101 receives an input of Unicode for one character and is in a range of 00 to 7F assigned to an ASCII character, preferably a general character other than the control character among the ASCII characters (for example, “A” to “Z”, This is a hash function that outputs a 1-byte code in a range assigned to “0” to “9”). Normally, in any local code, ASCII characters are assigned to 00 to 7F, so the Unicode hash function 101 functions as a hash function that outputs a code common to the local code. In addition, the 1-byte code sequence obtained by applying the Unicode hash function 101 represents the same character string composed of only ASCII characters in any local code system.

  The aspect of the Unicode hash function 101 can be determined according to the design. For example, the Unicode hash function 101 is defined so that the Unicode for one character is delimited every byte, each 1 byte obtained by the delimitation is totaled, and the remainder when the total value is divided by 127 is output. May be. Also, for example, when an ASCII character Unicode is input, a 1-byte code corresponding to the ASCII character is output, and when a non-ASCII character Unicode is input, it is assigned to a specific ASCII character (for example, “_”). The Unicode hash function 101 may be defined so as to output a 1-byte code.

  Next, the file management module 35 creates a short file name composed of ASCII characters based on the converted 1-byte code string composed only of ASCII characters (S204). The creation of the short file name can be executed in the same manner as in the past as shown in the example above.

  Next, the file management module 35 sets the created short file name as the short file name of the file X that has received the write request, and sets the file name Y as the long file name as necessary. The file X is written to the storage medium 14 via the system 36 (S205).

  As described above, in this embodiment, when a write request for the file X specifying the file name Y described in Unicode is received from the client terminal 26, the Unicode hash function 101 is applied to the file name Y to apply ASCII characters. Is used, and the file X is written to the storage medium 14 using the created short file name.

  According to such a configuration, as described above, the Unicode hash function 101 functions as a hash function that outputs a code common to the local code, and therefore needs to have a conversion table for each code system of the local code for file writing. No, the file can be written via the file system 36 without specifying the code system of the local code in advance. In addition, as a result of eliminating the need for a conversion table for each code system, consumption of memory resources required for the conversion table can be suppressed, and localization work for adapting to a new code system is also unnecessary.

  In addition, the file X written under such a configuration has a short file name composed of only ASCII characters, so that the same short file name is used in any local file code system. It can be read correctly as a character string.

(Modification)
The present invention is not limited to the above-described embodiment, and can be variously modified and applied. For example, in the above embodiment, the printer 1 is described as an example. However, the present invention can also be applied to a printing apparatus such as a copying machine, a facsimile machine, and a multifunction machine. In addition, in response to a file read request from the client terminal, a file is read via the file system and transmitted to the client terminal, and a file is written via the file system in response to a file write request from the client terminal. The present invention is applicable to apparatuses other than printing apparatuses.

  In the above embodiment, in the file reading process, the converted short file name of each file stored in the storage medium 14 is set. However, the process of setting the converted short file name of each file is performed by the file reading process. You may perform as a process different from a read-out process.

  Further, for example, in the above-described embodiment, the file name is converted using the 1-byte code conversion table 100 in the file reading process, but instead of the 1-byte code conversion table 100, the 1-byte code hash function 102 is used. The file name may be converted.

  The 1-byte code hash function 102 is a hash function that inputs 1-byte code 00 to FF and outputs Unicode for one character (unicode of general characters other than control characters). The specific form of the 1-byte code hash function 102, that is, what kind of Unicode is output for each 1-byte code is designed regardless of the local code system adopted by the short file name to be converted. Can be determined according to

  However, it is desirable that the 1-byte code hash function 102 is configured to output ASCII character Unicode when the 1-byte code 00 to 7F is input. This is because, as in the case of the 1-byte code conversion table 100, the short file name after conversion can be composed only of ASCII characters, and can have commonality with the short file name created when writing the file.

  Also, when the file name is converted by applying the 1-byte code hash function 102, the characters of the file name may not match before and after the conversion, as in the case of the 1-byte code conversion table 100. However, by applying the 1-byte code hash function 102, Unicode is assigned to all the 1-byte codes 00 to FF, so that there is a possibility that there is a local code to which no Unicode is assigned. Unlike the case where a conversion table is applied, a short file name after conversion written in Unicode can be set.

  Hereinafter, with reference to FIG. 7, a file reading process when the 1-byte code hash function 102 is used will be described.

  When the access control unit 34 receives a request for file information related to the storage medium 14 from the client terminal 26, the access control unit 34 notifies the request to the file management module 35 (S300).

  When the file management module 35 receives a file information request, the file management module 35 acquires a local code string of a short file name for each file stored in the storage medium 14 via the file system 36 (S301).

  Next, for each file stored in the storage medium 14, the file management module 35 applies the 1-byte code hash function 102 to each 1-byte code when the acquired local code sequence is regarded as a 1-byte code sequence. Then, the acquired local code string is converted into a Unicode string, and a short file name after conversion of the file is set by the converted Unicode string (S302).

  Next, the file management module 35 creates file information including the set converted short file name for each file stored in the storage medium 14, and transmits it to the client terminal 26 (S303). The file information may include a Unicode string of the long file name for the file for which the long file name is set. Also, information such as file size and creation date / time may be included.

  When the file information is received, the client terminal 26 displays a list of converted short file names and the like on the display unit based on the file information. The user can instruct file reading by referring to the list. When the client terminal 26 receives a file read instruction from the user, the client terminal 26 creates a file read request in which the specified file is designated by a short file name after conversion, and transmits the file read request to the printer 1.

  When the file management module 35 receives a file read request from the client terminal 26, first, the file name specified in the file read request and the long file name of each file stored in the storage medium 14 (when set) ) Is compared (S304).

  If there is a file whose long file name matches, the file is read from the storage medium 14 via the file system 36 (S305) and transmitted to the client terminal 26 (S306).

  On the other hand, if there is no file whose long file name matches, the file management module 35 acquires the Unicode string of the specified file name and sets the converted short file name for each file stored in the storage medium 14. Are compared with the Unicode string of the designated file name (S307), and the file having the matched Unicode string is read from the storage medium 14 via the file system 36 (S308) and transmitted to the client terminal 26. (S306).

  Thereby, the client terminal 26 can acquire the file instructed by the user.

  According to such a configuration, it is not necessary to have a conversion table for each local code system, and a file can be read out via the file system 36 without specifying the local code system in advance.

2 is a diagram illustrating an appearance of a printer 1. FIG. 2 is a block diagram illustrating a configuration of a printer. FIG. 3 is a block diagram showing a configuration of a file management module 35. FIG. It is a flowchart which shows the flow of the file read-out process in embodiment of this invention. It is a flowchart which shows the flow of the file write-in process in embodiment of this invention. It is a figure which shows the example of the 1 byte code conversion table. It is a flowchart which shows the flow of the file read-out process in the modification of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Printer, 14, 15, 16 ... Storage medium, 17, 18, 19 ... Slot, 22, 25 ... Port, 23 ... External storage device, 26 ... Client terminal, 30-33 ... Slot control part, 34 ... Access control 35: File management module, 36 ... File system, 37 ... Print control unit, 40 ... Print processing unit, 41 ... Information processing unit, 100 ... 1 byte code conversion table, 101 ... Unicode hash function, 102 ... 1 byte code Hash function

Claims (10)

In response to a file read request from the client terminal, the file is read from the storage medium via the file system and transmitted to the client terminal. In response to a file write request from the client terminal, the file is stored in the storage medium via the file system. A file management module to write,
Means for storing a 1-byte code conversion table in which any Unicode is assigned to each of the 1-byte codes 00 to FF without duplication;
For each file stored in the storage medium, a local code string of a file name is acquired, and the 1-byte code conversion table is added to each 1-byte code when the acquired local code string is regarded as a 1-byte code string. Applying, converting the acquired local code string to a Unicode string, and setting a file name after conversion of the file by the converted Unicode string,
A file including a file name after conversion set by the file name conversion means for each file stored in the storage medium when a request for file information of each file stored in the storage medium is received from the client terminal Means for transmitting information to the client terminal;
When receiving a file read request designating the converted file name from the client terminal, the 1-byte code conversion table is applied to each Unicode of the Unicode string of the designated converted file name, and the converted file A Unicode string of a name is converted into a local code string, the converted local code string is compared with a local code string of a file name of each file stored in the storage medium, and a file having a matching local code string is compared with the file system Means for reading from the storage medium via the network and transmitting to the client terminal;
Means for storing a unicode hash function that takes a unicode for one character as input and outputs a 1-byte code in a range of 00 to 7F assigned to an ASCII character;
When a write request for a file X specifying a file name Y described in Unicode is received from the client terminal, it is determined whether or not a non-ASCII character is included in the file name Y. Based on the file name Y, a file name composed of ASCII characters is created, and if included, the Unicode hash function is applied to each Unicode of the Unicode string of the file name Y to obtain the Unicode of the file name Y The sequence is converted to a 1-byte code sequence in the range of 0 to 7F, a file name composed of ASCII characters is created based on the converted 1-byte code sequence, and the file is created using the created file name. Means for writing the file X to the storage medium via a system;
A file management module comprising: In response to a file read request from the client terminal, the file is read from the storage medium via the file system and transmitted to the client terminal. In response to a file write request from the client terminal, the file is stored in the storage medium via the file system. A file management module to write,
Means for storing a 1-byte code hash function that inputs 1-byte code 00 to FF and outputs Unicode for one character;
For each file stored in the storage medium, a local code string of a file name is acquired, and the 1-byte code hash function is added to each 1-byte code when the acquired local code string is regarded as a 1-byte code string. Applying, converting the acquired local code string to a Unicode string, and setting a file name after conversion of the file by the converted Unicode string,
A file including a file name after conversion set by the file name conversion means for each file stored in the storage medium when a request for file information of each file stored in the storage medium is received from the client terminal Means for transmitting information to the client terminal;
When receiving a file read request designating the converted file name from the client terminal, the designation of the Unicode string of the converted file name set by the file name converting means for each file stored in the storage medium Means for reading the file with the matching Unicode string from the storage medium via the file system and comparing it with the Unicode string of the file name after conversion,
Means for storing a unicode hash function that takes a unicode for one character as input and outputs a 1-byte code in a range of 00 to 7F assigned to an ASCII character;
When a write request for a file X specifying a file name Y described in Unicode is received from the client terminal, it is determined whether or not a non-ASCII character is included in the file name Y. Based on the file name Y, a file name composed of ASCII characters is created, and if included, the Unicode hash function is applied to each Unicode of the Unicode string of the file name Y to obtain the Unicode of the file name Y The sequence is converted to a 1-byte code sequence in the range of 0 to 7F, a file name composed of ASCII characters is created based on the converted 1-byte code sequence, and the file is created using the created file name. Means for writing the file X to the storage medium via a system;
A file management module comprising:   2. The file management module according to claim 1, wherein the 1-byte code conversion table is configured by assigning ASCII character Unicode to each of the 1-byte codes 00 to 7F without duplication.   3. The file management module according to claim 2, wherein the 1-byte code hash function outputs Unicode of ASCII characters when 1-byte codes 00 to 7F are input. A file management module that reads a file from a storage medium via a file system and transmits it to a client terminal in response to a file read request from the client terminal,
Means for storing a 1-byte code conversion table in which any Unicode is assigned to each of the 1-byte codes 00 to FF without duplication;
For each file stored in the storage medium, a local code string of a file name is acquired, and the 1-byte code conversion table is added to each 1-byte code when the acquired local code string is regarded as a 1-byte code string. Applying, converting the acquired local code string to a Unicode string, and setting a file name after conversion of the file by the converted Unicode string,
A file including a file name after conversion set by the file name conversion means for each file stored in the storage medium when a request for file information of each file stored in the storage medium is received from the client terminal Means for transmitting information to the client terminal;
When receiving a file read request designating the converted file name from the client terminal, the 1-byte code conversion table is applied to each Unicode of the Unicode string of the designated converted file name, and the converted file A Unicode string of a name is converted into a local code string, the converted local code string is compared with a local code string of a file name of each file stored in the storage medium, and a file having a matching local code string is compared with the file system Means for reading from the storage medium via the network and transmitting to the client terminal;
A file management module comprising: A file management module that reads a file from a storage medium via a file system and transmits it to a client terminal in response to a file read request from the client terminal,
Means for storing a 1-byte code hash function that inputs 1-byte code 00 to FF and outputs Unicode for one character;
For each file stored in the storage medium, a local code string of a file name is acquired, and the 1-byte code hash function is added to each 1-byte code when the acquired local code string is regarded as a 1-byte code string. Applying, converting the acquired local code string to a Unicode string, and setting a file name after conversion of the file by the converted Unicode string,
A file including a file name after conversion set by the file name conversion means for each file stored in the storage medium when a request for file information of each file stored in the storage medium is received from the client terminal Means for transmitting information to the client terminal;
When receiving a file read request designating the converted file name from the client terminal, the designation of the Unicode string of the converted file name set by the file name converting means for each file stored in the storage medium Means for reading the file with the matching Unicode string from the storage medium via the file system and comparing it with the Unicode string of the file name after conversion,
A file management module comprising: A file management module that writes a file to a storage medium via a file system in response to a file write request from a client terminal,
Means for storing a unicode hash function that takes a unicode for one character as input and outputs a 1-byte code in a range of 00 to 7F assigned to an ASCII character;
When a write request for a file X specifying a file name Y described in Unicode is received from the client terminal, it is determined whether or not a non-ASCII character is included in the file name Y. Based on the file name Y, a file name composed of ASCII characters is created, and if included, the Unicode hash function is applied to each Unicode of the Unicode string of the file name Y to obtain the Unicode of the file name Y The sequence is converted to a 1-byte code sequence in the range of 0 to 7F, a file name composed of ASCII characters is created based on the converted 1-byte code sequence, and the file is created using the created file name. Means for writing the file X to the storage medium via a system;
A file management module comprising:   The file management module according to claim 1, the file system, an interface for accessing the storage medium via the file system, and an interface for communicating with the client terminal A printing apparatus comprising: In response to a file read request from the client terminal, a file read process for reading the file from the storage medium via the file system and transmitting it to the client terminal; and in response to a file write request from the client terminal, stored via the file system A file management method including a file writing step of writing a file to a medium,
The file reading step includes
Obtaining a local code string of a file name for each file stored in the storage medium;
A 1-byte code conversion table in which any Unicode is assigned to each 1-byte code 00 to FF without duplication is applied to each 1-byte code when the acquired local code sequence is regarded as a 1-byte code sequence. Converting the acquired local code string into a Unicode string;
Setting the converted file name of the file by the converted Unicode string;
A file including a file name after conversion set by the file name conversion means for each file stored in the storage medium when a request for file information of each file stored in the storage medium is received from the client terminal Transmitting information to the client terminal;
When receiving a file read request designating the converted file name from the client terminal, the 1-byte code conversion table is applied to each Unicode of the Unicode string of the designated converted file name, and the converted file Converting the Unicode string of the name to a local code string;
Comparing the converted local code string with a local code string of a file name of each file stored in the storage medium;
As a result of the comparison, reading a file with a matching local code string from the storage medium via the file system and transmitting it to the client terminal;
Means for storing a unicode hash function that takes a unicode for one character as input and outputs a 1-byte code in a range of 00 to 7F assigned to an ASCII character;
The file writing step includes
A step of determining whether or not a non-ASCII character is included in the file name Y when receiving a write request for the file X specifying the file name Y described in Unicode from the client terminal;
As a result of the determination, if not included, creating a file name composed of ASCII characters based on the file name Y;
As a result of the determination, if it is included, the Unicode hash function is applied to each Unicode of the Unicode string of the file name Y, and the Unicode string of the file name Y is converted into a 1-byte code string in the range of 0 to 7F. Converting and creating a file name composed of ASCII characters based on the converted string of 1-byte code;
Writing the file X to the storage medium via the file system using the created file name.   A program for causing a computer to execute the file management method according to claim 9.

Images