理想情況下，它應該有一個名稱，且不應取代已存在的版本。Paratext 在啟動專案進度時，應僅顯示最新版本。不取代舊版本也意味著 Paratext 可以更輕鬆地自動將計畫的任何先前版本更新為新版本（例如如此影片所示）。
給專案計畫開發者的注意事項：
- 您應確保計畫 ID 在版本之間沒有變更。
- 您應確保所有階段和任務的 ID 保持相同。
- 請確保檔案中已設定計畫版本號。
- 理想情況下，您應使用 （按住 Shift 鍵）Paratext > Support and development > Base project plans 來建立新版本。如果您之前不知道這個功能的存在，現在可能已太遲無法再使用它。
請參閱此貼文以獲取有關建立計畫更新的更多資訊。
編輯：看來擁有不同的名稱對於自動更新過程來說，並沒有我最初認為的那麼重要，而且版本號實際上會成為計畫 ID 的一部分（因此格式為 {ID}_{Version}）。
Ideally, it should have a name and should not replace the one that already exists. Paratext should only show the most recent version when starting progress for a project. Not replacing it also means that Paratext can more easily automatically update any previous version of the plan to the new version (e.g. as shown in this video).
Note for the developers of a project plan:
- You should ensure that the plan ID has not changed from one version to the next.
- You should ensure that the ID of all stages and tasks are the same.
- Make sure the plan version number is set in the file.
- Ideally, you used (Hold Shift) Paratext > Support and development > Base project plans to create the new version. If you didn’t know this existed, it is likely too late to work with it now.
See this post for more information on creating plan updates.
EDIT: It appears having a different name isn’t as important to the automatic update process as I originally thought and that the version number actually becomes part of the plan ID (so it’s {ID}_{Version}).
機器翻譯自 English
