White-space present between an end-tag and a start-tag is by definition ignored by the interpreters, so having the whole of the XML data as one long string of text without any line-breaks is actually completely OK ! plist files also embeds binary data, but Apple encodes the data in BASE64 thus following the rules.Īs to the formatting problem: formatting - that's only to make it more human-readable. Now, in OOXML M$ bastardized this principle by allowing pure binary data in a proprietary format to be embedded in the format. You can actually print it out, send it by snail-mail, and then type it in on the receiving end. All of these formats are in clear-text and thus human-readable. You''ll always want to do something with this data on the receiving end. The purpose of XML, HTML and SGML is to function as meta-formats that describe the data. When you've got a proper reflow of the document, you might want to use some search & replace commands to compact the document to bring several lines together. You can always undo and return to the original, if an experiment doesn't give you a good result. You've got several options you can experiment with.
HOW TO RUN A MAC TEXT FILE IN BROWSER TRIAL
You can download a trial version from barebones.
The only program, I can think of, that might be able to handle M$ XML, is BBEdit. Most programs will expect the input to follow the standard & can't handle bastard versions. I'm guessing, that M$ has implemented some bastard version of XML in MSN. But they implemented a draft version of the XML standard and never updated it to the final version, thus leading to severe compatibility problems between the browsers, as everybody else implemented the final version of the XML standard. in IE6 M$ introduced support for IE6 to be able to handle raw XML files. M$ has a long history of embrace - extend - own in their relationship with the standards.
0 kommentar(er)
