The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Usually, you would encode CR and LF as the XML entities and respectively. However, roslaunch trims whitespace (including CR/LF) from the beginning and the end of a parameter string value (which is unfortunate and possibly a bug), and seems to convert CR/LF and CR to LF even when encoded properly (which would be a bug in the XML parser).
| | 2 | No.2 Revision |
Usually, you would encode CR and LF as the XML entities and respectively. However, roslaunch trims whitespace (including CR/LF) from the beginning and the end of a parameter string value (which is unfortunate and possibly a bug), and seems to convert CR/LF and CR to LF even when encoded properly (which would be a bug in the XML parser).
| | 3 | No.3 Revision |
Usually, you would encode CR and LF as the XML entities and respectively. However, roslaunch trims whitespace (including CR/LF) from the beginning and the end of a parameter string value (which is unfortunate and possibly a bug), and seems to convert apply the XML end-of-line handling (convert CR/LF and CR to LF LF) even when to these encoded properly entities (which would be a bug in the XML parser).
| | 4 | No.4 Revision |
Usually, you would encode CR and LF as the XML entities and respectively. However, roslaunch trims whitespace (including CR/LF) from the beginning and the end of a parameter string value (which is unfortunate and possibly a bug), and seems to apply the XML end-of-line handling (convert CR/LF CR+LF and CR to LF) even to these encoded entities (which would be a bug in the XML parser).
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
