Abstract: Methods, computer readable media, and apparatuses for font matching are presented. A glyph may be received and processed. The processing of the received glyph may include reducing the glyph, computing bounds associated with the glyph, and normalizing the glyph. The processed glyph may be compared to a repository of image prototypes. The comparison may include determining a distance of the processed glyph from one or more the image prototypes, sorting the determined distances, and selecting one or more of the image prototypes based on the determined distances. Additional techniques may be used to enhance the resolution or accuracy associated with the various methods and algorithms.

Abstract: Systems and methods are presented that process documents, identify fonts being used to reproduce the documents, and identify conflicts based on the identified fonts. The systems and methods may identify a font associated with a document, identify a conflict between the font and another font, determine a substitute font for the document, and then modify information of the substitute font and the document based on the conflict to prevent the identified conflict from causing the document to be incorrectly processed. The systems and methods may then allow the document to be further processed based on the modified information.

Abstract: Methods, computer readable media, and apparatuses for preventing unauthorized font linking are presented. A request for a font file may be received. It may be determined whether the request is valid, and this determination may be based on a security token and/or a referrer string. If the request is determined to be valid, a first watermark may be embedded in the font file, and the first watermark may be based on the security token. The first watermark may include at least one point in at least one glyph contained in the font file. A second watermark may be embedded in the font file, and the second watermark may include at least one table that identifies a customer. The font file then may be served to the requestor.

Abstract: Aspects of this disclosure relate to a system and method for loading and viewing a web page in a browser to preview fonts without altering the constituent elements of the web page. According to one or more aspects of this disclosure, the system may include a browser for viewing a web page and previewing fonts on the web page. According to one or more aspects of this disclosure, the method may include receiving a web page at a browser, storing a representation of the web page into a memory, rendering the representation of the web page, receiving a selection of one or more elements of the web page, receiving a font property that specifies a change to a font type and/or a font size, and applying the specified font property to the selected elements.

Abstract: Fonts may be activated based on the applications that are launched or operating on a computing device. Accordingly, if an application needs a particular set of fonts, the fonts may be activated upon launching of that application. Fonts may further be deactivated when they are no longer necessary or needed by the application (e.g., when the application is terminated). If supported by an operating system, instead of activating and deactivating the fonts, fonts may be pre-activated and then hidden from the operating system. The pre-activated fonts may be revealed when needed for the applications and then hidden again when the applications terminate.

Abstract: To resolve compatibility issues between font file formats and user agents such as web browsers, a font repository may determine a compatible font file format upon receiving a request from the user agent for a font. The determination may be made based on the type of user agent making the request. In one or more arrangements, if a font file in the compatible font file format is not available at the repository, a request may be transmitted to another repository. A font reference in a style sheet or code defining the network document may be unique to the font, but common to all font files corresponding to the font. An application for facilitating the generation of a network document may thus automatically generate such a code in response to a user selecting a desired font.

Abstract: Documents that are created using a particular font often do not include all glyphs defined for the font. Accordingly, to reduce the amount of bandwidth needed to obtain the font used to create the document over a network, a font file may be created that includes a reduced set of glyphs. In one or more examples, the font file might only include the glyphs used in the document being viewed. Reduced glyph font files may be generated on-the-fly and/or cached for quick retrieval at a later time.

Abstract: Text may be contextually previewed in various fonts using preview panes with a level of transparency. Fonts or font groups may then be applied to a document using the preview panes. In one example, text to be inserted may be previewed in different fonts against the document in which the text is to be added. Once a user has selected a desirable font, the user may choose to insert the text into the document using the preview pane. Alternatively, a user may apply a font to existing text from the preview pane. Text in fonts of different types and/or sizes may be previewed in a variety of formats in a single preview area and/or with individual font preview panes.

Abstract: Methods, systems and techniques for in-process font activation are described herein. According to various illustrative aspects, fonts for a job in process may be activated by a plug-in or other adaptive or extensible font module. The font module may be configured to conform to an application programming interface (API) of the document creation system in question (e.g., Adobe InDesign, Illustrator, InCopy; Quark XPress, CopyDesk, etc.). A job jacket is maintained that identifies a document for output along with all fonts necessary to create the desired output. During the print process, all identified fonts are activated in-process (i.e., during the print process). When a font is activated, either globally or in the local process space, the font module overwrites the previously activated font in memory in the local process space.

Abstract: An method for using a floating pallet for a digital asset management system in a plurality of different applications is disclosed. A single extension plug-in is created to interface with API's of all of the plurality of different applications, wherein the extension plug-in communicates with the digital asset management system. The floating pallet for said digital asset management system is created in one of the plurality of different applications wherein the floating pallet uses the properties and behaviors of a selected application. An indication that a file has been transferred from said digital asset management system to said selected application is then given.

Abstract: An apparatus for using a floating pallet for a digital asset management system in a plurality of different applications is disclosed. A single extension plug-in is created to interface with API's of all the plurality of different applications, wherein the extension plug-in communicates with the digital asset management system. The floating pallet for the digital asset management system is created in one of the plurality of different application wherein the floating pallet uses the properties and behaviors of a selected application. An indication that a file has been transferred from the digital asset management system to the selected application is then given.

Abstract: A method for examining font files for corruption involves an font manager communicating with a remote font server which stores uncorrupted font files. A portion of the font file to be checked for corruption may be compared with the uncorrupted font file to determine whether the file is corrupted. If the file is corrupted, an uncorrupted font file may be downloaded to the font manager to replace a portion of the corrupted font file containing the actual font file as opposed to a portion of the font file which may include other information such as kerning information.

Abstract: A preflight system has a printer profile database containing a list of problem document elements and a list of universal resource locator addresses. Each of the universal resource locator addresses is associated with at least one of the problem document elements. The preflight system also has an analyzer that compares document elements from a print file submitted by a print buyer with the problem document elements, in order to identify those document elements occurring in the print file that may cause a problem during printing. The analyzer then compiles a list of the universal resource locator addresses associated with problem document elements found in the print file.