當我們思考如何最好地支持這些需求時，我在考慮幾個選項：
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 書卷的版面，並讓所有設定遵循新的/更新的版面。這種方法的缺點是，如果您試圖擁有不同類型的前置內容版面（例如，模組的故事書格式，以及用於教會的正式外觀的路加福音+使徒行傳出版物——這些中的每一個可能需要相當不同的 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?
