docbook 5.0 中书籍的标题页

发布于 2024-08-27 18:54:43 字数 215 浏览 7 评论 0原文

我正在研究 docbook 5.0 中的结构书(小说)。我有几个介绍性的页面,比如关于这本书、关于作者、关于出版商(有版权、关于打印机和排版器的 isbn 信息)、混蛋标题、扉页。

我不确定是否最好在信息元素中构建所有这些内容,或者尝试构建多个部分作为每个介绍性页面的容器。

有没有这方面的例子,或者你能提供一个例子吗?

任何提示表示赞赏。多谢!

坦率

I am looking into structuring book (fiction) in docbook 5.0. I have got several introductory pages like about the book, about the author, about the publisher (with copyright, isbn info about the printer and the pagesetter), bastard title, title page.

I am unsure, if it is better to structure all this in the info element or try to build several part sections as container for each introductory page.

Are there any examples for this, or are you able to provide an example?

Any hint is appreciated. Thanks a lot!

Frank

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

放我走吧 2024-09-03 18:54:44

弗兰克,

简短的回答:两者都有。元素主要是有关包含它的元素的元信息的容器。但什么是版权、isbn 等?您可能会说它只是元素的元信息(正如 Docbook 指南所做的那样,因为它指出该元素“仅限于元信息”),但它也是用户可见的。还请记住,信息的处理期望如下:

被抑制。此包装器中的许多元素可以在演示中使用,但它们通常不会作为包装器格式的一部分进行打印。包装器仅用于识别它们发生的位置。

因此,将其放入元素中可以让图书出版商获取其 XML 数据库的元信息,而将其放入文档正文中则可以让您正确格式化它以进行打印、Web 等。

现在,我注意到您正在使用一本小说书。您可能更适合使用 DocBook Publishers 架构,而不是原始 Docbook。 Publisher 由 OASIS DocBook 出版商子委员会设计,该委员会被授权开发和维护 DocBook 的官方变体以支持出版业。 DocBook Publishers Schema 基于 DocBook 5.0,并以规范的 RelaxNG Schema 格式提供。

它删除了 Docbook 中的许多技术和软件工程元素,因此使用起来更加容易。它还添加了一些诗歌、戏剧和演讲的元素。如果您使用都柏林核心元数据,它还会将它们添加为在块中使用的元素。

请参阅:http://docs.oasis-open.org/ docbook/specs/publishers-1.0-spec.html

存储库位于:http://docbook.svn.sourceforge.net/viewvc/docbook/trunk/docbook/relaxng/publishers/

我一直在使用 Publisher 作为特定的基础开发一个架构非小说类书籍的类型。

Frank,

Short answer: both. The element is primarily a container of meta information about the element that contains it. But what is copyright, isbn, etc? You could argue that it's just meta information for the element (as the Docbook guide does, since it notes that the element is "is confined to meta-information"), but it's also user visible. Remember also that the processing expectations for info read:

Suppressed. Many of the elements in this wrapper may be used in presentation, but they are not generally printed as part of the formatting of the wrapper. The wrapper merely serves to identify where they occur.

So putting it in the elements allow a book publisher to harvest the meta-information for their XML database, while putting it in the body of the document lets you format it properly for print, Web etc.

Now, I notice you're working with a fiction book. You may be better off with the DocBook Publishers schema, rather than the original Docbook. Publisher was designed by the OASIS DocBook Sub Committee for Publishers which was chartered to develop and maintain official variants of DocBook in support of the publishing industry. The DocBook Publishers Schema is based on DocBook 5.0, and delivered in the normative RelaxNG Schema format.

It's a lot easier to work with in that it removes a lot of the technical and software engineering elements from Docbook. It also adds a few elements for poetry, drama and speeches. If you use the Dublin Core metadata, it also adds them as elements for use in blocks.

See: http://docs.oasis-open.org/docbook/specs/publishers-1.0-spec.html

The repository is here: http://docbook.svn.sourceforge.net/viewvc/docbook/trunk/docbook/relaxng/publishers/

I've been developing a schema using Publisher as a base for a particular type of non-fiction book.

海未深 2024-09-03 18:54:43

这一切并不是那么重要。我想说的是,写下内容并移动它,以防它需要去其他地方(稍后)。这完全取决于您使用的 (XSLT)。 XSL 转换过程负责将内容信息从 DocBook XML 转换为例如格式化对象 XML,它(/可以)用于创建 PDF。

This is all not that important. I would say write the content and move it around in case it needs to go somewhere else (later). It all depends on the (XSLT) you use. The XSL Transformation process is responsible of transforming the content information from the DocBook XML into for example Formating Objects XML, which is (/ can) used to create a PDF.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文