DE102013007748A1 - Method for creating electronically portable documents for e-book-like browsing on market-standard browsers in application-optimized form for online, offline, and print applications - Google Patents

Abstract

The process creates a file from electronic documents of various formats, such as PDF, with a finished layout, which can be viewed or read with widely used common browsers (e.g. Internet Explorer, Firefox, Google Chrome), so that the usual page turning is modeled. The process provides documents that can achieve the perceived appearance and ease of use of high-quality print media. The area of application extends in particular to brochures, catalogs or magazines, which can be electronically transmitted quickly and personally via email (attachment). Anonymous or non-anonymous distribution via download is also possible. The documents can be opened ergonomically on a wide variety of widely used device types with different operating systems via browser and viewed with the device's ease of use. Suitable devices are PCs, notebooks, touch screen devices such as tablets or smartphones. No special viewer is required to use the documents. There is no hurdle to an additional installation.

Description

Current situation

High-quality brochures and documents are still largely sent as a printed edition. The need for the smallest and medium-sized editions of documents in electronic formats such as (individual) photo books and brochures, (association) magazines is still present or even growing. The basis for this are the already predominantly electronically created and present texts and photos - the latter from digital cameras and smartphones.

As a rule, software that is downloaded from the Internet and installed locally (typically on the PC) is offered for the creation of print products. The disadvantage here is the time and the circumstances during download and installation. The result is then especially for the print product and due to the specific format hardly suitable for an often desirable simultaneous distribution on the Internet or in the local network.

Online providers often use Flash as a technology for creating print products. On the one hand, this proves to be safety-critical and, on the other hand, there is currently no support for smartphones and tablets.

The creation of print products with pure HTML and scripting languages or programming languages is hardly used or only used for relatively simple functions due to the different source code interpretations by the different browser types and versions, especially with regard to more complex functionalities. In addition to much more demanding session management in web applications compared to FAT client applications, creating complex layout products in terms of generating different output formats and simultaneously ergonomic viewing is another challenge, especially in terms of high quality print formats. Print formats require significantly higher image quality compared to online formats (monitor resolution) and quickly lead to unacceptable download times (bandwidth) when viewed online.

Furthermore, the control over what the addressee sees on his monitor and receives as a printed copy ("What you see what you get," WYSIWYG) is insufficiently resolved. Providers of print products present their results in RGB format and do not offer a preview of high quality print products sent to the high-end printer in the (bulkier) CMYK format - RGB is not printable.

Both providers who provide their software online or offline for the production of print products, especially in offline mode and in the email delivery do not have adequate, universally applicable, portable document format to disseminate the results created without the explicit installation of not standard installed software.

The most common methods of disseminating the results are the transmission of specific formats, PDF downloads, online presentations or the sending of print products.

Especially with regard to specific e-book formats, the installation of less widely used viewers or even special devices is typically required - in the business and private application area. With PDF documents, the visual functions such. For example, browsing is resolved within e-books.

The dispatch of appealing descriptions of products requiring explanation in print format proves to be disadvantageous for small and medium-sized companies in international business with regard to costs and with regard to timely delivery. The desire for a document format that can be kept locally in your own network or on your own computer (the customer), online representations also not. Although common browsers allow offline storage of Web pages as files in a local directory structure or even as a bundled file (for example, Internet Explorer mht format), multimedia content such as pictures, videos, and Sounds without network connection often display errors, which, among other things on unresolved URI's z. As the Internet and a limited recursion depth of references to external files within the HTML page are due. Another disadvantage is the method of offline storage of the web page as a directory tree in that the transmission due to the number of documents and the structural structure to be maintained z. B. via e-mail consuming and only practical if it was previously converted as a container file (eg ZIP).

improvement

The inventive method described here is in the fields of electronic media; assign electronic documents and their formats, transformations and presentations.

overview

