电子书标准与HTML [英] eBook standards vs HTML
问题描述
我希望获得有关任何行业电子书标准与使用
普通HTML（以及一些服务器端脚本）的反馈。我相信HTML适合展示书籍，但我可能会遗漏一些东西。作为网站管理员
的Authorama.com我也有兴趣知道是否有任何可以通过转换为某种电子书格式直接获得的
（我'不是
出售任何东西，因为这些书属于公共领域 - 我在谈论
获得额外的读者，优化的阅读体验等。） Philipp div Lenssen写道：
I would like to get feedback on any industry eBook standards vs using
plain HTML (along with some server-side scripting). I believe HTML is
suited to display books, but I might be missing something. As webmaster
of Authorama.com I''d also be interested in knowing if there''s anything
that can be directly gained by converting to some eBook format (I''m not
selling anything, as the books are public domain -- I''m talking about
gaining additional readers, optimized reading experience, etc.).
我希望获得有关任何行业电子书标准与使用
平原的反馈意见。
推荐答案
HTML（以及一些服务器端脚本）。我相信HTML适合展示书籍，但我可能会遗漏一些东西。作为Authorama.com的网站管理员，我也有兴趣知道是否有任何可以通过转换为某种电子书格式直接获得的东西（我不是
）出售任何东西，因为书籍是公共领域 - 我在谈论
获得额外的读者，优化的阅读体验等。）
I would like to get feedback on any industry eBook standards vs using
plain HTML (along with some server-side scripting). I believe HTML is
suited to display books, but I might be missing something. As webmaster
of Authorama.com I''d also be interested in knowing if there''s anything
that can be directly gained by converting to some eBook format (I''m not
selling anything, as the books are public domain -- I''m talking about
gaining additional readers, optimized reading experience, etc.).
我认为HTML是最好的选择。在这种类型的东西中通常会有太多的自私（我们将以PDF格式分发它，所以它会...... / b
看起来像我们喜欢它，但我的意见是应该有一个
的妥协。 HTML可能没有所有必需的功能，但目前几乎每台PC上的浏览器都是
，并且HTML文件大小很小，并且它有足够的排版功能可以获得回报。至于获得大多数读者的好处，除了新的软件要求之外，还有一些事情比仅仅为了阅读可以用HTML表示的东西更具威慑性。
或纯文本。
I think that HTML is the best choice. There''s normally too much
selfishness in this type of thing ("we''ll distribute it in PDF, so it''ll
look like we like it"), but my opinion is that there should be a
compromise. HTML may not have every needed feature, but browsers are
currently on virtually every PC and HTML file sizes are small, and it
has enough typographic features to be a payoff. As for obtaining the
most readers, there are few things more deterring than the requirement
of new software just to read something that could be represented in HTML
or plain text.
> Philipp Lenssen写道：
>Philipp Lenssen wrote:
我会想要获得有关任何行业电子书标准的反馈，而不是使用纯HTML（以及一些服务器端脚本）。我相信HTML适合展示书籍，但我可能会遗漏一些东西。 ...
I would like to get feedback on any industry eBook standards vs using
plain HTML (along with some server-side scripting). I believe HTML is
suited to display books, but I might be missing something. ...
2004年1月13日星期二11:48:13 +0000，Keith Bowes回答：我认为HTML是最好的选择。 ...
我曾经同意你的意见，直到我真的试图为一本书做这件事
我妻子写的。我会说这取决于书。
当然，HTML是传统的理想选择。小说作品，用一种字体书写
，可能还有一些斜体。大多数教科书也应该在HTML中运行良好，因为即使有标题和块引用
和插图和侧边栏，作者也一般不在乎
*确切*它们对读者的看法，只要他们以可理解的方式传达内容。
它得到一个当作者想要使用特定的
排版技巧作为一部小说的一部分时，会更加棘手。我的妻子希望在网上发布她的小说（共享软件），而且很容易让她在Microsoft Word中做的很多事情对我来说非常困难。 >
在HTML / CSS中为她复制。示例：三个字符在他们的三个不同的笔迹中写了
待办事项列表。我不能指望所有读者下载并安装三种手写字体，所以
我能用HTML / CSS做的最好的是默认的草书字体，
草书+斜体，草书+粗体（看起来很糟糕，并留下
读者想知道哪个字体与哪个人相关）。另一个例子：
一个角色遭受记忆风暴随机记忆在各种字体的重叠文本框中显示为
。在CSS中获得
定位是一场噩梦，当然在某些浏览器中它会完全失败
。
For像这样的东西，PDF是一个更好的解决方案。
...这种类型的东西通常有太多的自私（我们将以PDF格式分发它） ，所以它会看起来像我们喜欢它，但我的意见是应该有一个妥协。 ...
这回到旧的，旧的将内容与演示文稿分开
参数。有时候演示文稿*是*内容的一部分，在
这种情况下，期望它作为作者出现而不是自私的
想要的。
... HTML可能没有所有必需的功能，但目前几乎所有PC上的浏览器和HTML文件都很小，而且它有足够的排版功能可以获得回报。至于获得大多数读者，除了阅读可用HTML
或纯文本表示的内容之外，几乎没有什么比新软件的要求更具威慑力。
On Tue, 13 Jan 2004 11:48:13 +0000, Keith Bowes replied:I think that HTML is the best choice. ...
I used to agree with you, until I actually tried to do it for a book
my wife has written. I would say it depends on the book.
Certainly, HTML is ideal for a "traditional" work of fiction, written
in one typeface with maybe some italics. Most textbooks also ought to
work well in HTML, because even if there are headings and blockquotes
and illustrations and sidebars, the author doesn''t generally care
*exactly* how they appear to the reader, as long as they communicate
the content in an understandable manner.
It gets a lot more tricky when the author wants to use specific
typesetting tricks as part of, say, a novel. My wife wants to
distribute her novel online (shareware), and many things that were
easy for her to do in Microsoft Word are very difficult for me to
replicate for her in HTML/CSS. Example: three characters are writing
a to-do list in their three different handwritings. I can''t expect
all her readers to download and install three handwriting fonts, so
the best I can do in HTML/CSS is the default cursive font,
cursive+italic, and cursive+bold (which looks crappy and leaves the
reader wondering which font goes with which person). Another example:
a character suffers a "memory storm" in which random memories appear
in overlapping boxes of text in various fonts. Getting the
positioning right in CSS is a nightmare, and of course it will fail
completely in some browsers.
For something like this, PDF is a much better solution.
... There''s normally too much
selfishness in this type of thing ("we''ll distribute it in PDF, so it''ll
look like we like it"), but my opinion is that there should be a
compromise. ...
This gets back to the old, old "separating content from presentation"
argument. Sometimes the presentation *is* part of the content, in
which case it''s not selfish to expect it to appear as the author
wants.
... HTML may not have every needed feature, but browsers are
currently on virtually every PC and HTML file sizes are small, and it
has enough typographic features to be a payoff. As for obtaining the
most readers, there are few things more deterring than the requirement
of new software just to read something that could be represented in HTML
or plain text.
这是一个权衡。要求您的客户更新他们的浏览器以获得最新版本，以便CSS正常工作，可能会导致他们同样麻烦。 PDF文件也很小，并且
Adobe Acrobat Reader适用于许多不同的平台。
但我同意使用专有的电子书格式（我的意思是，除了
PDF）通常是一个坏主意。
= - = - = Bill Statler = - = - =
It''s a tradeoff. Requiring your customers to update their browsers to
the latest versions, just so that the CSS works properly, may be
causing them just as much trouble. PDF files are also small, and the
Adobe Acrobat Reader is available for lots of different platforms.
But I agree that using a proprietary e-book format (I mean, other than
PDF) is generally a bad idea.
=-=-= Bill Statler =-=-=
Bill Statler写道：
Bill Statler wrote:
Keith Bowes：
Keith Bowes:
Philipp Lenssen写道：
Philipp Lenssen wrote:
我想获得有关任何行业电子书标准与使用纯HTML（以及一些服务器端脚本）的反馈。我相信HTML适合展示书籍，但我可能会遗漏一些东西。 ...
I would like to get feedback on any industry eBook standards vs using
plain HTML (along with some server-side scripting). I believe HTML is
suited to display books, but I might be missing something. ...
我认为HTML是最佳选择。 ...
I think that HTML is the best choice. ...
我曾经同意你的意见，直到我真的试着为一本书做这件事
我妻子写的。我会说这取决于这本书。
当然，HTML是传统的理想选择。小说作品，用一种字体写成，可能有一些斜体。大多数教科书也应该在HTML中运作良好，因为即使有标题和区块引用，插图和侧边栏，作者也一般不关心*确切*它们看起来如何读者，只要他们以可理解的方式传达内容。
当作者想要使用特定的排版技巧作为其中一部分时，它会变得更加棘手，比如说，小说。
I used to agree with you, until I actually tried to do it for a book
my wife has written. I would say it depends on the book.
Certainly, HTML is ideal for a "traditional" work of fiction, written
in one typeface with maybe some italics. Most textbooks also ought to
work well in HTML, because even if there are headings and blockquotes
and illustrations and sidebars, the author doesn''t generally care
*exactly* how they appear to the reader, as long as they communicate
the content in an understandable manner.
It gets a lot more tricky when the author wants to use specific
typesetting tricks as part of, say, a novel.
曾经有一段时间，novellists能够向公众描述情况，以及具体的排版方式诀窍根本不是
。
-
芭芭拉
http://home.wanadoo.nl/b。 de.zoete / html / weblog.html
http://home.wanadoo.nl/b.de.zoete/html/webontwerp.ht ml
There was a time that novellists were able to describe situations so
well to their public, that the specific typesetting tricks were not
necessary at all.
--
Barbara
http://home.wanadoo.nl/b.de.zoete/html/weblog.html
http://home.wanadoo.nl/b.de.zoete/html/webontwerp.html
这篇关于电子书标准与HTML的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
