Re:Microsoft office 365 v/s Open Source Fedena
by anonymfus on Sunday April 28, 2013 @07:45AM
(#5620906)
Looks like autoSpaceLikeWord95 is defined in ISO/IEC 29500-4:2012 "Information technology -- Document description and processing languages -- Office Open XML File Formats -- Part 4: Transitional Migration Features" as compatibility feature for unicode handling bug and ever has full name "Incorrectly Adjust Text Spacing for Specific Unicode Ranges".
Re:Microsoft office 365 v/s Open Source Fedena
by Someone on Sunday April 28, 2013 @01:27PM
(#5621984)
"because your clients are pointing to documents your program has created and saying that right here, there, and here too, the Word95-like autospacing is missing."
Firstly, I think it is way more likely they will point to documents they created earlier or that they received over the mail that your word processor does not show correctly (page breaks will change, which means textual references such as 'line 2 of page 3' will break).
Secondly, I doubt they will phrase it as "look, Word95-like autospacing is missing" it's more likely that they will say "MS Word is way better than your #%$! product".
You and I know this is part of some compatibility section of the spec, but if a customer has thousands of documents somewhat depending on those features, you must support it.
In summary: it may not be a matter of wanting to support that feature, but of having to support it.
Well, presumably, if you want to give your word processor the ability to "autoSpaceLikeWord95"--for a business use-case, not just as a feature to tick off on a checklist--then you already know what it means to "autoSpaceLikeWord95", because your clients are pointing to documents your program has created and saying that right here, there, and here too, the Word95-like autospacing is missing.
Basically, these compat flags are suggestions to activate the compat functionality it turns out you needed to build anyway; if you're adding compat for some old version of some app because the hook is there, without any of your own clients needing to preserve the old behavior in their documents, you're Doing It Wrong. It would be like Firefox parsing <!--if IE7--> tags just because there's a standard for how IE should handle them.