Updates:
Summary: libdoc.py doesn't unescape `\n` and `\t` in resource files'
top-level documentation
Status: Done
Owner: pekka.klarck
Comment #2 on issue 320 by pekka.klarck: libdoc.py doesn't unescape `\n`
and `\t` in resource files' top-level documentation
http://code.google.com/p/robotframework/issues/detail?id=320
The problem was that the documentation wasn't unescaped and thus `\n` and
`\t` were
left into their literal format. Because table rows are separated by
newlines, and the
resulting doc didn't have newlines at all (only literal `\n`), formatting
tables
failed too.
This was fixed in r2063. The fix is included also in the development
version of
libdoc.py found from
http://code.google.com/p/robotframework/wiki/LibraryDocumentationTool
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