• – OffDoc (Offline-Document): einfach lokal speicherbares Offline-Format mit multimedialen Inhalten, das mit dem lokal vorhandenen Browser benutzerfreundlich betrachtet und durchblättert wird zur Nutzung im lokalen Netzwerk oder Speichermedien ohne Internetverbindung.
• – OnDoc (Online-Document): ressourcenschonenden, performantes Online-Format mit multimedialen Inhalten für das ansprechende ergonomische Blättern und Betrachten, vorzugsweise für die Nutzung im Internet (Webpräsentation).
• – PrintDoc (Print Document): qualitativ hochwertiges Printformat zur Online-Druckvorschau mit dem lokal vorhandenen Browser oder zur Druckaufbereitung für Druckmaschinen unter besonderer Berücksichtigung des WYSIWYG-Prinzips bei gleichzeitig performanter Ergonomie.

The method enables user-friendly online creation, modification and viewing of layouts, especially for e-book related documents. In various forms, the process generates and transforms online and offline formats for various applications using a single (intermediate) source into the following result documents:

• - OffDoc (offline document): simply locally storable offline format with multimedia content, which is user friendly with the local browser and browsed for use in the local network or storage media without an Internet connection.
• - OnDoc (online document): resource-saving, high-performance online format with multimedia content for appealing ergonomic browsing and viewing, preferably for use on the Internet (web presentation).
• - PrintDoc (Print Document): high-quality print format for online print preview with the locally available browser or for print preparation for printing presses with special consideration of the WYSIWYG principle combined with high-performance ergonomics.

The method optionally generates encrypted documents which are transmitted electronically, in particular for business applications (eg email, FTP, HTTP) and can be opened at the receiver via a browser that is available everywhere. The documents can also be opened in an online portal or downloaded from there and stored locally for further use. After local storage on the PC, smartphone or tablet of the addressee, the documents can be opened again at any time via the usual browser - even offline, without network connection. Due to the use of HTML in each of the popular browsers, an HTML format for the process output is technically preferred, but not limited to.

The layout comes in the form of an electronic book, magazine or booklet for relaxed reading or viewing, and comes close to the familiar feeling of leafing and turning pages. The method expands the design scope of the layout in such a way that the contents can be extended over an open double page (on the left the straight side and on the right the odd). The result is absolutely seamless and therefore even better than the classic model of print media in practice. This design option will be preferred for images and graphics. Both the online formats and the offline formats can be zoomed in real time. The resolution and the richness of detail of the respective document variant can be controlled in a user-friendly manner according to the method by the author.

• – Mausklick auf linken/rechten Dokument-Seiten-Rand führt zum Rückblättern/Vorwärtsblättern;
• – Mausklick auf einen (z. B. mit einem Pfeil graphisch markierten) aktiven (sensitiven) Bereich links und rechts vom Dokumentrand, führt zum Rück/Vorwärtsblättern;
• – die Pfeiltasten „links/rechts” blättern entsprechend;
• – bei berührungsempfindlichen Screens sind die sensitiven Bereiche entsprechend zu berühren;
• – bei Gestensteuerung ist die entsprechende Geste für links/rechts anzuwenden.

The user interface for reading and viewing offers the convenience of the browser and device used (eg PC, notebook, tablet, mobile phone). These include, without limitation, the following examples:

• - Mouse click on left / right document page border leads to backward / forward page;
• - mouse click on an active (sensitive) area to the left and to the right of the document border (eg marked with an arrow), leads to backward / forward scrolling;
• - the arrow keys "left / right" scroll accordingly;
• - for touch-sensitive screens, the sensitive areas should be touched accordingly;
• - for gesture control, the corresponding gesture is to be used for left / right.

solution components

The inventive method presented here consists of process drivers (PT), which are located on one or more servers according to the method (VServ). The actual goal of the process is to create different output formats (process results) according to the same layout of an original document.

Without limitation to this expression illustrated 1 the basic process steps, which are described in more detail in the following sections.

In the further description, it is assumed that the original objects such as images, texts, videos, and sounds have already been uploaded from the UPC to the VServ and stored in the VServ database DB usable for the actual process.

UPC

The terminal (UPC), which can be a PC, tablet, smartphone or the like, accesses the layouter (LO) with a commercially available browser via a transmission protocol.

Layouter (LO)

• – Das JQuery-Plugin ”Booklet” (hier PlugBooklet genannt) von http://builtbywill.com/code/booklet/ (MIT License) stellt ein E-Book ähnliches Layout in blätterbarer Form zur Verfügung.
• – Das JQuery-Plugin ”Kinetic” (hier PlugZoom genannt) von https://github.com/davetayls/jquery.kinetic (MIT License) realisiert das Rein- bzw. Rauszoomen in bzw. aus Dokumenten.

