Sigil v0.1.2 has been released. The ChangeLog (live version
here) for this release follows:
Quote:
Sigil v0.1.2 2009.08.12.
- added the ability to specify the main publication identifier directly,
through the "CustomID" basic metadata property (issue #3)
- fixed a bug with warning dialog not informing the user of unsaved changes
when editing in code view (issue #30)
- Sigil is now a universal Mac application (ppc and i386, in 32bit) (issue #5)
- implemented a workaround for a bug in QTextCodec causing bad HTML codec detection (issue #74)
- SVG elements are not removed anymore (issue #24)
- inter-document HTML links are now fully supported (issue #53)
- fixed rare issue where CSS style rules could get duplicated when changing views
- fixed issue with inline style tags in OPS documents not being loaded (issue #58)
- Sigil can now accept a file to load as the first command line argument; this also
provides support for "Open With..." operating system features (issue #63)
- fixed an issue where the reported build time in the About dialog was actually the execution
time (issue #65)
- loading of missing files in the recent files list is now improved (issue #57)
- fixed a rare issue where the wrong view could be sent to the printer on print actions
- Sigil now creates a guide element with a cover page in the OPF if the content of the first
OPS document is less than 1000 characters long (issue #48)
- support for importing UTF-16 encoded documents (not just UTF-8)
- provided install target for linux; the binary is now also named "sigil"
(lower case 's') on Unix systems (except Mac) for the sake of convention (issue #46)
- removed dependency on "data" directory (issue #51)
|
There is no binary build for the Linux version, and this is final. The build system is now trivial to use, and it has a shiny new "install" target (for Linux).
The next release should come with an installer for the Windows platform. Mac users already have a prepackaged DMG, and from what Mac users tell me (and the Apple developer website), this is the preferred way of deploying applications for that platform.
I will not be providing DEB and RPM (and whatever else package type) packages for Linux systems simply because there are too many. 32bit & 64bit DEB's and 32bit & 64bit RPM's alone make up four, and this is simply too much work for what Google Analytics and the download counts specify as
10-15% ~9% of the Sigil user base. Providing just some package types and not others would be unfair. And when/if package repository maintainers of the various distros decide to include Sigil, they will be making their own packaged versions either way. So there's really little point.
Sorry guys. But as I've said, building Sigil is trivial, and now you have an install target too. From what I can tell from other native-code, multi-platform OSS projects, an installer for Windows, a DMG for Macs and a source package for Linux people is a common way of doing things. And their build procedures are a
lot more involved.
Now let's get back to "Yaaay, Sigil is 0.1.2! Why haven't you done the search dialogs and view syncing yet? You
sooo suck."
