在思考如何最好地支持这些需求时，我在考虑几个选项：
a) 每个配置都有一个选项来存储其自己的本地 FRT 书，最初可能从 Paratext 的 FRT 书复制而来，并且是特定于配置的——从而消除了每次从不同配置打印时都需要不断更改 Paratext 中 FRT 文件的需求。这种方法的优点是实现简单，并且您将获得本地 FRT 规范中指定的确切内容。这种方法的缺点是：
- 随着本地 FRT 随着每次新出版物的发布而不断演变/改进，在不同书卷之间保持一致性很快就会变得困难；因此，如果您决定更改其中一个，您可能需要重新访问所有其他保存的配置以更新它们。
- 一旦制作了 Paratext FRT 的副本，Paratext 中的原始 FRT 将不会更新。
b) 另一个选项是继续使用 Paratext 的 FRT 书，但允许配置更改/更新其中的内容。类似于 FRTbookchanges.txt 的文件，在出版时填充 FRT。想象一下这样一个系统：我们有一个单一的项目级 FRT 模板，其中包含一些（用户定义的）代码，如 <MainTitle>, <SubTitle>, <CopiesPrinted>，甚至像 <MainTitleIndonesian> 或 <MainTitleVernacular> 这样具体的代码，然后 FRT 书的其余部分将包含需要在所有出版物中出现的材料。
\id FRT XYZ Language Name (C) 2010-2021 Copyright Notice
\periph Title Page
\mt <MainTitleVernacular>
\mt2 <SubTitleVernacular>
\periph Publication Data
\imt <MainTitleVernacular>
\imt2 <SubTitleVernacular>
\pc <MainTitleIndonesian>
\pc <SubTitleIndonesian>
\pc Language: Wakawaka
\pc Script: Latin
\pc Copies Printed: <CopiesPrinted>
PTXprint 设置只需列出在 FRT 书中找到的内容，并允许您填写它们。我们可以做得更花哨，为每个代码指定vernacular（土著语言）、regional（区域语言）、national（国家语言）、international（国际语言），或者保持简单，如下所示：
<MainTitleVernacular>Looku
<MainTitleIndonesian>LUKA
<MainTitle>Luke
<SubTitle>The Gospel of Jesus Christ by Dr Luke
<CopiesPrinted>250
这个想法显而易见的优点是配置只需要存储最基本的内容（即对于此特定出版物不同的部分）。它还允许您调整或重新排列 Paratext FRT 书的布局，并让所有配置遵循新的/更新的布局。缺点是，如果您试图拥有不同种类的前置内容布局（例如，模块的故事书格式，以及用于教会的正式外观的 Luke+Acts 出版物——这些中的每一个可能需要相当不同的 FRT 定义，尽管许多元素是相似的）。这种方法的另一个问题是，FRT 书将无法在 Paratext 中正常工作（因为被 PTXprint 特定的代码劫持了），尽管一些简单的 PrintDraftChanges.txt 规则可以帮助它在 Paratext 中正常工作。
在两种情况下，所有常规的\zimagecopyrights, \zcopyright, \zlicense类型的代码也将照常工作。我不确定这是否可能，但能够说出类似以下内容将很棒：
\pb
\includePDF "c:\data\ForewordFromGovernor.pdf"
\pb
\ztableOfContents
\pb
您对以上选项有何看法？点击回复并告诉我们您更喜欢哪一个以及为什么？
As we think through how to best support these needs, I’m wondering about a couple of options:
a) Each configuration would have an option to store its own local FRT book, which might initially be copied from Paratext’s FRT book, and be config-specific - thus removing the need to keep changing the FRT file in Paratext for each different config you print from. The advantage of this approach is that it is simple to implement, and you’ll get exactly what you’ve specified in the local FRT specification. The disadvantages of this approach are:
- It quickly becomes difficult to maintain consistency across different books as the local FRT continues to evolve/improve with each new publication; so if you decide to change something in one, you may have to re-visit all the other saved configs to update them as well.
- Once a copy of Paratext’s FRT has been made, the original FRT in Paratext would not be updated
b) Another option is to keep using Paratext’s FRT book, but allow the configuration to change/update what is in there. Something like FRTbookchanges.txt which fills in the FRT at publishing time. So imagine a system where we have a single project-wide FRT template with some (user-defined) codes like <MainTitle>, <SubTitle>, <CopiesPrinted>, or even something specific like <MainTitleIndonesian>, and <MainTitleVernacular>, and then the rest of the FRT book would contain the material that needs to be in ALL publications.
\id FRT XYZ Language Name (C) 2010-2021 Copyright Notice
\periph Title Page
\mt <MainTitleVernacular>
\mt2 <SubTitleVernacular>
\periph Publication Data
\imt <MainTitleVernacular>
\imt2 <SubTitleVernacular>
\pc <MainTitleIndonesian>
\pc <SubTitleIndonesian>
\pc Language: Wakawaka
\pc Script: Latin
\pc Copies Printed: <CopiesPrinted>
The PTXprint settings could just list the found in the FRT book and allow you to fill those in. We could get fancy and specify vernacular, regional, national, international for each of the codes, or just keep it simple as follows:
<MainTitleVernacular>Looku
<MainTitleIndonesian>LUKA
<MainTitle>Luke
<SubTitle>The Gospel of Jesus Christ by Dr Luke
<CopiesPrinted>250
The obvious advantage of this idea is that the configuration only needs to store the bare necessities (i.e. what is different for this particular publication). It would also allow you to tweak or re-arrange the layout of Paratext’s FRT book, and have all configs follow the new/updated layout. The disadvantage would be if you are trying to have different kinds of front-matter layout (say, a story-book format of a module, and an official-looking Luke+Acts publication for use in church - each of these may need a rather different FRT definition, although many elements would be similar). Another problem with this approach is that the FRT book wouldn’t work properly for Paratext (having been hijacked by PTXprint-specific codes), although some simple PrintDraftChanges.txt rules would help it work fine in Paratext.
In BOTH cases, all the usual \zimagecopyrights, \zcopyright, \zlicense kinds of codes would also work as normal. And I’m not sure if this is possible, but it would be great to be able to say things like:
\pb
\includePDF "c:\data\ForewordFromGovernor.pdf"
\pb
\ztableOfContents
\pb
What are your thoughts on the above options? Hit Reply and tell us which you prefer and WHY?
