in ePub format.
* Free and open source software under GPLv3
* Multi-platform: runs on Windows, FreeBSD, Linux and Mac
* Full Unicode support: everything you see in Sigil is in UTF-16
* Full EPUB spec support
* WYSIWYG editing
* Multiple Views: Book View, Code View and Split View
* Metadata editor with full support for all possible metadata entries
(more than 200) with full descriptions for each
* Table Of Contents editor
* Multi-level TOC support
* Book View fully supports the display of any XHTML document possible
under the OPS spec
* SVG support
* Basic XPGT support
* Advanced automatic conversion of all imported documents to Unicode
* Currently imports TXT, HTML and EPUB files; more will be added with time
* Embedded HTML Tidy; all imported documents are thoroughly cleaned;
changing views cleans the document so no matter how much you screw
up your code, it will fix it (usually)
* An actually usable user interface
WWW: http://code.google.com/p/sigil/
PR: ports/150348
Submitted by: Jonathan Chen <jonc@chen.org.nz>
<ChangeLog>
- Fixed a not critical but important VM bug: from time to time a race
condition may happen and a client may never get the reply from a given
request.
- Now we have a make install target as stated in the README.
- redis-cli no longer tries to understand if it's part of a pipe
so there is to use the -x option to read the last arg from stdin.
This prevents it from creating problem when running inside cron scripts.
- Fixed the init script provided in the tar.gz. It was totally broken.
- Fixed a bug related to connecting more than 10k clients to Redis.
</ChangeLog>
* in PostgreSQL 8.3.1 Release note
Make encode(bytea, 'escape') convert all high-bit-set byte values into \nnn octal escape sequences (Tom)
This is necessary to avoid encoding problems when the database encoding is multi-byte. This change could pose compatibility issues for applications that are expecting specific results from encode.
but pyPgSQL escape bytea encode as it's own implementments. PostgreSQL says that it may make failure(see PQescapeBytea documentation).
in PQescapeBytea function documentation:
"The only difference from PQescapeByteaConn is that PQescapeBytea does not take a PGconn parameter. Because of this, it cannot adjust its behavior depending on the connection properties (in particular, whether standard-conforming strings are enabled) and therefore it might give the wrong results. Also, it has no way to return an error message on failure."
Patch is included upstream already
PR: ports/122616
Submitted by: "Choe, Cheng-Dae" <whitekid@gmail.com>
