aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJorge Arellano Cid <jcid@dillo.org>2015-05-26 11:29:21 -0300
committerJorge Arellano Cid <jcid@dillo.org>2015-05-26 11:29:21 -0300
commitc7aefa2cd7ef9bae68773df9f338da4b44a76d73 (patch)
tree460cd0d429069705e07af8c3b403ede439e669e2 /doc
parent02a3ee925afe16af350979f679df869164dd39c2 (diff)
Fix view-source dpi to handle null characters correctly
Although not allowed in text contexts, null characters should not stop/halt/fail dpi protocol, thus the patch. Test Example. Display a file with these contents: null padding^@^@ (two trailing null characters) and view source for it. Note that dillo will not _display_ the file completely correct, it will eat a char after each null, but this is not a problem in dpi nor dpip but in rendering, the cache gets it right. Adding code to correctly _display_ these anomalous pages is probably not worth the effort though.
Diffstat (limited to 'doc')
-rw-r--r--doc/Dpid.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/Dpid.txt b/doc/Dpid.txt
index 82b81311..6c418f57 100644
--- a/doc/Dpid.txt
+++ b/doc/Dpid.txt
@@ -285,9 +285,10 @@ commented code in hello.c and start making changes!
Debugging a dpi
---------------
- The simplest way is to add printf() feedback using the MSG*
+ The simplest way is to add printf-like feedback using the MSG*
macros. You can start the dpid by hand on a terminal to force
-messages to go there.
+messages to go there. Filter dpis use sdterr and server dpis
+stdout.
Sometimes more complex dpis need more than MSG*. In this case
you can use gdb like this.