#13493 closed enhancement (fixed)
mutt-1.14.0
Reported by: | Bruce Dubbs | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 10.0 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
New minor version.
Change History (7)
comment:1 by , 4 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 4 years ago
comment:3 by , 4 years ago
The good news is that the shipped manual.txt no-longer gets wiped out.
The bad news is that producing a PDF manual is broken.
if test -n "/usr/share/sgml/docbook/dsssl-stylesheets-1.79"; then \ openjade -t tex -D /usr/share/sgml/docbook/dsssl-stylesheets-1.79 -d print/docbook.dsl dtds/decls/xml.dcl manual.xml; \ fi openjade:E: cannot find "manual.xml"; tried "manual.xml", "/usr/share/sgml/docbook/dsssl-stylesheets-1.79/manual.xml", "/usr/share/sgml/manual.xml" openjade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/dtds/decls/xml.dcl:179:2:E: end of document in prolog make: [Makefile:640: manual.tex] Error 1 (ignored)
It then continues, but the resulting PDF is empty.
In the doc Makefile is the following:
# Note / Request For Help: # On Debian, the below invocation of openjade is not working for me. # I was able to generate manual.tex by instead running: # openjade -t tex -D $(DSLROOT) -d print/docbook.dsl \ # -i xml /usr/share/xml/declaration/xml.dcl manual.xml # However, being completely unfamiliar with these tools, am unsure how to # make this portable. manual.tex: stamp-doc-xml -if test -n "$(DSLROOT)"; then \ openjade -t tex -D $(DSLROOT) -d print/docbook.dsl dtds/decls/xml.dcl manual.xml; \ fi
Note that we do not have /usr/share/xml/declaration/xml.dcl. We do have /usr/share/sgml/docbook/dsssl-stylesheets-1.79/dtds/decls/xml.dcl (docbook-dsssl), /usr/share/sgml/OpenSP-1.5.2/xml.dcl (OpenSP) (OpenSP), /usr/share/sgml/xml.dcl (sgml-common).
I tried each in turn in that modified command, but none of them produce manual.xml.
I checked Arch and Opensuse, neither create the PDF docs - everyone else seems to be on old versions.
Will comment the code and the deps, and in future go with the text (needs 'less', not 'view' and the html.
comment:4 by , 4 years ago
Further note: the creation of manual.tex in mutt-1.13.5 uses the same command, and creation of manual.pdf in 1.13.5 still works with current texlive. Not sure where the breakage has occurred.
Details of changes are in the UPDATING file -
+ $imap_deflate enables support for COMPRESS=DEFLATE compression. Defaults unset, but please give it a try and report any issues.
! Date pattern modifiers accept YYYYMMDD format dates.
+ $crypt_opportunistic_encrypt_strong_keys modifies $crypt_opportunistic_encrypt to only look at strong (fully-valid) keys. ! Pattern modifiers ~b, ~B, and ~h are allowed in send2-hook patterns.
+ New compose menu functions <move-up> and <move-down> to rearrange the order parts.
+ Background editing support. Compose and browse your mailbox at the same time, or have multiple compose sessions ongoing! New config vars $background_edit, $background_confirm_quit, and $background_format. New function <background-compose-menu> in the index and pager menu. New %B expando added to the default for $status_format. Please see the manual and release notes for details.
+ $fcc_delimiter, when set, allows Fcc'ing to multiple mailboxes via $record or fcc-hook.
+ Index and pager menu functions <sidebar-first> and <sidebar-last>.
! "mailboxes -label" allows displaying a label in the sidebar or mailbox browser instead of the mailbox path. "-nolabel" removes an existing label.
! "mailboxes -nopoll" turn off new mail polling for the mailbox. "-poll" restores polling for an existing mailbox.
! "root" disposition added to the "attachments" command. Please see the manual for the details of how it works.
! Decryption failures will no longer abort the displaying the pager.
! With "exact address" enabled, mailboxes that contain non-ascii characters, or sequences that require RFC 2047 encoding, will be written in normalized "Name <user@host>" form when sending emails, so that they can be properly RFC 2047 and IDNA encoded.
The Release Notes http://www.mutt.org/relnotes/1.14/ are described as a review of some of the more interestign features in this release.