 |
Tmax Office: Connect the Office |
---|
 |
Worldwide Market For Office- [Graph] (Source: Gartner, May 2007)
|
---|
 |
Can You Open This [File]?[Diagram omitted] |
---|
 |
- 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
|
---|
 |
The Reality Of Document Compatibility- There exists open standard, but what about compatibility?
[Table omitted] |
---|
 |
Compatibility Of Tmax Office[Diagram omitted] |
---|
 |
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
|
---|
 |
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
|
---|
 |
- Replacement and addition of models and filter services
[Diagram omitted] |
---|
 |
Challenges Of Implementing Compatibility- There are cases that some document features are present in one format but not in another
|
---|
 |
- 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?
|
---|
 |
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
|
---|
 |
- Existence of undocumented features
- Tested every combination for this
- [Example:] GUID-based table style
|
---|
 |
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
|
---|
 |
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
|
---|
 |
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
|
---|
 |
Thank You! |
---|