EP0976053A1 - Systeme de conversion automatique - Google Patents

Systeme de conversion automatique

Info

Publication number
EP0976053A1
EP0976053A1 EP98909722A EP98909722A EP0976053A1 EP 0976053 A1 EP0976053 A1 EP 0976053A1 EP 98909722 A EP98909722 A EP 98909722A EP 98909722 A EP98909722 A EP 98909722A EP 0976053 A1 EP0976053 A1 EP 0976053A1
Authority
EP
European Patent Office
Prior art keywords
client
information
server
converter
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP98909722A
Other languages
German (de)
English (en)
Other versions
EP0976053A4 (fr
Inventor
Eliyahu Marmor
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Google LLC
Original Assignee
El-Mar Software Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from IL12107197A external-priority patent/IL121071A0/xx
Application filed by El-Mar Software Ltd filed Critical El-Mar Software Ltd
Publication of EP0976053A1 publication Critical patent/EP0976053A1/fr
Publication of EP0976053A4 publication Critical patent/EP0976053A4/fr
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/957—Browsing optimisation, e.g. caching or content distillation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user

Definitions

  • This invention is related to the field of multi-lingual and multi-standard communication between independent computers and, in particular, to automatic conversion between different standards.
  • the WWW is a collection of networked computers which exchange pages of hyper-text using the TCP/IP protocol. These pages may contain combinations of text, images and sounds, each of which may be either dynamic or static. Hyper-text is also called hyper-media or hyper-links. In addition, these pages may provide various methods of data input, for example, fill-in forms. In the context of the WWW, the pages are also called documents.
  • the computers may be roughly divided into two main classes, clients and servers. The pages are usually downloaded from the servers by a client, using a specialized program called a "browser".
  • the client enters data onto a page, and transmit this data to a server.
  • This data is usually used to find new pages for the client to download.
  • it is becoming a common practice to generate WWW pages on-the-fly at the server, using special programs.
  • a rapidly growing subset of the "client" class of computer is the network computer, which is a specialized computer which is especially designed for connection to the Internet. Included in this sub-class are also Internet telephones and Internet TVs, all of which are not general purpose computers and have their Internet support hard-wired rather than programmed in software.
  • Multi-lingual computer applications are known, for example multi-lingual word processors and even multi-lingual operating systems.
  • the system developer enforces a single standard of language representation and handling.
  • the Internet there is no single system developer and it is not possible to enforce a single standard worldwide.
  • the first failure mode is related to data representation, i.e., how textual data is represented and how individual characters are encoded. As noted above, there are three such encoding standards in Japan and several in Israel. Further, the same character code may be used for different glyphs depending on the language and on the character set.
  • the second failure mode is related to data manipulation, where a given program cannot manipulate multi-lingual data.
  • Some browsers do not support fonts which require more than 8 bits for encoding. Unicode, for example, requires 16 bits. None of the leading browsers are designed to support variable width (in bits) character codes.
  • the third failure mode is data display. It should be noted that in many languages, such as Arabic, the glyph form of a letter is dependent on the surrounding letters. This requires various display algorithms. In addition, the number of languages and fonts in the world are much greater than the number usually stored in a client computer, especially if it is a specialized network computer. Also, when using some browsers it is not possible to simultaneously display more than one language at a time (in addition to English).
  • the fourth failure mode is related to data input.
  • One issue is keyboard mapping - assuming that a browser supports the font of the language used by the server, how should the browser map keystrokes to the individual glyphs.
  • Another issue is support for bi-directional data input. Some languages, for example, Hebrew and Arabic, are written from right to left (RTL) rather than from left to right (LTR), as English is. Other, oriental, languages are written in a vertical orientation.
  • RTL right to left
  • LTR left to right
  • the text may be stored in a "logical" manner, where the first stored letter is usually the rightmost letter.
  • the text may be stored in a "visual" manner, where the first stored letter is the leftmost letter, which in a multi-line text is located in the middle of the text.
  • visually stored data is displayed LTR (with an appropriate font)
  • logically stored data must be displayed on a letter-by-letter basis - LTR letters displayed one way and RTL letters displayed in another way. It is a common practice to mix visual and logical representations in a single WWW page. This is particularly true for input. The input is most conveniently made using a logical representation, even though the data may be stored using a visual representation.
  • search engines automatically assimilate the contents of many WWW pages and allow a client to search these pages using various methods. If a page is stored using a visual representation, a search using keywords entered using a logical representation will not find the page. Of course, if the character set encoding is different, the page will not be found either.
  • search engines arises in languages where there is more than one legal way to spell a word. This is common in various dialects of English, but in Thai, there is a lexical equivalence between various orderings of certain three-letter groups. Since search engines are inherently global, enforcing a single standard is practically impossible.
  • Another example of a compound problem is the use of multiple standards and/or languages in a single WWW page.
  • Another compound problem is translating between units of measurements and ways of writing dates and times. For example, "1/6/1999" represents January 6, 1999 in the US and June 1, 1999 in Europe. To make matters worse, even the standard language of the WWW pages, HTML
  • Israel is one of the world industrial leaders in most Internet applications.
  • the penetration of the Internet into the public sector is substantially retarded as compared to the US, even though a higher percentage of households in Israel own a computer with a modem than in the US.
  • a web site has been constructed in which a client enters search terms in one language (Hebrew) and the search engine translates the words to English and applies the translated words to one of a limited number of existing search engines.
  • the input is entered using Latin characters, which the web site maps to Hebrew characters after the input process is finished.
  • a web site has been created in which a JavaScript code segment is included in a WWW page, which displays a virtual keyboard in the desired language and which allows a user to click on keys. Each click adds a letter to a text object. The input from the user is directed only to the web site and for use of the programs therein and does not allow communication with other web sites.
  • the Microsoft Internet Explorer version 3.01, Hebrew version uses meta-tags in the WWW page to indicate whether a text object uses visual encoding or logical encoding. This mformation is used to drive display algorithms for the text object.
  • Japan by Kunio Goto and Masaya Nakayama, URL "http://kl2.jain.ad.jp/inet95.html”
  • the server is suggested for use as a proxy server and it replaces character codes from one standard set with codes from another set. This replacement is on a letter by letter basis.
  • the server and the client communicate using a WWW protocol.
  • An automatic converter in accordance with preferred embodiment of the invention is integrated into a client-server relationship as a (hidden) proxy.
  • the converter converts the information to a standard usable by the client.
  • the converter converts the input data to a standard usable by the server.
  • the support is provided by the network itself, i.e., "the network is the computer”.
  • the converter automatically determines the standard used by the server for a WWW page.
  • the converter automatically detects the language of at least a portion of the page.
  • the converter automatically detects the standard used by the client.
  • the converter automatically detects the language used by the client.
  • the client sends information to the converter regarding the client's capabilities.
  • the converter queries the client regarding the client's capabilities. The client may respond automatically, or a user at the client may respond instead.
  • the client is provided with a manual override for the standard used by the server and/or the client.
  • This feature is especially useful if the automatic standard detection does not properly detect the standard.
  • the automatic converter does attempt to narrow the possibilities. It should be appreciated however that automatic detection of standards may be adversely affected by the existence of mistakes in the WWW page, such as spelling mistakes.
  • data from the server which cannot normally be displayed on the client is converted, by the automatic converter, into image files for display on the client.
  • text data for which there is no available font on the client is converted in image data, for example GIF format data.
  • the text data is converted into a plurality of images.
  • small groups of words are converted into a single GIF file, such that resizing of an object containing the text data is facilitated.
  • the number of words in a group is inversely related to the font size.
  • each group consists of a single word, to enhance caching.
  • information relating to the content and or the format of the converted text is encoded into the name of the image file.
  • the name of an image file may include an indication that the word is "the" and that it is underlined. Encoding the information in this manner increases the efficiency of cache systems.
  • Another aspect of some preferred embodiments of the invention relates to replacing input objects, which are not supported by the client, with custom made Java applets.
  • the converter replaces the definitions of input objects, in the pages sent by the server, with calls to Java applets.
  • the automatic converter parses the pages to determine the input objects and replaces the input objects which have no support at the client with Java applets.
  • the client When the page is displayed by the client, the client is provided with a "new" input object, which supports the standards and/or language. This is most convenient for the client and which does not require support by the client's browser.
  • these Java applets are cached at the client for future pages, so that the applets need not be download anew with each page.
  • the new input object is compatible with the server's standards.
  • the converter converts the data entered using the input object to a standard supported by the server.
  • the Java applets which are used for input in a particular language render individual keystrokes as character glyphs even if the particular font required by the language is not supported by the client.
  • the applets also provide other services, such as bi-directional input, letter fusion and even spell checking.
  • copyrighted information is provided through a conversion server, which server encodes the information so that it is difficult to copy using data manipulation programs, yet easy to assimilate using human senses, once displayed.
  • the display process is also protected so copying the displayed information is also difficult.
  • an automatic converter brokers information between a client and an information provider, while providing and presenting the information to the client in a form which is not easily copied.
  • the client is provided with a program, preferably a Java applet, which temporally modulates the information, so that only small parts of the information are displayed at any instant.
  • a program preferably a Java applet
  • temporal modulation include, displaying the data in a running strip and intermixing advertisements with the copyrighted information.
  • client programs are authenticated.
  • the authentication uses a key-code system in which the server sends a key to the client and the client is expected to respond with a code which is a (secret) function of the key.
  • a different key-code combination is used in each communication by the server.
  • the transmitted data is encrypted, to reduce the possibility of it being intercepted by a copyright pirate.
  • a method for transferring information between a server and a client, through a converter comprising: analyzing at least a portion the information by said converter, to determine a standard used by said server to encode the information in the portion; and replacing at least a portion of the analyzed information with other information, which other information uses a second standard, wherein, analyzing comprises parsing the information on a syntactic level and wherein said information comprises at least one Internet hypertext document.
  • the standard comprises a language.
  • the standard comprises a standard for an RTL language.
  • replacing comprises replacing only a portion of the analyzed information.
  • a method for transferring information between a server and a client, through a converter, which information includes at least one input object comprising receiving said information by said converter from said server; replacing said input object with another input object; and transmitting the information after said replacing, wherein said information comprises at least one Internet hypertext document.
  • the input object is a text object.
  • said another input object is of a type supported by said client.
  • said input object is of a type not supported by said client.
  • said input object is of a type supported by said client.
  • replacing comprises replacing said input object responsive to a known difference in standards between said client and said server.
  • said another input object is not included in a toolkit portion of said client.
  • said another input object is a call to a program.
  • said program is a Java applet.
  • the method comprises replacing a second input object with a Java applet, wherein said second input object is supported by the client.
  • a method for transferring information between a server and a client, through a converter comprising analyzing at least a portion of the information by said converter, to determine a standard used by said server to encode the information in the portion; and determining at least one portion of said information not supported by said client, wherein said information comprises at least one Internet hypertext document.
  • the method comprises replacing said at least one portion with a portion supported by the client.
  • said standard comprises a language.
  • said standard comprises a standard for an RTL language.
  • a method for transferring information between a server and a client, through a converter comprising: selecting an output portion of said information, which information is designated for the client and comprises at least one Internet hypertext document, which portion has a particular appearance when displayed by a client compatible with output portion; and replacing the output portion with other data, having a similar outward appearance as the output portion, when the other data is displayed by the client for which the information is designated.
  • said other data is image data.
  • said output portion is textual data.
  • selecting an output portion comprises selecting an output portion not compatible with said client.
  • said other data comprises a reference to a data file and wherein said reference encodes at least a portion of the content of said output portion.
  • said other data is generated on-the-fly.
  • said other data is generated at the converter.
  • a method for transferring information between a server and a client, through a converter, each of said client and said server using different standards to encode said information comprising: receiving data from said client; changing said received data from a known standard of the client to a known standard of the server; and transmitting said changed data to said server, wherein said data and said changed data comprise at least one Internet hypertext document.
  • said standards differ in language.
  • said standards differ in logical/visual representation of an RTL language.
  • said standards differ in character set encoding.
  • said standards differ in character bit width.
  • a method for transferring information between a server and a client, through a converter comprising: detecting a text portion of said information by said converter, which portion comprises ordered characters having a meaning in a first representation and which information comprises at least one Internet hypertext document; and changing the order of at least some of said characters, such that the text portion has the same meaning in a second representation.
  • changing the order comprises changing the order characters responsive to a known display method used by said client.
  • apparatus for brokering the transmission of information between a server and a client comprising: a connection to said client; a connection to said server; and a converter which receives an Internet hypertext document from the server through the connection to the server, adds a control to the document and transmits the document to the client through the connection to the client, wherein said control is operable to allow a user to enter configuration information for said converter.
  • control is operable to download a data entry form from said converter.
  • apparatus for brokering the transmission of information between a server and a client comprising: a connection to said client; a connection to said server; and a converter which receives an Internet hypertext document from the server through the connection to the server, changes an object in the document and transmits the changed document to the client through the connection to the client.
  • said converter adds an object to the document.
  • said converter removes an object from the document.
  • said converter replaces an object on the page with another object.
  • said object comprises an object to be displayed by said client.
  • said object comprises an object which accepts input at said client.
  • the apparatus comprises a server.
  • the server and the converter are comprised in a single computer. Alternatively or additionally, the server and the converter operate as a single process.
  • a method for controlling the viewing of copyrighted information, transmitted from a data source to a client, on the Internet comprising: transmitting the information from the data source to a server, wherein said information is in a format viewable by the client; converting the information, at the server, to an encoded form; transmitting the encoded form of the information to the client; and decoding and displaying, at the client, of the encoded information, wherein said encoding and decoding makes said information less available to copying by said client.
  • the format of said information is a format used on the Internet.
  • said format is a HTML format.
  • displaying comprises temporally modulating the display of the information.
  • decoding comprises decoding by a server-provided program.
  • the server-provided program requires a live connection with said server.
  • the server-provided program is downloaded from the server.
  • the method includes authenticating the server-provided program to the server.
  • converting comprises converting said information to a form unusable by said client without said server-provided program. In a preferred embodiment of the invention, converting comprises encrypting.
  • converting the information comprises converting only a portion of the information.
  • FIGS. 1A-1C are schematic diagrams illustrating preferred network topologies for integrating an automatic converter, in accordance with a preferred embodiment of the invention, into a network;
  • Figs. 2A and 2B show a portion of a HTML page before and after automatic conversion, in accordance with a preferred embodiment of the invention
  • Fig. 3 is a flowchart of a process for determining what standards should be used by a converter, in accordance with a preferred embodiment of the present invention
  • Fig. 4 shows a phrase using a visual representation and using a logical representation, for a text mixing an LTR language and an RTL language
  • Fig. 5 is a flowchart of a process for converting input data to a standard recognized by a server, in accordance with a preferred embodiment of the invention
  • Fig. 6 is a flowchart of a process for converting input and output objects in a HTML page, in accordance with a preferred embodiment of the invention.
  • Fig. 7 is a flowchart of a Java applet which enables multi-lingual input on a single language client, in accordance with a preferred embodiment of the invention.
  • FIG. 1A shows a configuration 20 of an interconnection of a server 24 and an automatic converter 22, connected via an Internet 26 to a client 28, in accordance with a preferred embodiment of the present invention.
  • Internet includes also “Intranet” and
  • FIG. 2A shows a portion of an HTML file downloaded by client 28 from WWW server 24.
  • a reference number 10 indicates a text output object to be displayed and a reference number 12 indicates an input request object.
  • Displaying the HTML file at client 28 is usually performed using a browser.
  • client 28 is not capable of displaying text object 10, for example, for lack of a suitable font.
  • client 28 is even more usual that client 28 is not capable of performing the input request 12, for example, if the client does not have a keyboard mapping for the language used by server 24.
  • incompatible portions of the HTML file are automatically converted by converter 22 such that client 28 is capable of displaying the information in text object 10 and/or performing input request 12.
  • this process is substantially invisible to client 28 and server 24.
  • server 24 supplies the file to converter 22.
  • Converter 22 modifies the file, on the fly, so that displaying the information in the file will be within the capabilities of client 28 and sends the modified file to client 28. If input is entered at client 28, which input is not compatible with server 24, converter 22 converts the input to a form usable by server 24.
  • converter 22 replaces input objects with
  • Java applets for example, an applet 16. These Java applets enable a user at client 28 to enter data in a manner which is more comfortable for him and which manner is not otherwise supported by client 28.
  • the applet supports keyboard mapping, character combining and/or different types of display of RTL languages.
  • JavaScript, BasicScript and ActiveX may be used instead of Java, however, they are less preferred due to their technical limitations and because they are not as widely used as Java.
  • Figs. 1A-1C show various configurations for connecting an automatic converter in an
  • Fig. 1A shows configuration 20, where converter 22 is associated with server 24 and separated by Internet 26 from client 28. Thus, communication between converter 22 and server 24 is facilitated.
  • This configuration is useful if converter 22 comprises a proxy server or a gateway for the server.
  • this configuration is not optimal.
  • converter 22 typically increases the volume of data which it transfers and usually adds to the number of files transferred.
  • the file in Fig. 2B is larger than Fig. 2A, even without including the attached image files for Fig. 2B.
  • this increase in file size is deemed to be insignificant, especially when compared to the planned transmission of audio and video information on the Internet and in view of the rapid increase in the available communication bandwidth.
  • the server and the converter are comprised in a single computer.
  • WWW pages are automatically generated by an automatic page generator on server 24 and passed to converter 22, which converts them for client 28.
  • the page generator is incorporated into converter 22, such that they operate as a single (CPU) process. It should be appreciated that server 24 handles the requests from client 28, controls the page generator and, in this embodiment, converter 22.
  • Fig. IB shows a configuration 30 in which a converter 30 is separated from server 24 by an Internet 32 and separated from client 28 by an Intemet 34.
  • this configuration neither communication between converter 30 and client 28 nor communication with server 24 are facilitated.
  • this configuration may be desirable if converter 30 servers as a server or as a translation-service provider which is not associated with any particular client or server.
  • converter 30 preferably adds promotional information to pages downloaded by client 28.
  • Converter 30 may add promotional or other information also in other configurations of connections between converter 30, server 24 and client 28.
  • Fig. 1C shows a configuration 40 in which a converter 38 is associated with client 28.
  • converter 38 may serve as a proxy an/or gateway for client 28.
  • converter 38 is connected by LAN (Local Area Network) to client 28 and possibly to an additional client 36.
  • LAN Local Area Network
  • converter 38 is run on the same computer as client 28. It should be appreciated that since the communication between converter 38 and client 28 is based on TCP/IP, the physical locations of the server, converter and client are transparent, except for issues related to the communication of data.
  • Fig. 3 is a flowchart showing a page reading and conversion process in accordance with a preferred embodiment of the invention. When a page download is requested by client 28, converter 38 receives the desired page from server 24.
  • a parser in converter 38 then parses the page to determine input and output objects. As can be appreciated, if converter 38 is used for converting elements other than input and output objects, the parser will analyze those elements too.
  • the parser can be a very fast parser, because, in a preferred embodiment of the invention the parser does not need to perform a complete syntactic analysis of the page. Rather, the parser can obtain most of the information it needs by identifying the input and output objects and tags in the page. Further, the simplicity of the parser provides some protection against improperly structured WWW pages.
  • the standards used by the server are determined, preferably automatically.
  • the WWW page includes meta-tags which indicate the standard and/or language of particular objects.
  • meta-tags are neither common, nor does a single world-wide standard govern their use.
  • Detecting the standard(s) used by the server or, more usually, limiting the number of possible standards is preferably a heuristic process.
  • One heuristic may be used for detecting the character set-encoding. In a large amount of text, it may be expected that most of the characters are letters. By analyzing the distribution of the character codes, it is usually possible to determine which character codes represent letters, the number of letters in the character set and whether there are special letters at the beginning or at the end of a word.
  • some languages are characterized by a particular distribution of letters in the language, for example in English, the most common letters are T, N, O and E. Further, the distributions at the end of words is different, in many languages, from at the beginning of words. Also, some letter pairs or triplets may be common in a particular language, e.g., "th" and "ing" in English. It is also usually possible to detect which character codes represent numbers. If converter 38 is loaded with most (if not all) of the possible standards, the choice can be limited to those standards which are reasonable in view of the page downloaded from server 24. Preferably, each output object is separately analyzed, since multiple languages and/or standards per page are possible. The set of possible languages may be guessed based on the server location.
  • a particular type of standard which may be determined using these methods is whether an RTL language is stored in a visual or logical manner.
  • RTL languages such as Hebrew
  • the letters at the end of a word may use different glyphs than at the beginning of a word.
  • By detecting an end-letter at a beginning of a word is can be determined whether the language is stored visually rather than logically. If such an end- letter is detected in a middle of a word, than the language is probably not such an RTL language or the character set encoding is not as expected.
  • some RTL language standards use special direction changing control codes, which are not letters and which are usually located in an output object between RTL portion (language) and LTR portions (numbers and other languages). The particular code value of such a control code and its location may also be used to indicate the standard.
  • Such an automatic detection method may fail, at times. This failure may be due to a text portion being too short or ambiguous or it may be due to mistakes in the WWW page.
  • One common mistake in Hebrew is the inadvertent replacement of a regular letter with a similar-looking end-letter.
  • end-letters are sometimes not used in some words.
  • common mistakes and inconsistencies are registered in converter 38 and are ignored thereby.
  • converter 38 adds a control, such as a push-button, to the page.
  • a control such as a push-button
  • the control activates a Java applet which displays a configuration form.
  • the configuration page enables the user to select the standard of the page.
  • data is entered using a form.
  • the user can see the effect of his selection on at least a sample of the page.
  • the user can select a different standard for each portion of the page, using the configuration page.
  • the user may also use the configuration page to indicate the capabilities of client 28.
  • each downloaded page may use a different standard.
  • the user can configure converter 38 with a user-defined standard.
  • a user-defined standard is useful for standards which are not yet registered in converter 38. Also, many standards have small variations, not all of which can be automatically detected.
  • a user can upload a user- defined standard to converter 38.
  • An uploaded standard may include definitions of code ranges, heuristics for determining the standard or even Java applets for affecting the conversion. Java applets may include input-object applets as describe below.
  • the capabilities of the browser at client 28 may be registered using a configuration page, as described above. Altematively, the capabilities of each type of browser are stored in converter 38. Further altematively, converter 38 queries client 28 regarding its browser type and/or its capabilities. If the amount of text entered by the user is sufficient, it may be possible to automatically detect the standard used by client 28.
  • a control on each downloaded WWW page enables an override of the conversion.
  • An override may be required when the client includes a printer having a different type of multi-lingual support than the browser. Also, some cut-and-paste mechanism may not support multi-lingual usage.
  • One example is visual/logical display of RTL languages.
  • Fig. 5 is a flowchart of another aspect of automatic conversion.
  • client 28 sends data to server 24, it may be necessary to convert the standard from a standard used by client 28 to a standard which is usable by server 24.
  • server 24 is a search engine
  • client 28 may enter data using a logical representation.
  • Search engines usually store data using a visual representation, as they are stored using a visual representation in most WWW pages. Thus, if the data is not converted from logical to visual, the search will probably fail.
  • Fig. 4 shows a phrase 70, as it is displayed (visual representation), including two LTR word 72 and 74 and an RTL word 76.
  • phrase 70 is stored using a logical representation, shown as a phrase 78, RTL word 76 is visually meaningless but its letters are ordered in the same way as in most search databases. In such a bi-directional search, a user is well advised to enter the search terms in both visual and logical formats.
  • an input object as described below, allows a user to specify if data is to be visual or logical or both.
  • a search engine registers multilingual pages both before and after conversion by a converter, such as by downloading the pages both directly and through the converter.
  • a converter such as by downloading the pages both directly and through the converter.
  • converter 38 Another problem which can be solved by converter 38 is the problem of illegal form responses. If text in a foreign language is appended to a URL (or POSTed) using the CGI.BIN standard, the characters of the response may interfere with a correct interpretation of the form response by the server. Converter 38 can indicate the existence of a problem to client 28 and recommend the user change his input. In addition, converter 38 may be able to modify the response in a way which will be understandable by server 24, but will not affect the content of the response. An example of such a problem arises when a server sends a page encoded in Unicode
  • Another aspect of conversion of data sent from client 28 to server 24 relates to tags sent in association with the actual data.
  • One such tag is "accept-charset", in which client 28 requests data using a particular charset, since it can only display data in that charset. This indicates the limitations of client 28 to server 24.
  • converter 38 since the use of converter 38, in accordance with preferred embodiments of the present invention, allows even a limited client to display substantially any font, converter 38 preferably modifies this tag (and other such tags) to account for the combined capabilities of converter 38 and client 28. Altematively, converter 38 only changes the "accept-charset" tag if server 24 indicates that it cannot supply the desired information under the "accept-charset” constraint and then resends the request.
  • Fig. 6 is a flowchart of a conversion process of a WWW page in accordance with a preferred embodiment of the invention. First, converter 38 reads and parses a page. The conversion process may be effected in parallel with the parsing or it may be performed after the parsing.
  • converter 38 determines if the output object is supported by client 28, including, mter alia, font, character size and character encoding. If the output object is not supported by client 28, it is converted into a form which is supported by client 28 and the output object is replaced with the converted object(s). For example, in Figs. 2A and 2B, output object 10 is replaced by an output object 14.
  • the output object may be replaced with a different output object which is supported by client 24.
  • the output object may be replaced with a call to a Java applet which renders the output object. Preferably, such an applet is downloaded only once and different data to be rendered is submitted to the applet for each output object.
  • the output object is replaced by one or more image files, which are generated on-the-fly by converter 38.
  • each image preferably corresponds to a small number of words, so that if the output object is resized, the line breaks will look good.
  • text is usually folded over to the following line.
  • relatively small images must be used, so images that do not fit on a line will be pushed to the next line.
  • the number of words in each image is inversely related to the font size. Altematively, each word is placed in a separate file.
  • the image files have a special file extension, such as ".B64", rather than ".GIF" so that the converter can more easily detect this type of file.
  • the converter instructs the browser to display B64 files as GIF files.
  • the names of the created image files encode the content and/or the format of the words they replace. This encoding helps in caching, in garbage collection and, if the client is capable of rendering using a Java applet, it replaces the need to actually download the images, since they can be locally generated.
  • the client since the client receives the content of the output object and not only its image, makes it possible for client 28 to supply a Java applet which searches the contents for textual information. Another benefit is that the converter is relived of the necessity to maintain a table of image files and where they were sent.
  • the following data is preferably encoded in the name: font size (one of seven), font attributes (Italic, Bold, Underline), 24 bits of color and the text content.
  • the following encoding scheme is used: three bits for size, three bits for attributes, 24 bits for color and Nx8 bits for N 8-bit characters.
  • the encoding may also include flags indicating the encoding scheme (such as the number of bits per character).
  • the encoding also includes several bits for the font family and for the language.
  • the preferred encoding is one in which each six bits are represented by one character.
  • the following 64 characters are preferably used to indicate the bit values of between 000000 and 111111 : ABCDEFGHUJKL_VlNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789_@
  • the output object may be used to display a vertically oriented language. Displaying a vertically oriented language may require a Java applet, as will other types of output emulators.
  • converter 38 determines if client 28 is capable of displaying the input object. If client 28 is not capable of displaying the input object or if client 28 requested to use a different input method, which is more convenient than that supplied by his browser, the input object is replaced with a different and, usually more capable, input object.
  • the replacement input object is not an input object which is supported by the client's toolkit. Rather, the input object is a Java applet which embodies the desired input method. The Java applet preferably stays resident, so it does not need to be downloaded from converter 38 very often.
  • Fig. 7 is a flowchart of a Java applet, used for input emulation, in accordance with a preferred embodiment of the present invention.
  • the applet preferably deals with incoming keystrokes on an individual basis. The handling of the keystrokes is dependent on the keyboard mapping supplied by the Java applet. If a keystroke is mapped to a control, the control is executed. Examples of controls include, inter alia, "backspace”, “delete character”, “change language and/or writing direction”, “insert file”, “help” (which displays a help for using the Java applet, and in particular, the keyboard mapping), "connect letters” and "compose letter".
  • a control may display a keyboard mapping (for output only) or a matrix of characters, which can be directly selected using a mouse.
  • the Java applet may use the client toolkit to render the character.
  • the applet need only be capable of rendering characters not supported by the client toolkit.
  • the applet renders the character glyph in the input area.
  • entering a letter or a space, which usually indicates the end of a word
  • the applet rerender a glyph as an word-end letter or even combine two letters automatically.
  • each additional "letter" is an instruction to rerender the glyph.
  • the inputted data should be encoded so as not to interfere with the regular operations of the client and/or server.
  • Java applets have no interaction with any element of the WWW page, except that they can display data in their accorded display area, get input from the input devices, obtain a list of applets on the WWW page, communicate to such applets, open a socket to the applet source and (in most browsers) can request the downloading of a page.
  • One way of sending the data to converter 38 is to replace the submit button, of which each form contains at least one, with a second Java applet which queries the other Java applets in the form before uploading the form contents.
  • the standard submit button only queries input objects, not Java applets.
  • the Java applet sends its contents to converter 38 when the data is entered thereto.
  • converter 38 adds the input data it received from the Java applet to what the submit button sends. If the contents of the Java applet are over- written, it is the last entered data which is sent to server 24.
  • a free-standing input object is supplied with an individual submit button.
  • converter 38 can be used to emulate input/output structures, such as tables, on browsers which do not support tables.
  • converter 38 replaces an unsupported input or output structure with an indication to the user at client 28, of what the unsupported structure is, and preferably, how it may be obtained.
  • the converter renders the unsupported structures and sends them as images and/or as Java applets to display the structures.
  • converter 38 can be used to download Java applets, by demand, to client 28.
  • client 28 can be a simple browser and, when needed, capability expanders in the form of Java applets are downloaded by converter 38 to client 28.
  • Downloading applets as described above is better than replacing portions of the browser and/or using plug-ins.
  • the applets are downloaded with the page that requires them and without any intervention of the client.
  • the applet can only display information and/or handle input, they pose less of a security risk. Downloading capability expanders by demand opens up the possibility that any individual may register a standard or a capability at converter 38, included with which there should be a Java applet for supporting the new features.
  • a client When a client tries to read a WWW page in that standard, the client will receive a capability expander from converter 38.
  • These capabilities are especially useful in Java-based browsers, which can download applets for supporting input and output objects from a converter attached to them by a LAN.
  • a browser may download an updated version of itself or at least an updated version of a portion thereof from a different computer, usually not a converter. It should be appreciated that by converting the WWW pages and appending applets thereto in contrast to modifying the browser itself, there is a minimum of inference with the development of new browsers, since the applets have only a bare minimum of interaction with client 28.
  • text based output objects are replaced with audio output objects. This is especially useful for users who have limited vision.
  • input objects may be replaced with audio input objects.
  • the voice recognition may reside at the client or it may reside at the converter.
  • conversion includes translating from the original language of the WWW page to a language suitable for the client.
  • translation includes transliteration from one writing form to another, such as from Japanese characters to Latin characters.
  • translation includes detecting the original language of the page, translating it and replacing the original text with the new text. The same process may be performed when translating input entered at client 28.
  • Another aspect of the present invention relates to converting data so as to reduce readability by client 28.
  • One of the bothersome problems with the Intemet is that once copyrighted information is transmitted to one computer, it can be retransmitted to many computers without any control or reimbursement of the copyright owner.
  • a particular case is where, in a large organization, one user buys certain information from an information provider and then distributes copies of the information, by LAN to many other workers in the organization.
  • the copyright owner would be satisfied if the users of the information paid for each copy of the information or if they are forced to view commercial information, such as advertisements, when viewing the copyrighted information.
  • the copyright owner can then charge money from the advertiser, for advertising space.
  • copyrighted information is textual information, however, copyrighted information also includes audio and image information.
  • copyrighted information is presented, on a computer, in such a manner that it is easily accessible to the senses of a consumer, but not easily accessible to data manipulation tools on the computer.
  • a first interception point is when the data is presented on a display. Once a screenfull of text data is displayed the screen can be photographed or an image of the screen can be captured and then printed. In a preferred embodiment of the invention, the displayed data is temporally modulated so that at any given instant only a small portion of the data is displayed. Thus, an image of the screen is not useful for a copyright infringer.
  • the data may be temporally modulated using one of two schemes, the data may exist on the client computer and be displayed in a temporally modulated manner or the data may be downloaded, using a live connection, from the server, so that only a small portion of the data is on the client computer at any given moment.
  • data is temporally modulated by only showing a small amount of data on a screen at a time, the rest preferably being taken up by advertisements.
  • an infringer would be required to capture many screens and to piece together many data portions from these screens.
  • the location of the data portion changes between screens to increase the difficulty of automatically piecing together of the data portions.
  • the copyrighted information is intermixed with the advertisements in such a manner that it can be easily separated by a human, but not by standard data manipulation programs.
  • One example of such a display is using a different fonts or font sizes for the advertisements and for the copyrighted information.
  • the data is temporally modulated at a high enough frequency that a human can integrate the displayed data, but a screen image will only capture part of the data.
  • a human can integrate the displayed data
  • a screen image will only capture part of the data.
  • Another example is highlighting only a few words at a time, while the rest of the text is on a dark background.
  • Yet another example, is displaying the data in a moving strip, such that only a portion of the data is simultaneously displayed.
  • a second interception point is at the data display program itself. For example, when a
  • the data display program (usually a browser) sends that data files directly to the printer.
  • the data is not available to the data display program.
  • the data is made unavailable, by encoding it using an encoding scheme not recognized by the browser, but only by a server-supplied Java applet. This is an opposite to the usually situation, where the data is originally encoded in an unrecognizable manner.
  • the Java- applet "knows" how to print the data and will do so at the request of the browser.
  • the Java applet will not print the data, since that would be counter-productive to the protection of the data.
  • the encoding scheme can include, changing the character codes, using an unsupported font and changing the order of characters.
  • the Java applet may be downloaded anew each information transfer or it may be locally resident at the client.
  • a data provider may supply a data display program, such as a browser, or even an add-in, which incorporates the functionality of the Java applet.
  • the Java applet transmits back to the server various information regarding, number of uses, a user number (for charging fees) and the like.
  • an encapsulated copy of the copyrighted information including both the encoded data and Java applet may be freely distributed, since, in order to view the data, some sort of control by the copyright owner will be exercised.
  • the data is encoded using a cipher.
  • each data packet is sent with a different key, so that continuous connection with the original provider of the data is necessary in order to decode the data.
  • the key is time coded so that a live connection to the data source is required.
  • the encoding may include public-key encoding, in accordance with a preferred embodiment of the invention. It should be noted that not all the data need be encoded, it usually is only necessary to hide enough of the data so that the remaining information is degraded beyond a point which makes plain copying feasible. This type of encoding is also useful for audio-visual data, for example, for controlling viewing of pay-by-view movies in cable television systems.
  • a live connection between the Java applet and the server is preferred to reduce the chances of a "pirate" program disguising itself as a client.
  • the client is required to identify itself using a new code each time it runs.
  • the server may maintain a list of all the used codes. Thus, data can only be displayed once using a particular code and additional displays required a new code.
  • the server also provides multi-use codes which limit the display of data to a small number of times. Altematively or additionally, only a small portion of the information, such as an abstract, can be viewed without a proper code. Altematively or additionally, the server uses a code to authenticate clients.
  • the server sends a code to the client and the client is expected to send back a second code which is a function of the first code.
  • a "pirate" program will probably not be able to respond with the correct code, especially if different codes are used each time by the server. It should be appreciated that only the codes need to be transmitted, not all the data, so the required bandwidth is very narrow.
  • the Java applet is compiled in a manner to make it difficult to reverse engineer.
  • the data is displayed using graphical display functions rather than text based display functions, so as to limit the ease of eavesdropping on the data as it is displayed.
  • the text is not displayed in a serial order, as is common, but in a random fashion, such that the display commands need to be analyzed in order to reconstruct the correct order of the displayed text. It should be appreciated that requiring a would-be infringer to store images rather than text data increases the cost of infringement to a point where it will usually not be practiced.
  • data is sent in a format which is suitable only for display, such as a low resolution graphical format.
  • Printing such a display results in inferior quality copies.
  • One example is works of art, which are currently transmitted at full quality.
  • only an inferior quality of the data will be sent, suitable only for a particular display, unless a certain fee is paid or advertisements viewed.
  • a conversion server performs the conversion and/or the communication with the clients, on demand.
  • the converter only encodes the copyrighted information and not any associated advertisements.
  • an information provider sends the copyrighted information from a data source, in its original form, to the conversion server and the conversion server converts the data to a form which is accessible to the (human) client, but not to the (computer) client.
  • the conversion server can then provide various services in a centralized manner, including, customer payments and partitioning advertisements for particular market sectors.
  • the server is added on as a gateway to the data source.
  • the data which is transmitted from the data source to the conversion server is already in a format suitable for the client, such as HTML.
  • the data is preferably transmitted from the data source using an Intemet protocol, such as a WWW protocol.
  • converter 38 is a general purpose computer with appropriate software.
  • converter 38 may be a dedicated computer based on Java.
  • converter 38 may also be embodied as part of a server computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un procédé permettant de transmettre des informations entre un serveur (24) et un client (28) par l'intermédiaire et d'un convertisseur (22), qui comprend les étapes suivantes: le convertisseur (22) analyse au moins une partie des informations, de façon à déterminer la norme utilisée par le serveur (24) pour coder les informations contenues dans ladite partie; puis il remplace au moins une partie des informations analysées par des informations utilisant une seconde norme. L'analyse comprend l'analyse des informations au niveau de la syntaxe et lesdites informations appartiennent au moins à un document hypertexte transmis par Internet.
EP98909722A 1997-03-27 1998-03-24 Systeme de conversion automatique Ceased EP0976053A4 (fr)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US4162397P 1997-03-27 1997-03-27
US41623P 1997-03-27
IL12107197 1997-06-12
IL12107197A IL121071A0 (en) 1997-03-27 1997-06-12 Automatic conversion server
PCT/IL1998/000134 WO1998044424A1 (fr) 1997-03-27 1998-03-24 Systeme de conversion automatique

Publications (2)

Publication Number Publication Date
EP0976053A1 true EP0976053A1 (fr) 2000-02-02
EP0976053A4 EP0976053A4 (fr) 2005-09-21

Family

ID=26323449

Family Applications (1)

Application Number Title Priority Date Filing Date
EP98909722A Ceased EP0976053A4 (fr) 1997-03-27 1998-03-24 Systeme de conversion automatique

Country Status (4)

Country Link
EP (1) EP0976053A4 (fr)
AU (1) AU6417998A (fr)
IL (3) IL129633A (fr)
WO (1) WO1998044424A1 (fr)

Families Citing this family (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6298446B1 (en) 1998-06-14 2001-10-02 Alchemedia Ltd. Method and system for copyright protection of digital images transmitted over networks
IL124895A0 (en) * 1998-06-14 1999-01-26 Csafe Ltd Methods and apparatus for preventing reuse of text images and software transmitted via networks
EP1149443A4 (fr) 1998-09-11 2006-03-22 New Focus Inc Laser accordable
EP1001330A3 (fr) * 1998-11-16 2006-03-29 Finjan Software, Ltd. Méthode et système pour la protection du droit d'auteur lors de la transmission d'images numériques sur réseaux
US7168086B1 (en) * 1998-11-30 2007-01-23 Microsoft Corporation Proxy for video on demand server control
US6392664B1 (en) 1998-11-30 2002-05-21 Webtv Networks, Inc. Method and system for presenting television programming and interactive entertainment
US6804825B1 (en) 1998-11-30 2004-10-12 Microsoft Corporation Video on demand methods and systems
US6628302B2 (en) 1998-11-30 2003-09-30 Microsoft Corporation Interactive video programming methods
CA2393930A1 (fr) * 1999-08-02 2001-02-08 Harris Interactive, Inc. Systeme de protection d'informations sur internet
US6993476B1 (en) 1999-08-26 2006-01-31 International Business Machines Corporation System and method for incorporating semantic characteristics into the format-driven syntactic document transcoding framework
JP2001084183A (ja) 1999-09-17 2001-03-30 Nec Corp データ変換システム
EP1103351B1 (fr) 1999-10-26 2007-09-05 Sony France S.A. Méthode et système de télétransfert d'agent pour robot
US8090856B1 (en) 2000-01-31 2012-01-03 Telecommunication Systems, Inc. Intelligent messaging network server interconnection
US6721804B1 (en) * 2000-04-07 2004-04-13 Danger, Inc. Portal system for converting requested data into a bytecode format based on portal device's graphical capabilities
US7209498B1 (en) 2000-05-04 2007-04-24 Intel Corporation Method and apparatus for tuning a laser
US7483983B1 (en) 2000-11-13 2009-01-27 Telecommunication Systems, Inc. Method and system for deploying content to wireless devices
US8458754B2 (en) 2001-01-22 2013-06-04 Sony Computer Entertainment Inc. Method and system for providing instant start multimedia content
US6658031B2 (en) 2001-07-06 2003-12-02 Intel Corporation Laser apparatus with active thermal tuning of external cavity
US6901088B2 (en) 2001-07-06 2005-05-31 Intel Corporation External cavity laser apparatus with orthogonal tuning of laser wavelength and cavity optical pathlength
US6724797B2 (en) 2001-07-06 2004-04-20 Intel Corporation External cavity laser with selective thermal control
US7191233B2 (en) 2001-09-17 2007-03-13 Telecommunication Systems, Inc. System for automated, mid-session, user-directed, device-to-device session transfer system
US7426535B2 (en) 2002-10-08 2008-09-16 Telecommunication Systems, Inc. Coordination of data received from one or more sources over one or more channels into a single context
US7502729B2 (en) * 2003-12-19 2009-03-10 International Business Machines Corporation Emulating different country keyboards for controlling a remote computer over a network
US9483405B2 (en) 2007-09-20 2016-11-01 Sony Interactive Entertainment Inc. Simplified run-time program translation for emulating complex processor pipelines
US9100585B2 (en) 2008-10-28 2015-08-04 Sony Computer Entertainment Inc. Combined broadcast and backchannel delivery of streaming content

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5522041A (en) * 1992-12-17 1996-05-28 Hitachi, Ltd. Data processor and data transfer method

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
GAVIN NICOL: "The Multilingual World Wide Web" INTERNET CITATION, [Online] November 1994 (1994-11), pages 1-17, XP002338120 Retrieved from the Internet: URL:http://www.oasis-open.org/cover/nicol-multwww.html> [retrieved on 2005-07-26] *
KIKUI ET AL: "Identifying the coding system and language of on-line documents on the internet" INTERNATIONAL CONFERENCE ON COMPUTATIONAL LINGUISTICS. PROCEEDINGS OF COLING, August 1996 (1996-08), pages 652-657, XP002099142 *
KIKUI G ET AL: "Cross-lingual Information retrieval on the WWW (URL)" PROCEEDINGS EUROPEAN CONFERENCE ON ARTIFICIAL INTELLIGENCE, CHICHESTER,, GB, 1996, pages 1-6, XP002099141 *
SAKAGUCHI T ET AL: "A BROWSING TOOL FOR MULTI-LINGUAL DOCUMENTS FOR USERS WITHOUT MULTI-LINGUAL FONTS" PROCEEDINGS OF THE ACM INTERNATIONAL CONFERENCE ON DIGITAL LIBRARIES, 20 March 1996 (1996-03-20), pages 63-71, XP002919648 *
See also references of WO9844424A1 *
TAKADA T: "Multilingual information exchange through the World-Wide Web" COMPUTER NETWORKS AND ISDN SYSTEMS, NORTH HOLLAND PUBLISHING. AMSTERDAM, NL, vol. 27, no. 2, November 1994 (1994-11), pages 235-241, XP004037994 ISSN: 0169-7552 *

Also Published As

Publication number Publication date
IL129633A0 (en) 2000-02-29
IL159560A (en) 2010-02-17
AU6417998A (en) 1998-10-22
IL159560A0 (en) 2004-06-01
WO1998044424A1 (fr) 1998-10-08
EP0976053A4 (fr) 2005-09-21
IL129633A (en) 2004-09-27

Similar Documents

Publication Publication Date Title
US6601108B1 (en) Automatic conversion system
WO1998044424A1 (fr) Systeme de conversion automatique
US7073121B2 (en) Web page thumbnails and user configured complementary information provided from a server
US6338096B1 (en) System uses kernals of micro web server for supporting HTML web browser in providing HTML data format and HTTP protocol from variety of data sources
KR100310760B1 (ko) 인터넷웹페이지의국제적지원을위한방법및시스템
US6405192B1 (en) Navigation assistant-method and apparatus for providing user configured complementary information for data browsing in a viewer context
KR100317401B1 (ko) 관련된웹페이지를인쇄하기위한장치및방법
US6925595B1 (en) Method and system for content conversion of hypertext data using data mining
US6944822B1 (en) Method and apparatus for preventing reuse of text, images, and software transmitted via networks
US5848413A (en) Method and apparatus for accessing and publishing electronic documents
US7058944B1 (en) Event driven system and method for retrieving and displaying information
US20080154911A1 (en) System and method for on-line generation of asian documents with multiple font faces
US20020169829A1 (en) Method, apparatus and system for directing access to content on a computer network
US20110093565A1 (en) Serving Font Files in Varying Formats Based on User Agent Type
GB2347329A (en) Converting electronic documents into a format suitable for a wireless device
JP2000090001A (ja) 変換設定を使用した電子デ―タの変換方法およびシステム
WO2003052582A1 (fr) Systeme et procede d'affichage de document
CA2344074A1 (fr) Methode et systeme de creation et de transmission de formulaires multi-plate-forme
CN111683098B (zh) 反爬虫方法、装置、电子设备及存储介质
US6253229B1 (en) Hotspots only interfaces to links in hypertext document pages in network display stations
US6636235B1 (en) Lettering adjustments for display resolution
GB2377294A (en) Transmitting information with content appropriate to receiving device and user
JPH10289206A (ja) ホームページ通信システム
US6192383B1 (en) Method and system in a computer network for automatically adding synchronization points to network documents
US6763355B2 (en) Method and apparatus in mark-up language documents for providing mark-up language hidden attributes

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 19991027

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): DE FI FR GB IT NL SE

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NETMASK (EL-MAR) INTERNET TECHNOLOGIES LTD.

A4 Supplementary search report drawn up and despatched

Effective date: 20050809

RIC1 Information provided on ipc code assigned before grant

Ipc: 7G 06F 17/30 A

17Q First examination report despatched

Effective date: 20060629

APBK Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNE

APBN Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2E

APBR Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3E

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: GOOGLE INC.

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20150507

REG Reference to a national code

Ref country code: HK

Ref legal event code: WD

Ref document number: 1025643

Country of ref document: HK

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230519