您好，
我不使用 Mac，因此無法透過實際經驗驗證以下內容。我認為主要問題在於 InDesign 無法在具有 ARM 架構的 Windows / Parallels 中運作。
看起來 Parallels 20.2 嘗試為 Windows 10 或 Windows 11 提供 x86_64 模擬支援，但存在一些限制。聽起來效能可能會非常緩慢。
https://www.parallels.com/blogs/parallels-desktop-20-2-0
關於提取 PA 產生的檔案以在 Mac OS 上的 InDesign 中使用——PA 所做的包括：1) 建立一個包含整個出版物（一個或多個文件）的 InDesign 書籍，2) 為每卷聖經書卷或附屬書卷建立一個 InDesign 文件，3) 一組 InDesign 標籤文字檔案，這些檔案被「置入」（InDesign 的術語）到文件中。除此之外，4) PA 管理並驗證每頁上註釋、交叉引用和頁眉文字等內容的放置。
這些步驟中最與您的問題相關的方面可能是 3) PA 生成的標籤文字檔案。這些檔案可以置入 InDesign 文件中，並包含用於管理所有內容的完整樣式集合。實際建立和管理內容在文件中流動的其他方面（1、2、4）需要您自行管理。（您可以在這裡查看 PA 在基本聖經版面設計頁面中所做事項的摘要）。
Hello,
I don't use a Mac, and so I cannot validate the following by experience. I think the main issue is InDesign not working in Windows / Parallels with ARM architecture.
It looks like Parallels 20.2 attempts to support x86_64 emulation for Windows 10, or Windows 11, with some limitations. It sounds like the performance may be quite slow.
https://www.parallels.com/blogs/parallels-desktop-20-2-0
In terms of extracting file(s) which PA produces to use in InDesign on Mac OS --- What PA does is to produce 1) an InDesign book to contain the whole publication (one or more documents), 2) an InDesign document for each scripture book or peripheral book, 3) a collection of InDesign tagged text files which are 'placed' (the InDesign term) into the document. Beyond that, 4) PA manages and validates the placement of content such as notes, cross references, and header texts on each page.
The most relevant aspect of those steps (with respect to your question) might be the 3) tagged text files which PA generates. These are files which can be placed in an InDesign document which contain a full collection of styles for managing all the content. The others aspects of actually creating and managing the flow of the content through a document (1,2,4) are things you would need to manage yourself. (You can see a summary of the things PA is doing on pages for a basic Bible layout here).
機器翻譯自 English