The LO is a user-driven PT with an application-specific intuitive user interface that is used in real-time as an online service for layout creation purposes. The layout container, which represents the skeleton of the layout (eg containing objects and their positions), builds on the current state of the art and uses existing Java-Script libraries (such as JQuery) under other booklets can represent. Without limiting the alternative methods, the following selection is used in the preferred embodiment:

• - The JQuery plugin "Booklet" (here called PlugBooklet) of http://builtbywill.com/code/booklet/ (with license) provides an ebook-like layout in a scrollable form.
• - The JQuery plugin "Kinetic" (here called PlugZoom) of https://github.com/davetayls/jquery.kinetic (with license) realizes the zoom in or out of documents.

Jquery and the two plug-ins are open source objects of the MIT. The latter grants a far-reaching and free usage permit under conditions that can be found at the time of writing this description under the following link: http://opensource.org/licenses/MIT

At the time of writing, the condition was:
Without any limitation the rights to use, copy, modify, to obtain any copy of the software and associated documentation files (the "Software"). merge, publish, distribute, sublicense, and / or sell copies of the Software, and to provide the Software to which
The above copyright notice and this notice should be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED AS AS, WITHOUT WARRANTY OF ANY CHILD, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERS LIABILITY, WHETHER IN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."

The libraries of the plugins are used and extended in a novel way, in that the user can design user-friendly dynamic and at runtime individual layouts. The layout container PlugBooklet serves only as scaffolding and is extended by the PT by means of web languages (eg PHP, JAVA-Script, HTML, CSS, but not limited to) to the following functions, the actual content:
PlugBooklet is populated with layout-related presentation instructions for objects such as formatted text, images, videos, and sound objects, and their attributes (such as position, layers, bleed, resolution). In doing so, the LO translates the user-appropriate actions taken during layout into this implementation assembly that enables PlugBooklet for the LO result document, WorkDoc. This application-remote technical detail is kept away from the user by the user interface of the LO.

• – Hinzufügen, modifizieren und entfernen von multimedialen Objekten wie Bildern, formatierte Texte, Videos und Sound-Objekte.
• – verschieben, vergrößern/verkleinern, drehen und beschneiden von multimedialen Objekten
• – Objekte in den Vordergrund oder Hintergrund platzieren.
• – Multimedia Objekte wie Sound oder Video werden mit Elementen zur Ablaufsteuerung (z. B. Start, Stop, Pause, Vorwärts, Rückwärts) versehen.

Within the framework of the LO, the user will be provided with the following application-related functions in an intuitive, comprehensible manner for layout design in real time via UPC and browser

• - Add, modify and remove multimedia objects such as images, formatted texts, videos and sound objects.
• - move, zoom in, rotate and crop multimedia objects
• - Place objects in the foreground or background.
• - Multimedia objects such as sound or video are provided with flow control elements (eg start, stop, pause, forward, backward).

Depending on the hardware configuration, the user interface of the respective UPC can be z. B. with mouse, touch, gestures are served.

Further options for the equipment of the LO are z. Page templates, usage permissions via encryption or password.

WorkingDoc (WorkDoc) and Database (DB)

The creation and (subsequent) modification of the WorkDoc takes place on the basis of pricing, scripting and programming languages as well as declarative languages, in particular CSS, whose instructions are the layout properties of the respective referenced database objects (DB) or server objects within the individually defined layout area without changing the original objects (eg individual images).

The WorkDoc consists of an HTML header that includes, among other things, the libraries required for the procedure, an HTML body and a layout container that contains one or more page containers. Each page container consists of one or more object containers that contain the multimedia content (eg, images, video, text). (please refer 2 )

The object container contains a single object such as image, text or video. Each object container, consisting of a set of statements (preferably HTML statements) and associated object properties (eg URI, layout information), defines an object within a page container (single page) that ultimately Container with other page containers (ie with other pages) is summarized.

The layout container is stored either completely or in a DB such that only the attribute values (such as layout information, object references - URI) of the layout, page and object container are persisted without the associated instructions. The following abstract example illustrates the basic principle of the two approaches without being set:

1) Full storage:

The following source code is completely stored in the DB.

