OK I see. The carriage return is there, but your parser ignores it, right? CDATA does not change that. CDATA only makes < and & be parsed as regular characters.
It would be best if [CDATA] is used to render data that's returned from a "call". Thus, maintaining the format.
Please look into this..and perhaps, make it an enhancement.
I suppose you mean "output" within "call" element, right? I was rather referring you to "ls". But I see it does not cover all your needs.
Where do you miss carriage return? I do have them included in output. Regarding parsing. If you execute "ls" command in console, its output is server-specific.
All value>>-rwsr-xr-x 1 root root 35376 Feb 12 2003 /usr/bin/chage -rwsr-xr-x 1 root root 36216 Feb 12 2003 /usr/bin/gpasswd
Carriage return is missing from output value, what's the best way to parse the value of the "output" attribute ?
What command could list file details in the following manner ?
Machine Name | File Name (With Path) | Attributes: Owner | Attributes: Group | Attributes: Is SGID? | Attributes: Is SUID? | Attributes: Permissions - ASCII
machineo.com | _u | bin | bin | No | No | lrwxrwxrwx