The following is the English translation of [Tmax Office presentation slides](http://tmaxwindow.co.kr/images/common/Tmax%20Office.pdf). My own addition is in the [bracket].
[![Slide 01](o/01.jpg)](#01) Tmax Office: Connect the Office ===============================
[![Slide 02](o/02.jpg)](#02) Worldwide Market For Office --------------------------- * [Graph] (Source: Gartner, May 2007) * MS Office (98.3%) * Others
[![Slide 03](o/03.jpg)](#03) Can You Open This [File]? ------------------------- *[Diagram omitted]*
[![Slide 04](o/04.jpg)](#04) Changes In Document Format -------------------------- * From proprietary format, to open standard * Document format history * 2005: ODF became OASIS standard * 2006: ODF became ISO[/IEC] 26300 standard * 2007: ODF became Korean standard *[As KS X ISO/IEC 26300]* * 2008: MS Office binary file format goes public * 2008: OOXML became ISO/IEC DIS 29500 standard
[![Slide 05](o/05.jpg)](#05) The Reality Of Document Compatibility ------------------------------------- * There exists open standard, but what about compatibility? *[Table omitted]*
[![Slide 06](o/06.jpg)](#06) Compatibility Of Tmax Office ---------------------------- *[Diagram omitted]*
[![Slide 07](o/07.jpg)](#07) Infrastructure Of Tmax Office ----------------------------- * [Documents:] OOXML document (MS Office 2007), MS Binary document (MS Office 97-2003), ODF document (OpenOffice[.org]) * [Filters:] OOXML import/export, MS Binary import/export, ODF import/export * Document model for word processor, spreadsheet and presentation * [Monitor and keyboard, meaning rendering engine and user interaction] * [Supports:] i18n, drawing layer, GUI, framework, utilities, UNO, GSL, UCB, config[uration] m[an]g[e]r
[![Slide 08](o/08.jpg)](#08) Implementing Compatibility -------------------------- * OpenOffice document model is specialized at ODF, so cannot made fully compatible to OOXML and MS Office 97-2003 file format * Amount of document specification: OOXML at 5500 pages, MS binary at 5000 pages, ODF at 700 pages
[![Slide 09](o/09.jpg)](#09) * Replacement and addition of models and filter services *[Diagram omitted]*
[![Slide 10](o/10.jpg)](#10) Challenges Of Implementing Compatibility ---------------------------------------- * There are cases that some document features are present in one format but not in another
[![Slide 11](o/11.jpg)](#11) * There are cases that some document features are present but has differences in detail * Can adjust the individual shape [of combined shape]? * Can apply the style to individual lines? * Can adjust the text to fit in the shape automatically?
[![Slide 12](o/12.jpg)](#12) Implementing Document Filter ---------------------------- * Document input and output based on the intention of user * Handles missing features between document formats * Handles slight differences between document formats
[![Slide 13](o/13.jpg)](#13) * Existence of undocumented features * Tested every combination for this * [Example:] GUID-based table style
[![Slide 14](o/14.jpg)](#14) Compatibility Of User Experience -------------------------------- * Friendly UI * Minimizing feeling of foreignness and learning curve * Compatibility of features * Aiming at one-to-one correspondence of features * Performance improvement * Structure appropriate for multi-core processors * Improvements on huge documents * Improvements on multiple documents
[![Slide 15](o/15.jpg)](#15) Extensibility Of Tmax Office ---------------------------- * Platform via Tmax Office API * APIs for ODF support * Filter APIs for OOXML and MS binary model * Unique APIs for Tmax Office * Connection to TmaxSoft's enterprise products * ProCMS * ProPortal
[![Slide 16](o/16.jpg)](#16) Tmax Office ----------- * File compatibility, compatibility of user experiences, technical support * Dissolution of office [suite] monopoly via file compatibility * Conforms to document format standards * No OS dependency due to office suites
[![Slide 17](o/17.jpg)](#17) Thank You! ----------
[Back to the article](index).