summaryrefslogtreecommitdiff
path: root/lzo/doc/LZO.FAQ
diff options
context:
space:
mode:
authorArne Schwabe <arne@rfc2549.org>2012-07-02 21:42:07 +0200
committerArne Schwabe <arne@rfc2549.org>2012-07-02 21:42:07 +0200
commit21c3e54010129b504891e1786bf425d89328c969 (patch)
tree2e3eba26f5f0fa454188e1b52c7cab3761c4f208 /lzo/doc/LZO.FAQ
parentd4a1b52faa85df4446560a48c6bcc57f016e0c3c (diff)
parentb42eacfa8da0a642d629714f188cc0fc4c7e601a (diff)
Merge
Diffstat (limited to 'lzo/doc/LZO.FAQ')
-rw-r--r--lzo/doc/LZO.FAQ10
1 files changed, 5 insertions, 5 deletions
diff --git a/lzo/doc/LZO.FAQ b/lzo/doc/LZO.FAQ
index 604c98fa..cb1f38aa 100644
--- a/lzo/doc/LZO.FAQ
+++ b/lzo/doc/LZO.FAQ
@@ -47,7 +47,7 @@ Because of historical reasons - I want to support unlimited
backward compatibility.
Don't get misled by the size of the library - using one algorithm
-increases the size of your application by only a few kB.
+increases the size of your application by only a few KiB.
If you just want to add a little bit of data compression to your
application you may be looking for miniLZO.
@@ -73,7 +73,7 @@ What's the difference between the decompressors per algorithm ?
Once again let's use LZO1X for explanation:
- lzo1x_decompress
- The `standard' decompressor. Pretty fast - use this whenever possible.
+ The 'standard' decompressor. Pretty fast - use this whenever possible.
This decompressor expects valid compressed data.
If the compressed data gets corrupted somehow (e.g. transmission
@@ -81,7 +81,7 @@ Once again let's use LZO1X for explanation:
your application because absolutely no additional checks are done.
- lzo1x_decompress_safe
- The `safe' decompressor. Somewhat slower.
+ The 'safe' decompressor. Somewhat slower.
This decompressor will catch all compressed data violations and
return an error code in this case - it will never crash.
@@ -111,7 +111,7 @@ Once again let's use LZO1X for explanation:
Notes:
------
- When using a safe decompressor you must pass the number of
- bytes available in `dst' via the parameter `dst_len'.
+ bytes available in 'dst' via the parameter 'dst_len'.
- If you want to be sure that your data is not corrupted you must
use a checksum - just using the safe decompressor is not enough,
@@ -153,7 +153,7 @@ So after verifying that everything works fine you can try if activating
the LZO_ALIGNED_OK_4 macro improves LZO1X and LZO1Y decompression
performance. Change the file config.h accordingly and recompile everything.
-On a i386 architecture you should evaluate the assembler versions.
+On an i386 architecture you should evaluate the assembler versions.
How can I reduce memory requirements when (de)compressing ?