* not interoperating with documents produced with Microsoft applications
* mis-rendering the text in question
* adding full support for the Microsoft code pages, in effect making Microsoft'’s implementation a ''de facto'' standard.
These code pages arewere oftensometimes viewed as part of Microsoft’s [[embrace, extend and extinguish]] strategy towards open standards.
On the other hand, ISOwhen insistingstandards inbodies decided to not assigningassign characters to positionthe control code positions 80-–9F, a precious 12.5% of the available space appeared to be wasted. This, didn'tperhaps, was not in users’ best interests, either.
Fortunately, the ongoing transition to full [[Unicode]] support now offers standards-based applications the possibility of full interoperability with the [[character repertoire]] of these documents without giving up standards compliance on output.▼
fit user's requirements either.
▲Fortunately, the transition to full [[Unicode]] support now offers standards-based applications the possibility of full interoperability with the [[character repertoire]] of these documents without giving up standards compliance on output.