2.) Partial storage:

In the case of partial storage, the values (in the example marked in bold) of the respective attributes are first identified using a search algorithm and stored in the DB in such a way that the values (eg 150 px) correspond to the attributes (eg width) and the associated instruction (eg img id) and the respective page in the layout container. When restoring / opening the statements and their attributes are enriched again with the corresponding values from the DB.

For assignment without the context of the source code, the values can be arranged in a syntactically determined order, and for space-saving optional placeholders, e.g. For example, semicolons can be used to separate different hierarchies and commas between the same multiple-occurrence objects. This would z. B. above Layout_Container 1 are partially stored as follows:
1; 1,425px; 1,150px, 1,150px, " http://www.obst.de/apfel.jpg "

The complete storage is relatively easy to implement, but has the disadvantage over partial storage that more storage capacity is needed.

The source code is stored in both ways in such a way that foreign code (eg malware) is filtered out beforehand by allowing only instructions and attributes needed for the creation of the respective document,

As a third alternative, such a layout container can also be saved as an XML file on VServ.

The above examples of expression are not exclusive.

Due to the different source code interpretations by the different browser types and versions, the WorkDoc is stored in such a way that in real time, depending on the browser type and version, the corresponding part of the source code is inserted and / or executed in the WorkDoc viewed online that the intended representation of the layout and the contents takes place.

• – SmallObj: Umwandlung des OriginalObj in ein hinsichtlich der Auflösung reduziertes Abbild
• – PrintObj: Umwandlung des OriginalObj in ein typischerweise hochauflösendes CMYK-Objekt. Hierbei liegt es in der Verantwortung des Users/Autors, dass die OriginalObj in einer Qualität vorliegen, die mindesten so hoch ist, wie die höchste Anforderung. Bei Bildern ist das typischerweise ein für den Druck vorgesehenes Objekt.

As another feature, LO provides a method that appropriately scales the quality of the application uploaded by the user and already stored in the DB (OriginalObj) during the layout process, and the related object-related instructions are additionally stored in the DB in such a way that the original obj remains unchanged (preferred procedure). When applied to images, the following results

• - SmallObj: Conversion of the original Obj into an image reduced in resolution
• - PrintObj: transformation of the original Obj into a typically high-resolution CMYK object. It is the responsibility of the user / author that the originalObj is at least as high as the highest requirement. For images, this is typically an object intended for printing.

The transformation of the originalObj is done server-side in a background process using ImageMagick ( http://www.imagemagick.org/script/index.php ) without restricting the process alternatives.

Note: ImageMagick is free software delivered as a ready-to-run binary distribution or source code that you may use, copy, modify, and distribute in both open and proprietary applications. It is distributed under the Apache 2.0 license approved by OSI and recommended for use by the OSSCC.

For images, the resolution quality requirement increases with the magnification of the image within the layout.

Document Transformer (DocTF)

The Document transformer (DocTF) is a transformer that runs on VServ and at the instigation of the user (via browser of his UPC) from a WorkDoc generates the respective output format (process result) in a background process and makes UPC available. The output documents are executable HTML files.

Offline Document (OffDoc)

The OffDoc is an output document of the DocTF. It can be stored locally in a UPC or comparable device and used for offline use in the wrap-around mode with the browser typically present on the UPC or a comparable device. Opening an external memory such as a USB stick is also possible. The UPC or similar device does not need to be connected to the VServ.

The (HTML) structure of the OffDoc corresponds to that of the 2 WorkDoc, however, the preferred form of the header of the OffDoc contains the PlugZoom. This causes the user to use, among other things, the mouse wheel to zoom.

• 1.) Das WorkDoc wird auf Veranlassung des user-seitigen Browser von der VServ-Anwendung aus der DB mit einer Datenbanksprache in einem Hintergrundprozess im VServ geladen.
• 2.) Ein Suchprogramm identifiziert innerhalb des WorkDoc alle Verweise auf externe Skript- und HTML-Dateien und ersetzt die Befehle durch die entsprechenden Inhalte. Dieses Vorgehensweise wird rekursiv durch das gesamte WorkDoc angewendet.
• 3.) Ein Suchprogramm identifiziert innerhalb des WorkDoc alle Verweise auf multimediale Inhalte wie Bilder, Videos und Sounds (bevorzugt OriginalObj) und codiert diese vorzugsweise in Base 64, ohne darauf beschränkt zu sein.
• 4.) Das so transformierte WorkDoc wird in VServ zwischengespeichert und kann über LO mit Hilfe des UPC-seitigen Browsers heruntergeladen und lokal auf dem UPC gespeichert oder per Email versendet werden. Das spätere Öffnen des dann lokal vorliegenden OffDoc benötigt keine Verbindung zu VServ und kann ohne sonstige (Internet-)Netzanbindung betrachtet werden.

