From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Lastrite app-text/chmsee. Semi-lastrite libopensync-plugin-google-calendar.
Date: Wed, 2 May 2012 21:39:07 -0600 [thread overview]
Message-ID: <20120502213907.2706fff0@gentoo.org> (raw)
In-Reply-To: 4F9BC3D3.2090309@gentoo.org
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On Sat, 28 Apr 2012 12:17:55 +0200
Michael Weber <xmw@gentoo.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> According to upstreams homepage [1],
> the current tagged v1.99.09 does support xulrunner 11.0.
>
> @dirtyepic: Any chance to bump the version in portage?
> I can take a look (and grab this package).
From the bug report it sounded like xulrunner is going away completely.
> Is there any state-of-the-art(tm) alternative to read .chm ebooks? I
> wouldn't want to loose this possibility.
I also maintain kchmviewer and xchm and I think there are a couple other
non-dedicated readers that support it. Are there any features chmsee has that
these are missing? I added chmsee to replace gnochm but I don't think I've
ever used it. I use xchm for my collection. It's tech books and manuals
though, nothing too extravagant. It doesn't release often but upstream is
responsive.
--
fonts, gcc-porting
toolchain, wxwidgets
@ gentoo.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-05-03 3:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 6:21 [gentoo-dev] Lastrite app-text/chmsee. Semi-lastrite libopensync-plugin-google-calendar Samuli Suominen
2012-04-28 10:17 ` Michael Weber
2012-04-28 12:20 ` Ben
2012-04-28 14:15 ` Michał Górny
2012-04-29 10:54 ` Samuli Suominen
2012-04-29 11:42 ` Pacho Ramos
2012-04-30 19:00 ` Samuli Suominen
2012-04-30 19:27 ` Stelian Ionescu
2012-04-30 19:33 ` Samuli Suominen
2012-05-03 3:39 ` Ryan Hill [this message]
2012-05-03 20:53 ` [gentoo-dev] " Michael Weber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120502213907.2706fff0@gentoo.org \
--to=dirtyepic@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox