3 ms·

and ooxml is basically just a serialization of microsoft office internals, with attributes such as "likeword95" on certain elements.. microsoft made a total pi

and ooxml is basically just a serialization of microsoft office internals, with attributes such as "likeword95" on certain elements.. microsoft made a total piece of steaming turd, and its users dont care.

RachelF 1y ago
Yes, it's bad, but the users _do_ care. Most don't have a choice, business machines have MS Office/Outlook/Teams as default and they can't change.
- redeeman 1y ago
  they dont care enough. I have said no to work that would require me to work with loads of MS shit, I have said no to open photoshop files, various other proprietary crap files. They might care, but they just only care a tiny tiny tiny tiny bit, and certainly not enough to inconvenience themselves in any way for it.
tzs 1y ago
I think you are mixing up some things. There are no "likeword95" attributes. At one point during standardization there was a proposal to add several attributes with names like that although most of them referred to non-Microsoft products like WordPerfect, but it didn't make it into the final standard. That's what you are probably thinking of. Their purpose was to allow someone writing say a WordPerfect to OOXML converter to mark in the OOXML places that were using some specific WordPerfect formatting that couldn't be replicated in OOXML. OOXML word processors were supposed to preserve those markings if they encountered them but never add them.
- ndsipa_pomu 1y ago
  There was/is a <autoSpaceLikeWord95> https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.autospacelikeword95?view=openxml-3.0.1 https://learn.microsoft.com/en-us/dotnet/api/documentformat....
  - tzs 1y ago
    Huh. Looks like some of them came back. Here’s one of the WordPerfect ones. https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.wordperfectjustification?view=openxml-3.0.1 https://learn.microsoft.com/en-us/dotnet/api/documentformat.... I wonder if there is a complete list readily available?

RachelF 1y ago

Yes, it's bad, but the users _do_ care. Most don't have a choice, business machines have MS Office/Outlook/Teams as default and they can't change.

redeeman 1y ago
they dont care enough. I have said no to work that would require me to work with loads of MS shit, I have said no to open photoshop files, various other proprietary crap files. They might care, but they just only care a tiny tiny tiny tiny bit, and certainly not enough to inconvenience themselves in any way for it.

tzs 1y ago

I think you are mixing up some things. There are no "likeword95" attributes. At one point during standardization there was a proposal to add several attributes with names like that although most of them referred to non-Microsoft products like WordPerfect, but it didn't make it into the final standard. That's what you are probably thinking of. Their purpose was to allow someone writing say a WordPerfect to OOXML converter to mark in the OOXML places that were using some specific WordPerfect formatting that couldn't be replicated in OOXML. OOXML word processors were supposed to preserve those markings if they encountered them but never add them.

ndsipa_pomu 1y ago
There was/is a <autoSpaceLikeWord95> https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.autospacelikeword95?view=openxml-3.0.1 https://learn.microsoft.com/en-us/dotnet/api/documentformat....
- tzs 1y ago
  Huh. Looks like some of them came back. Here’s one of the WordPerfect ones. https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.wordperfectjustification?view=openxml-3.0.1 https://learn.microsoft.com/en-us/dotnet/api/documentformat.... I wonder if there is a complete list readily available?