creation and internal support of an ebook extension/format

RESOLVED EXPIRED

Status

SeaMonkey
UI Design
--
enhancement
RESOLVED EXPIRED
17 years ago
8 years ago

People

(Reporter: phoenixreads, Assigned: jag (Peter Annema))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
Through the ngs someone discovered my request for relative browsing of a zip
compressed html-based e-book already exists. 

Imagine being able to send someone a compressed section of a web site as an
ebook, for example a web-based user guide for using Mozilla, and it is fully
indexed, completely browsable, can use complex features like flash, not to
mention it is cross-platform compatible.  No special editors or separate
programs would be needed for its creation.  It would be able to do anything
which Mozilla (or Netscape) is capable of doing, including shockware, flash,
javascript, and java.  By default it will be able to take advantage of any
future developments in Mozilla.  It can easily access external WWW links without
any distruption to the flow of reading; that is launching a separate web
browser.  Sounds interesting?

May I bring it to your attention that capability already exists in Mozilla.  If
you exploit it you have the makings of a truly universal ebook format.  The
market is fragmented as each company goes their separate ways with their own
format and editors.  Here is a format which anyone can create using available
applications and know with confidence it can be read by *anyone* with a browser
that supports it.  I also see it gaining enough popularity to become a
cross-browser format as well.  Once created the format cannot be destory or
become obsolete since it will be based on the open-standards of the web and will
grow with the web.

It will become more popular then the Acrobat format.  It will co-existing with
Acrobat since Acrobat is and would still be superior for print-based electronic
books.  Where Acrobat fails to deliver is on web-based electronic books and this
is where the proposed new format comes in.  Also this new format would surplant
many multimedia formats since it would eventually become *the* acceptable
standard.  That is being a supported standard there would be need for a special
software, editors, or even a plugin for that matter.



What is need is the creation and support of a new file format, which like jar
files would be nothing more then a compressed zip file

Intially it can default to a 'index.html' file in the base directory since that
is what many web-based ebooks use as the entry point already.

What would be needed is the creation and support for an XML-based index page
which would be used to create a tree directory in the side bar.  The XML would
define the nature and links of the tree.  This would not be difficult to do at
present.

A future development would be a true cross-referencing, XML-based, *index* page
and this would be incorporated into the search feature of the browser.  Ideally
it would mimic a Google search display in the side bar.

Everything is there, all someone has to do is set things in motion.

Comment 1

17 years ago
For a start we need a mapping from some extension/mimetype (.edoc?) to an URL like: 

jar:<<bookurl>>!/index.html

The mapping should happen when the user clicks on a link, but not when he does a
"Save Link As".
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 2

16 years ago
->apps
Assignee: asa → pchen
Component: Browser-General → XP Apps
QA Contact: doronr → sairuh

Comment 3

16 years ago
-> default assignee
Assignee: pchen → trudelle

Comment 4

16 years ago
cc tpringle, ->future
Target Milestone: --- → Future
Product: Core → Mozilla Application Suite
Assignee: trudelle → jag
QA Contact: bugzilla
Target Milestone: Future → ---

Comment 5

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 6

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 10

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

9 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 12

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.