Steps to OffDoc:

• 1.) At the behest of the user-side browser, the WorkDoc is loaded from the VServ application from the DB with a database language in a background process in VServ.
• 2.) Within the WorkDoc, a search program identifies all references to external script and HTML files and replaces the commands with the corresponding contents. This approach is used recursively throughout the WorkDoc.
• 3.) A search program identifies within the WorkDoc all references to multimedia content such as images, videos and sounds (preferably OriginalObj) and encodes them preferably in Base 64, without being limited thereto.
• 4.) The so transformed WorkDoc is cached in VServ and can be downloaded via LO using the UPC-side browser and stored locally on the UPC or sent by email. The subsequent opening of the locally available OffDoc does not require a connection to VServ and can be viewed without any other (Internet) network connection.

The result OffDoc can be stored permanently in the DB of the VServ or with only occasional request, the DB memory can be saved and the OffDoc each time anew (because performance-optimized) are created. Preferably, the WorkDoc is retained in the DB in order to generate one of the other result documents if required.

In an alternative embodiment, the coding in step 2 is already carried out in the preceding step 2, i. H. as soon as the multimedia contents are in the process of processing.

Online document (OnDoc)

The online document OnDoc is to be used for online use on VServ in flip-wrap mode with the browser typically found on the UPC. The UPC needs a (real-time) connection to the VServ.

• 1.) Das WorkDoc wird auf Veranlassung des Users aus der DB mit einer Datenbanksprache in einem Hintergrundprozess im VServ geladen.
• 2.) Ein Suchprogramm identifiziert innerhalb des WorkDoc alle Verweise auf multimediale Inhalte wie Bilder, Videos und Sounds und ersetzt diese durch Verweise, die auf ein reduziertes Abbild in der Auflösung eines jeden Objektes referenzieren (SmallObj), um das Online-Arbeiten während der Layout-Session auch bei der typischerweise begrenzten Bandbreite der Verbindung zwischen VServ und UPC flüssiger zu erledigen.
• 3.) Das transformierte WorkDoc wird nach oder während der Bearbeitung auf VServ gespeichert und kann über UPC performant als Ganzes oder auch seitenweise in den Browser-Bereich des UPC geladen werden. Bevorzugt bleibt das WorkDoc in der DB erhalten, um daraus bei Bedarf eines der anderen Ergebnis-Dokumente zu generieren.

Procedural steps for OnDoc:

• 1.) The WorkDoc is loaded at the instigation of the user from the DB with a database language in a background process in VServ.
• 2.) A search program identifies within the WorkDoc all references to multimedia content such as images, videos and sounds and replaces them with references that refer to a reduced image in the resolution of each object (SmallObj) to the online working during the layout -Session even with the typically limited bandwidth of the connection between VServ and UPC liquid to do.
• 3.) The transformed WorkDoc is saved to VServ after or during editing and can be loaded via UPC performant as a whole or also page by page into the browser area of the UPC. Preferably, the WorkDoc is retained in the DB in order to generate one of the other result documents if required.

Print document (PrintDoc)

The print document (PrintDoc) is created on VServ and is to be used for online use in flip-wrap mode with the browser typically found on the UPC, but serves primarily as a basis for generating high-quality print formats such as PDF. The UPC needs a (real-time) connection to the VServ. Although videos and sounds can be displayed in principle, they are not intended for the printing process and are therefore not integrated into the PrintDoc, which is intended as a preliminary stage to the print product (hard copy).

