Browse Prior Art Database

A Method for Scaling Down File Formats and Merging to the Master Version Disclosure Number: IPCOM000204369D
Publication Date: 2011-Feb-22
Document File: 2 page(s) / 142K

Publishing Venue

The Prior Art Database


A method to scale down file formats for manipulation on resource-constrained devices in such a way as to allow merging back to the master version of the file. This is achieved through a specialised API which records the actions taken against the scaled-down file. On file synchronisation with the master version of the file, the actions are replayed against the file format's API. This means that the high resolution content is preserved while allowing new content to be added.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 54% of the total text.

Page 01 of 2

A Method for Scaling Down File Formats and Merging to the Master Version

Disclosed is a method whereby file formats can be scaled down for manipulation on resource-constrained devices and yet still be merged back to the master full-scale version of the file.

    When authoring content on a computer, such as a presentation or even a video or graphics project, it can become very difficult to make the file portable. For example, a business user is working on a presentation for a client and wants to include video clips in it. He then decides that he would like to take a copy of this presentation with him on his smartphone or netbook, but the hardware of the device is not sufficient to process the large presentation file and associated embedded videos and images.

    Existing solutions to this problem is to transcode the file and down scale it to the lowest command file format. For example, using Active Sync to convert Microsoft Word documents and spreadsheets. Specific styling or embedded content of those files are removed to make them compatible with the lower powered device.

    This invention works by providing an API method of reading and writing the file contents that each interaction with the file can be recorded. When the file is synchronised back to the master file, only the deltas require playing back against the master.

    For example, a user is working on a presentation that contains hi resolution images, specialised fonts, advanced slide transitions and embedded videos. The user wants to work on this presentation on their portable device (such as a smartphone), but it is unable to cope with the large overhead of processing this file.

    The user can export a version of the file targeted for the smartphone device. The scaling mechanism can represent the large images with low resolution images (while retaining metadata such as position and dimensions that the smartphone can understand). The video can be converted to a low bit-rate, low resolution version, fonts can be substituted and advanced transitions can be metadata only, but not necessarily rendered on the smartphone.

    When the user modifies the file on their smartphone, they are only interacting with specific parts of the file through the specialised API. For example, they may make another slide with additional text. The API only records the playback actions of:

Make new slide and insert it into presentation

Insert a text area (optionally specify the font or use the default) Enter text into the text area
Position the text area

    When the file is synchronised back to the master v...