Unclear on the concept
My prospective TAG client is having word-processing issues.
No, no, I don’t know what word-processor she uses, or even whether she uses one. But she’s clearly got a word-processing mental model of XML, and it’s starting to be a problem.
First she wanted to know what font I was going to use to enter her Greek. Um, I’m going to give her XML with Unicode. As long as she has a Unicode font and I have a Unicode font, it doesn’t even remotely matter if my font isn’t the same as hers; if I’ve entered an alpha, she’s going to see an alpha.
Now she wants to know what XML editor and validator I use. I told her outright that I use a text editor and shell out to nsgmls. But, look, it DOESN’T MATTER. XML is XML.
These things matter in word processors. You don’t have the right font? Watch your document implode. You don’t have the right word processor? Forget about even opening the document.
But XML isn’t a word-processing format. (Word-processing formats are being written in XML, mind you. But that’s not the same thing.) XML qua XML doesn’t give a damn what you edit it in.
Part of this is my fault. I’m familiar (from unfortunate experience) with “XML” that has Sooper Seekrit Bits inserted by the editing software. Mess with the Sooper Seekrit Bits (say, because you use a different XML editor), and bad things happen when the original user tries to use the file. I mentioned this as a possibility because I like to cover all possibilities (even remote ones). I am now kicking myself for getting embroiled in irrelevancies.
Oh, well. Guess that’s why they pay me the big bucks. (*snerk*)