Re:Microsoft office 365 v/s Open Source Fedena
by tzs on Sunday April 28, 2013 @08:30AM
(#5620998)
Those are a bit misunderstood. Here's the use case they were put in for:
1. You have an existing workflow built around, say, WordPerfect 6 documents. You've got custom software that understands that format (possibly from reverse engineering).
2. You wish to adopt OOXML as your standard document storage format. You are going to write custom software that converts from your existing format to OOXML.
3. There are things in your existing format that cannot be represented in OOXML, but that need to preserved when you convert a document to OOXML, because your custom software needs that. For instance, your software might need to know about truncateFontHeightsLikeWP6 because it needs to be able to calculate what page something appeared on when the document was printed from Word Perfect 6. (I'm just guessing that font height truncation could affect this).
All they are really doing in the OOXML spec with these settings is acknowledging that people are out there with the legacy preservation needs described above, and giving them a way to all be on the same page (no pun intended!) when it comes to how they can store this information.
1. You have an existing workflow built around, say, WordPerfect 6 documents. You've got custom software that understands that format (possibly from reverse engineering).
2. You wish to adopt OOXML as your standard document storage format. You are going to write custom software that converts from your existing format to OOXML.
3. There are things in your existing format that cannot be represented in OOXML, but that need to preserved when you convert a document to OOXML, because your custom software needs that. For instance, your software might need to know about truncateFontHeightsLikeWP6 because it needs to be able to calculate what page something appeared on when the document was printed from Word Perfect 6. (I'm just guessing that font height truncation could affect this).
All they are really doing in the OOXML spec with these settings is acknowledging that people are out there with the legacy preservation needs described above, and giving them a way to all be on the same page (no pun intended!) when it comes to how they can store this information.