begin quoting John H. Robinson, IV as of Fri, Jul 06, 2007 at 11:36:20AM -0700:
[snip]
> consumable.comment.en="Toner Black (4000 prints) - $80
> Toner Yellow (4000 prints) - $110
> Toner Magenta (4000 prints) - $110
> Toner Cyan (4000 prints) - $110
> Transfer Belt (35000 prints) - $47
> "
Also:
consumable.comment.en={
Toner Black (4000 prints) - $80
Toner Yellow (4000 prints) - $110
Toner Magenta (4000 prints) - $110
Toner Cyan (4000 prints) - $110
}
Or:
consumable.comment.en=<<ENDCOMMENT
Toner Black (4000 prints) - $80
Toner Yellow (4000 prints) - $110
Toner Magenta (4000 prints) - $110
Toner Cyan (4000 prints) - $110
ENDCOMMENT
[snip]
> Yup. As I suspected: XML config files are overgrown, overbloated, hard to
> read, and contain WAY too much redundant information.
Fan as I am of XML (!), I actually was making the argument *for*
using XML, not for configuration, but for marshalling object to a
serialzed format.
--
Ever notice how XML can require you to have a network connection?
Stewart Stremler
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