• 1.) Das WorkDoc wird auf Veranlassung des Users aus der DB mit einer Datenbanksprache in einem Hintergrundprozess im VServ geladen.
• 2.) Ein Suchprogramm identifiziert innerhalb des WorkDoc alle Verweise auf Bilder und ersetzt diese durch Verweise, die auf die OriginalObj die den Qualitätsansprüchen hochaufgelöster CMYK-Bilder (PrintObj) entsprechen sollen (Verantwortung des Users/Autors), um dem User mit UPC eine Vorschau des drucknahen Ergebnises zu bieten – ”WYSIWYG”.
• 3.) Das transformierte WorkDoc wird nach oder während der Bearbeitung auf der VServ-DB gespeichert und kann ausschnittsweise oder seitenweise ohne übermäßige Belastung der Übertragungsmedien oder der erwarteten ergonomischen Download-Zeit zum UPC-Browser geladen werden.

Steps to PrintDoc:

• 1.) The WorkDoc is loaded at the instigation of the user from the DB with a database language in a background process in VServ.
• 2.) A search program identifies all references to images within the WorkDoc and replaces these with references to the original objects that meet the quality requirements of high-resolution CMYK images (PrintObj). should correspond (responsibility of the user / author) to provide the user with UPC a preview of the pressure-related result - "WYSIWYG".
• 3.) The transformed WorkDoc is stored on the VServ DB after or during processing, and can be loaded to the UPC Browser, in sections or pages, without undue burden on the transmission media or the expected ergonomic download time.

The peculiarity of all online and offline formats is that no special viewer and no special hardware is needed as UPC - consumer standard is sufficient. In order to ensure a high-performance use, the contents are loaded page by page on large OnDoc and PrintDoc pages.

Output Formatter (OutFormatter)

For all of the above output formats, the output size of the target document can be variably determined; H. that both the layout framework and all contained objects can be proportionally scaled. This is particularly applicable to the production of high quality print documents in combination with PrintDoc and to optimize the display on different monitor devices. The procedure described here is not absolutely necessary, but rather intended as an optional extension and can optionally be installed after loading the WorkDoc.

PDF Generator (PDFGen)

The PDFGen creates PDF documents (PDFDoc) based on the PrintDoc, in combination with the OutFormatter, in any scaled formats that are primarily intended for professional printing or print previews. It should be noted that printed products such as brochures, books or magazines require a divisible total of 4 pages.

Procedural steps for PDFGen

• 1.) PageChecker checks if the total page number of the PrintDoc is divisible by 4. Assuming that this is the case, follow step 2
• 2.) Preferably the PrintDoc transformed with the optional extension OutFormatter is loaded in a background process in an X-Window (or in a virtual desktop). With a link to CutyCapt, which points to a single page container of the PrintDoc, a (virtual) screenshot is created on the server side in print-optimized quality, preferably in jpeg.
• 3.) The image created under process step 2 is integrated into a PDF on the server side.
• 4.) The process steps 2-3 are run in a loop until all pages are integrated into the PDF.

