我沒有將此貼文標記為「問題」。這可能是一個錯誤報告,除非我發現我們做錯了什麼。[編輯與劇透:這並不是錯誤;我們忽略了一個功能;請閱讀整個討論串以了解詳情;現在已標記為「問題」,標題標記為「已解決」;一切正常]
最近一個專案被分支(fork)了:先進行本機的「備份專案到檔案」(Backup project to file),然後進行本機的「從檔案還原專案」(Restore project from file),並選擇「新專案」(New Project)選項。在建立新專案的過程中,按照 PT 的建議,選取了所有檔案,包括列為「註釋標籤 [日期和時間]」(Note Tags [date and hour])的內容。新專案已正確註冊,目前運作正常。
但今天團隊注意到*,所有特殊註釋不再像以前那樣被標記。專案中的特殊標籤消失了。註釋本身沒問題。但所有原本有特殊標籤和圖示的地方,現在在(註釋清單視窗)中顯示為空白,而通常那裡應該顯示圖示。
我進行了一些調查:
我們現在有一個新的 CommentTags.xml 檔案,幾乎是空的。看起來 PT 在分支後沒有找到該檔案,並建立了一個新的空白檔案,其中只有預設的紅旗。(專案目前使用 PT 9.3.103.7。)
我們仍然可以存取舊的 CommentTags.xml 檔案,其中包含我們的特殊標籤和圖示。(這是來自 PT9 版本,該版本在 2022 年秋天左右是「最新版」。)
我找到了這個相關問題(關於 PT7)
其中用戶被鼓勵說「複製 CommentTags.xml 檔案不應造成任何問題。」
既然我們現在使用的是 PT9 最新版,我想在進行嫁接或拼接過程之前,尋求類似的鼓勵。我可以用舊的完整 CommentsTags.xml 取代新的不完整檔案嗎?
我對兩個 XML 檔案進行了比較,發現結構完全相似。只是舊檔案有更多的條目。我會冒這個風險。
感謝您的想法。
簡而言之:
關於可能的 B 計畫的註釋:我知道如何手動在專案屬性的「註釋」標籤頁中建立新標籤並選擇圖示。我知道我們註釋中的名稱、圖示和範本。我只是擔心,如果我透過 PT 圖形介面重新建立舊系統,可能會分配不同的標籤 ID。舊 XML 檔案中缺少某些 ID,這告訴我團隊過去一定刪除過某些標籤。因此,我考慮過這可能比修改 XML 檔案更「安全」。但由於 ID 無法透過圖形介面存取,我並不喜歡這個 B 計畫。
*今天我們有一個場合,用戶 X 像過去一樣將一些註釋發送給用戶 Y,要求將一整批編輯輸入 PT 主專案,包括對某些關鍵術語的拼寫更改。就在這時,團隊發現他們的特殊標籤和圖示不見了。
用戶 X 在語言觀察方面非常資歷深厚,並能與團隊討論這些問題。然後,PT 中這類根本性的編輯總是由團隊成員 Y 處理,他對 PT 有很好的感覺,知道如何輸入哪種類型的更改;特別是當它們涉及超過一節經文時。
過去在用戶 X 和用戶 Y 之間,曾有一個用於此類工作的特殊標籤和圖示。
這些標籤和圖示(約 10 個)對團隊和專案很重要;它們是工作流程的一部分,確實有助於不在紅旗中迷失。總共有許多註釋,因此能夠篩選並知道什麼是什麼是重要的。
I did not mark this post as a “question”. It might be a bug-report, unless I will find out that we did something wrong. [edit and spoiler: It was NOT a bug; we overlooked a feature; read the entire thread to know it all; this is now tagged as a “question” and the title is marked as “solved”; all is well]
Recently a project was forked: A local “Backup project to file” and then a local “Restore project from file” with the option “New Project”. All files were selected in the process of creating the new project, as proposed by PT, including what was listed as “Note Tags [date and hour]”. The new project is properly registered and works fine so far.
But today the team has noticed* that all special notes are no longer tagged as before. In the project the special tags are gone. The notes themselves are fine. But all those that had special tags and icons are showing a blanc space (in the Notes List window) where normally the icon would be.
I have done some digging:
We have presently a new file CommentTags.xml which is almost empty. Looks like PT did not find it after the fork and created a new blank one with only the default red-flag. (Project is currently using PT 9.3.103.7.)
We still have access to the former file CommentTags.xml with our special tags and icons. (This is from a PT9 version which was “the latest” around autumn 2022.)
I found this related question (about PT7)
where the user is being encouraged with " Copying the CommentTags.xml file should not cause any issues."
Since we are now in PT9, latest version, I want to ask for similar encouragement, before I do the grafting- or splicing-process. Can I replace the the new incomplete file with the old and complete CommentsTags.xml?
I did a file-compare on both XML files and find that the structures are fully similar. Just the old file has got more entries. I would risk it.
Thank you for your thoughts.
TL/DR:
Note about a possible plan B: I know how to manually create new tags and select icons in the project properties “notes” tab. I know the Names and the Icons and the Templates from our notes on notes. I just fear that different Tag-IDs might get assigned, if I re-create the old system from the PT GUI. There are certain IDs missing from the old XML file, which is telling me that the team must have deleted certain tags in the past. So I have considered this, as possibly “safer” than to hack XML-files. But as the IDs are not accessible via the GUI, I do not really like this plan B.
*Today we had an occation where user X sent some notes to user Y, as in the past, requesting that an entire batch of edits should be entered into the PT main project, including changes-of-spelling for certain key terms. This was the moment, when the team discovered that their special tags and icons had gone missing.
User X is very qualified for linguistic-observations and for discussing such issues with the team. Then such fundamental edits in PT are always handled by team-member Y, who has got a good feel for PT, and for how to enter what type of changes; especially if they concern more than one verse.
There used to be a special tag and icon for such work, between user X and user Y.
Those tags and icons (about 10) are important to the team and project; they are part of the work-flow and really help to not drown in red-flags. There are many notes in total, so it matters that they can filter and know what is what.