The present disclosure relates generally to rendering text on an computing device and in particular to rendering text in collaborative document processing systems.
Traditionally, the viewing and editing of electronic documents—such as word processing documents, spreadsheets, and presentations—was done using specific software applications installed on a computing device. Recently, online document processing applications have been developed which makes it possible for people to create these documents without having document processing software specially installed. These online applications provide access to the document processing features through an Internet browser. The actual documents are stored on the application server, but may be downloaded locally to a client computing device. Because the documents are stored centrally and are accessed via an Internet browser, it is possible for multiple people to view, edit, and share the document regardless of the hardware and software capabilities of the computing device they are using.
The appearance of the same text in an electronic document may differ from one computing device to another. In particular, the appearance of the same text may differ among various Internet browsers. For example, the height or width of the characters may be different or the line breaks may occur at different points in the text. There are several reasons for these differences. Browsers may have different versions of the same font installed. Browsers may also use different algorithms for kerning (determining the amount of space between characters), layout, sizing, or rendering. Furthermore, some browsers may engage in sub-pixel rendering if the display screen of the computing device allows.
In online document processing applications, uniform appearance of text is important. If the size and line breaks of the text do not appear the same across different computing devices, it can cause confusion among different users who view or edit the document from different computing devices. Current solutions to the uniform text rendering problem generally have relied on having the same display or rendering program installed in each computing device.
It is preferable to find a solution that can display text uniformly regardless of the hardware or software capabilities of the computing device. Systems and methods are disclosed herein for rendering text on a client computing device by a server. In one aspect, a computerized method includes sending text from a server to the client computing device for rendering and receiving at the server initial text formatting information from the client computing device. The method further includes generating revised text formatting information on the server and sending the revised text formatting information from the server to the client computing device for re-rendering of the text in accordance with the revised text formatting information.
In another aspect, a computerized method for displaying a document on a plurality of client computing devices by a server includes sending the document from the server to the plurality of client computing devices and receiving initial text formatting information at the server from a first client computing device in the plurality of client computing devices. The method further includes generating revised text formatting information on the server for the first client computing device in the plurality of client computing devices and sending the revised text formatting information from the server to the first client computing device in the plurality of client computing devices for re-rendering of the document so that the document text appears substantially the same on each client computing device.
In another aspect, a system for displaying a document on a plurality of client computing devices includes a server. The server is configured to send the document to the plurality of client computing devices, receive initial text formatting information from each client computing device, generate revised text formatting information for each client computing device, and send the revised text formatting information to each client computing device for re-rendering of the document so that the document text appears substantially the same on each client computing device.
In another aspect, a computerized method for re-rendering text on a client computing device by a server includes receiving initial text formatting information at the server from the client computing device. The method further includes generating revised text formatting information on the server and sending the revised text formatting information from the server to the client computing device for re-rendering of the text in accordance with the revised text formatting information.
In another aspect, a computerized method for server-side rendering of text on a client computing device includes receiving text from the server on the client computing device, generating initial text formatting information on the client computing device, and sending the initial text formatting information to the server. The method further includes receiving revised text formatting information from the server and re-rendering the text in accordance with the revised text formatting information.
The methods and systems may be better understood from the following illustrative description with reference to the following drawings in which:
To provide an overall understanding of the invention, certain illustrative embodiments will now be described, including systems and methods for displaying a document on a plurality of client computing devices by a server. However, it will be understood by one of ordinary skill in the art that the systems and methods described herein may be adapted and modified as is appropriate for the application being addressed and that the systems and methods described herein may be employed in other suitable applications, and that such other additions and modifications will not depart from the scope thereof.
The server in client-server system 100 will now be discussed in greater detail.
Processor 201 may be configured to perform tasks such as sending electronic documents stored in database 211 to multiple client computing devices using communications interface 205, receiving edits to electronic documents stored in database 211 from client computing devices, and generating text formatting information to be displayed on client computing devices. Processor 201 may be configured to ensure that documents stored in database 211 and distributed to different computing devices will have uniform appearance of text across the client computing devices.
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from RAM or ROM or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Computer-readable media suitable for storing computer program instructions and data, such as database 211, include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
The interaction of a client computing device and the server will now be discussed.
Methods of operation of the server in the client-server system are now discussed.
After the server sends a segment of text to the computing device, the computing device uses local formatting information stored on the computing device to produce initial text formatting information. This initial text formatting information may include the width and height of each character, the location of line-breaks within the text, or text styling information (e.g. italics, underline). The initial text formatting information may pertain to an individual character, entire words, prefixes of words, or any other grouping of text. The computing device sends the initial text formatting information to the server in step 403.
When the server receives the initial text formatting information from the computing device, the server generates revised text formatting information in step 405. In some embodiments, the server uses Java or 2-D application programming interface (API) programs to generate the revised text formatting information. The server generates the revised text formatting information to ensure a uniform appearance of the text if the text was displayed on multiple computing devices. Thus the revised text formatting information may have different widths and heights for characters than in the initial text formatting information or may change the location of line-breaks within the text. In some embodiments, the revised text formatting information may be the same as the initial text formatting information, indicating that the computing device has already correctly rendered the text. In some embodiments, the server has a cache that stores revised text formatting information for retrieval in case a computing device requests formatting information for the same text segment.
After the server generates the revised text formatting information, the server sends this information to the computing device in step 407. Once the computing device receives the revised text formatting information, it can re-render any segments of text where the revised text formatting information differs from the initial text formatting information. In some embodiments, the revised text formatting information is stored in a cache on the computing device. If the same piece of text is re-rendered at a later time, the computing device can retrieve the revised text formatting information from its cache rather than communicating with the server again. Thus method 400 enables a server to control the rendering of text on a computing device to ensure uniform appearance of text across a variety of computing devices.
Next, methods of rendering documents on multiple computing devices using a server are discussed.
After the server sends the document to each computing device, the computing devices uses local rendering information stored on each of the computing devices to produce initial text formatting information. This initial text formatting information may include the width and height of each character, the location of line-breaks within the text, or text styling information. The initial text formatting information may pertain to an individual character, entire words, prefixes of words, or any other grouping of text. Each computing device sends its initial text formatting information to the server in step 503.
When the server receives the initial text formatting information from a computing device in the plurality of computing devices, the server generates revised text formatting information for the computing device in step 505. In some embodiments, the server uses Java or 2-D application programming interface (API) programs to generate the revised text formatting information. The revised text formatting information may have different widths and heights for characters or may change the location of line-breaks within the text. The server generates the revised text formatting information to ensure a uniform appearance of the text across the plurality of computing devices. Thus the revised text formatting information generated by the server for the same segment of text should be the same for all computing devices. For some computing devices, the revised text formatting information may be the same as the initial text formatting information, indicating that the computing device has already correctly rendered the text. In some embodiments, the server has a cache that stores revised text formatting information for retrieval in case another computing device requests formatting information for the same text segment.
After the server generates the revised text formatting information, the server sends this information to the computing device in step 507. Once the computing device receives the revised text formatting information, it can re-render any segments of text where the revised text formatting information differs from the initial text formatting information. In some embodiments, the revised text formatting information is stored in a cache on the computing device. If the same piece of text is re-rendered at a later time, the computing device can retrieve the revised text formatting information from its cache rather than communicating with the server again. Thus method 500 enables a server to control the rendering of text on a plurality of computing devices to ensure uniform appearance of text.
It will be apparent to one of ordinary skill in the art that aspects of the invention, as described above, may be implemented in many different forms of software, firmware, and hardware in the implementations illustrated in the figures. The actual software code or specialized control hardware used to implement aspects consistent with the principles of the invention is not limiting of the invention. Thus, the operation and behavior of the aspects of the invention were described without reference to the specific software code—it being understood that one of ordinary skill in the art would be able to design software and control hardware to implement the aspects based on the description herein.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous.
Further, certain portions of the invention may be implemented as “logic” or a “component” that performs one or more functions. This logic may include hardware, such as an application specific integrated circuit or a field programmable gate array, software, or a combination of hardware and software.
Number | Name | Date | Kind |
---|---|---|---|
5231577 | Koss | Jul 1993 | A |
5408470 | Rothrock et al. | Apr 1995 | A |
5557722 | DeRose et al. | Sep 1996 | A |
5758358 | Ebbo | May 1998 | A |
5761669 | Montague et al. | Jun 1998 | A |
5793966 | Amstein et al. | Aug 1998 | A |
5819304 | Nilsen et al. | Oct 1998 | A |
6049664 | Dale et al. | Apr 2000 | A |
6243706 | Moreau et al. | Jun 2001 | B1 |
6327584 | Xian et al. | Dec 2001 | B1 |
6341305 | Wolfe | Jan 2002 | B2 |
6349308 | Whang et al. | Feb 2002 | B1 |
6349314 | Patel | Feb 2002 | B1 |
6418441 | Call | Jul 2002 | B1 |
6501779 | McLaughlin et al. | Dec 2002 | B1 |
6766333 | Wu et al. | Jul 2004 | B1 |
6988241 | Guttman et al. | Jan 2006 | B1 |
7017112 | Collie et al. | Mar 2006 | B2 |
7031954 | Kirsch | Apr 2006 | B1 |
7035910 | Dutta et al. | Apr 2006 | B1 |
7069502 | Numata et al. | Jun 2006 | B2 |
7162693 | Yamanaka et al. | Jan 2007 | B2 |
7213199 | Humenansky et al. | May 2007 | B2 |
7437421 | Bhogal et al. | Oct 2008 | B2 |
7478330 | Branson et al. | Jan 2009 | B1 |
7491399 | Vakharia | Feb 2009 | B2 |
7506242 | Kotler et al. | Mar 2009 | B2 |
7529778 | Dewey et al. | May 2009 | B1 |
7656543 | Atkins | Feb 2010 | B2 |
7680932 | Defaix et al. | Mar 2010 | B2 |
7698379 | Dutta et al. | Apr 2010 | B2 |
7774703 | Junuzovic et al. | Aug 2010 | B2 |
7890928 | Patrudu | Feb 2011 | B2 |
8019780 | Pinkerton et al. | Sep 2011 | B1 |
8151204 | Lusen et al. | Apr 2012 | B2 |
8266534 | Curtis et al. | Sep 2012 | B2 |
20010037346 | Johnson | Nov 2001 | A1 |
20020032701 | Gao et al. | Mar 2002 | A1 |
20020035580 | Tanabe | Mar 2002 | A1 |
20020133492 | Goldstein et al. | Sep 2002 | A1 |
20020174085 | Nelson et al. | Nov 2002 | A1 |
20030014406 | Faieta et al. | Jan 2003 | A1 |
20030037076 | Bravery et al. | Feb 2003 | A1 |
20030037303 | Bodlaender et al. | Feb 2003 | A1 |
20030084078 | Torii et al. | May 2003 | A1 |
20040044965 | Toyama et al. | Mar 2004 | A1 |
20040085354 | Massand | May 2004 | A1 |
20040088653 | Bell et al. | May 2004 | A1 |
20040133444 | Defaix et al. | Jul 2004 | A1 |
20040215672 | Pfitzner | Oct 2004 | A1 |
20040215825 | Pfitzner | Oct 2004 | A1 |
20040215826 | Pfitzner | Oct 2004 | A1 |
20040216090 | Kaler et al. | Oct 2004 | A1 |
20040248612 | Lee et al. | Dec 2004 | A1 |
20050091291 | Kaler et al. | Apr 2005 | A1 |
20050125461 | Filz | Jun 2005 | A1 |
20050131887 | Rohrabaugh et al. | Jun 2005 | A1 |
20050185636 | Bucher | Aug 2005 | A1 |
20050200896 | Narusawa et al. | Sep 2005 | A1 |
20050273695 | Schnurr | Dec 2005 | A1 |
20060031751 | Ehud | Feb 2006 | A1 |
20060075332 | Fairweather et al. | Apr 2006 | A1 |
20060101071 | Henderson | May 2006 | A1 |
20060149831 | Dutta et al. | Jul 2006 | A1 |
20060200755 | Melmon et al. | Sep 2006 | A1 |
20060230344 | Jennings et al. | Oct 2006 | A1 |
20070033654 | Wilson | Feb 2007 | A1 |
20070061714 | Stuple et al. | Mar 2007 | A1 |
20070070066 | Bakhash | Mar 2007 | A1 |
20070186157 | Walker et al. | Aug 2007 | A1 |
20070208992 | Koren | Sep 2007 | A1 |
20070220068 | Thompson et al. | Sep 2007 | A1 |
20070288637 | Layton et al. | Dec 2007 | A1 |
20080028302 | Meschkat | Jan 2008 | A1 |
20080040659 | Doyle | Feb 2008 | A1 |
20080059417 | Yamada et al. | Mar 2008 | A1 |
20080059539 | Chin et al. | Mar 2008 | A1 |
20080082604 | Mansour et al. | Apr 2008 | A1 |
20080126943 | Parasnis et al. | May 2008 | A1 |
20080127212 | Nakamizo et al. | May 2008 | A1 |
20090112953 | Barsness et al. | Apr 2009 | A1 |
20090112990 | Campbell et al. | Apr 2009 | A1 |
20090132907 | Shao et al. | May 2009 | A1 |
20090307585 | Tranchant et al. | Dec 2009 | A1 |
20100030578 | Siddique et al. | Feb 2010 | A1 |
20100059539 | Giraud et al. | Mar 2010 | A1 |
20100083096 | Dupuis-Latour et al. | Apr 2010 | A1 |
20100205230 | Simeonov et al. | Aug 2010 | A1 |
20100205520 | Parish et al. | Aug 2010 | A1 |
20100218099 | van Melle et al. | Aug 2010 | A1 |
20100235763 | Massand | Sep 2010 | A1 |
20100245256 | Estrada et al. | Sep 2010 | A1 |
20100251122 | Lee et al. | Sep 2010 | A1 |
20100252335 | Orsley | Oct 2010 | A1 |
20100318894 | Billharz et al. | Dec 2010 | A1 |
20110066957 | Prats et al. | Mar 2011 | A1 |
20110085211 | King et al. | Apr 2011 | A1 |
20110099093 | Mills | Apr 2011 | A1 |
20110164043 | Arora et al. | Jul 2011 | A1 |
20110179427 | Krishnamoorthy et al. | Jul 2011 | A1 |
20110219331 | Deluca et al. | Sep 2011 | A1 |
20110252299 | Lloyd et al. | Oct 2011 | A1 |
20110264712 | Ylonen | Oct 2011 | A1 |
20120117406 | Eun | May 2012 | A1 |
20120117452 | Lloyd et al. | May 2012 | A1 |
20120131483 | Archer et al. | May 2012 | A1 |
Entry |
---|
Ellis et al., “Concurrency Control in Groupware Systems,” ACM 1989, pp. 399-406. |
Huang et al., “A General Purpose Virtual Collaboration Room,” Google 1999, pp. 1-9. |
Kindberg, Mushroom: A Framework for Collaboration and Interaction across the Internet, Google 1996, pp. 1-11. |
Pacull et al., Duplex: A Distributed Collaborative Editing Environment in Large Scale, ACM 1994, pp. 165-173. |
Tsompanopoulou et al., “A Platform for Delivering Multimedia Presentations on Cultural Heritage,” 2010 14th Panhellenic Conference on Informatics, pp. 175-179. |
Non-Final Office Action dated Jan. 6, 2012 for U.S. Appl. No. 13/275,093. |
Non-Final Office Action dated Jan. 17, 2012 for U.S. Appl. No. 13/274,717. |
Non-Final Office Action dated Feb. 17, 2012 for U.S. Appl. No. 13/275,123. |
Non-Final Office Action dated Feb. 29, 2012 for U.S. Appl. No. 13/274,723. |
Non-Final Office Action dated Mar. 1, 2012 for U.S. Appl. No. 13/275,101. |
Non-Final Office Action dated Dec. 30, 2011 for U.S. Appl. No. 13/274,720. |
Krieger, Stephanie “Documents, Presentations, and Workbooks: Using Microsoft® Office to Create Content That Gets Noticed,” published May 2011, pp. 1-104. |
Raggett, Dave “Slidy—a web based alternative to Microsoft PowerPoint,” published 2006, pp. 1-13. |
“Simultaneously edit a presentation with other authors,” by MicrosoftTM Office: MAC, published Nov. 11, 2010, pp. 1-4. |
Taylor, Dave “Cool Apple Keynote Presentation Tricks and Tips,” published Apr. 2011, p. 1-5. |
Non Final Office Action dated Jul. 20, 2012 for U.S. Appl. No. 13/084,951. |
Non Final Office Action dated Aug. 31, 2012 for U.S. Appl. No. 13/275,101. |
Advisory Action dated Sep. 7, 2012 for U.S. Appl. No. 13/274,723. |
Non Final Office Action dated Sep. 7, 2012 for U.S. Appl. No. 13/226,165. |
Non-Final Office Action dated Oct. 24, 2012 for U.S. Appl. No. 11/497,206. |
Final Office Action dated Dec. 7, 2012 for U.S. Appl. No. 13/275,123. |
Final Office Action dated Nov. 16, 2012 for U.S. Appl. No. 13/274,716. |