Process steps 2-3 are based on the current state of the art and preferably use the functions of CutyCapt ( http://cutycapt.sourceforge.net/ ), without restricting the process alternatives, so that the order of the signatures can be binding.

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited non-patent literature

• http://builtbywill.com/code/booklet/ (WITH License) [0019]
• https://github.com/davetayls/jquery.kinetic (MIT License) [0019]
• http://opensource.org/licenses/MIT [0020]
• http://www.obst.de/apfel.jpg [0032]
• http://www.imagemagick.org/script/index.php [0039]
• http://cutycapt.sourceforge.net/ [0055]

Claims (5)

Method on a configuration consisting of a server VServ and a user terminal UPC, such that VServ is equipped with a database DB, in which at least one layout is finished HTML document WorkDoc, such that it consists of an HTML header with procedural libraries and an HTML body with a layout container containing a plug-in PlugBooklet, such that one page container per page is embedded in the structure of the PlugBooklet so that a page container contains object containers containing the multimedia objects such that, besides the texts, the objects are included via URI with reference to the resources external to the WorkDoc, and the object container to its object to which it refers, formatting, style, and positioning relative to those given in the page container Contains positions, limits, and stores so that the WorkDoc is viewable and readable in a scrollable online mode, and VSer v contains a working Document Transformer DocTF, and that the UPC is equipped with a browser that processes market standard HTML, and the configuration contains a connection such that it is constructed or degraded between UPC and VServ at the initiative of the user according to the method characterized in that the DocTF created an offline document OffDoc at the instigation of the user who has control influence on the DocTF via the UPC and the browser located thereon, so that the OffDoc can be downloaded to the UPC after its creation and locally on the UPC as a single file is storable, so that the OffDoc after saving is also open without a connection between UPC and VServ with the browser and in browsable manner is viewable and readable, and / or that the OffDoc by memory stick, or by data carrier, or via email attachment even without auxiliary container and without a zip container, as a simple document to other term inals is transferable and storable and can be used there with the HTML-compatible market-standard browser in the same way without further external connection and also without connection to the UPC originally used to create the OffDoc and without connection to VServ, in that DocTF to create the OffDoc in one Background process proceeds as follows: a. DocTF accesses the WorkDoc in the DB and loads a copy into a background process so that the so-loaded copy of the WorkDoc is used as the source for the new OffDoc to be created, and b. A search process identifies all references to external script and HTML files and gradually replaces the instructions directly with the corresponding content until the newly created OffDoc no longer references any script and HTML files outside the newly created OffDoc , and c. another search program identified within the now reached state of OffDoc all multimedia objects and encodes them, with the exception of text, in the preferred expression in Base64 such that the encoded result is substituted for the previous reference and can be displayed by a standard browser . and after step c. the finished OffDoc is either stored in the DB, so that it is used for one or more downloads or by email to one or more UPC for use, or is provided without storage directly to the UPC. A method according to claim 1, characterized in that at the instigation of the user via the browser on the UPC from the WorkDoc in a background process using the DocTF a document OnDoc is created by transformation and stored in the DB, such that the finished OnDoc from the UPC with the help of an existing connection between UPC and VServ as an online document with the UPC browser is retrievable and readable in a flip mode, thereby achieving that the DocTF at the instigation of the user, the content is not inserted directly into the resulting OnDoc but as a new URI with reference to such modified new copies of the content are replaced, that this new content is converted in the background process for display on a monitor in reduced or optimized resolution and stored in the DB and the new URI are directed to, and such that upon retrieval of the finished OnDoc at the instigation of the user, for Open with the UPC's browser, the HTML statements that make up the finished OnDoc and stored in the DB, in real time via the connection between the UPC and the VServ in sections or in full, such that the URI with external references, which are found by the browser, are resolved via the connection to the VServ, so that the contents are addressed to VServ and sent in real time over the connection to the browser for presentation. A method according to claim 2, characterized in that at the initiative of the user in a background process using a PDF creating process PDFGen, a document PDFDoc is created, such that from an input document in one of the formats OnDoc or OffDoc or WorkDoc by PDFGen successively the Links to the page containers of the input document is passed to a utility tool CutyCapt, so that the CutyCapt is selected to create screenshots from the pages defined in the page containers in HTML, so that CutyCapt from PDFGen in one X-Window process or is started in a virtual desktop process, so that CutyCapt created by an automated and parameterized command line call the PDFGen from each page a virtual screenshot, preferably in the format JPEG, so that PDFGen takes the screenshot and converts it into a PDF, so that each page is progressively integrated into the PDFDoc. A method according to claim 3, characterized in that the step of creating the PDFDoc at the end of the method described in claim 3 is not performed, such that the intermediate product is preferably used from JPEG screenshots of the pages, so that it with the finished pages represent the final layout and used as a resource-saving preview version of a document such that the preview document is interpretable and viewable by common browsers such as an OnDoc or OffDoc, and an assessment of the continuation of the process then allows for a more material-intensive printing process empties. A method according to claim 4, characterized in that the PDFDoc is created specifically for the transfer to a printer, such that a high-quality print with high resolution is possible, achieved by successively in the input document PrintDoc all images in the object containers those that meet the required resolution or are replaced by those that are created using an ImageMagick utility tool to the specific requirement, such that one copy at a time of each image preferably in GIF or JPEG format highest resolution is taken from DB as OriginalObj and optimized to ImageMagick for scaling to the required resolution and / or preferably transferred to the color space transformation in CMYK format and then the respective transformation result in the object container of the PrintDoc is used or in the DB is stored, so that in the latter In the case where the link in the affected object container is directed to the newly created object in the DB.

Images