I love tm_dialog, it looks so cool. I watched the screen cast and I have something configured (somewhere) wrong. In the screen cast the output is coming back in the form: {key = value; }
Which I believe is a plist
But when I run tm_dialog I am getting info back in this format: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>key</key> <string>value</string> </dict> </plist>
Which I guess is the xml representation of the same info. Is there something obvious I am doing wrong? I didn't see any flags on tm_dialog or in interface builder. I am a web developer so go easy on me :)
nds
On 1. Nov 2006, at 22:11, Nicholas Schlueter wrote:
I love tm_dialog, it looks so cool. I watched the screen cast and I have something configured (somewhere) wrong. In the screen cast the output is coming back in the form: {key = value; }
Which I believe is a plist
But when I run tm_dialog I am getting info back in this format: [...]
Which I guess is the xml representation of the same info. Is there something obvious I am doing wrong? [...]
No, the output just changed to the XML representation. If you would prefer to work with the old-style ASCII variant, add ‘|pl’ to your command line. pl will “pretty print” the XML representation into the corresponding ASCII variant -- the downside is that it doesn’t really support non-ASCII characters.
At a later time I may add an explicit “return readable UTF-8” option which makes it easier to work with the result w/o a plist parser.
-
Allan Odgaard -
Nicholas Schlueter