在每個專案資料夾中，都有一個 Lexicon.xml 檔案（至少如果已經進行過回譯的話）。
此外，許多專案中都有外國人參與（顧問、促進者），他們可能更適合使用「詞典」，即使是一個簡單的詞典也好。
我進行了一些思考和研究，看看如何輕鬆地「查看 PT 詞典」。我的夢想是擁有一個非常簡單的 Python 外掛程式（由我製作；好吧，在我的夢想中我可以做到），它可以在右鍵點擊單詞時顯示已輸入的內容。另外，還有一個可選的詞典視窗，可以在其中瀏覽或搜尋……
我也開始研究專門的 XML 工具和編輯器。有些工具可以將 xml 檔案轉換成相當漂亮的表格。但我發現 PT 詞典的結構對這些工具並不友好，因為實際的「詞元」是像「屬性」一樣存儲的，而不是像「內容」那樣。而且我目前看到的工具（價格合理的）也不喜歡某些詞元比其他詞元有更多的義項這一事實，即合適的表格定義需要一個結構化的系統，包括索引、條目、子索引和更多條目。
在我花更多時間在這上面之前，我想聽聽其他支持者和用戶的意見，看看目前已經有哪些工具，其他人在做什麼，以及是否有任何合適的工具浮現出來。
我主要合作的專案不希望將 PT 和 Flex 連結起來，因為這兩種工具（在這裡）以不同的速度通過版本（和重新命名）進行演變。這是一個歷史性的決定，原因是正字法變更、程式遷移和其他原因造成的不良體驗。雖然有將 PT 數據離線傳輸到 Flex 的方法，但從不是即時進行的，因此「通過 Flex 查詢」只是一個選項，前提是可以在同一台機器上維護一個專門用於此目的的分支版 Flex，與生產版 Flex 並存。
這是一個非常開放的問題，暫時沒有急迫性，但非常歡迎任何意見。謝謝。
In each project folder there is a file Lexicon.xml (at least if some back-translation has been done).
Also in many projects there are foreigners involved (consultants, facilitators) who could rather benefit from a “lexicon”, even a humble one.
I have done some thinking and some research to see how to easily “look into the PT lexicon”. My dream would be to have a very humble Python-plugin (made by me; well, in my dreams I can) that brings up what has been entered upon right-click on a word. And optionally a lexicon-window, where one could browse or search…
I have also started looking into dedicated XML tools and editors. Some can turn an xml file into a rather pretty table. But I found the structure of the PT lexica is not helping such tools by having the actual “lexemes” stored rather like “attributes” not so much like a “content”. And the tools I have seen so far (the affordable ones) also do not like the fact that some lexemes have more senses than others, i.e. that a suitable table-definition would need a structured system of index, entry, indixes and more entries.
Before I spend more time on this, I would like to hear from other supporters and users about what is out there already, what other people are doing and if any fitting tools are coming to mind.
The project I work most with, does not want to link PT and Flex because those two tools evolve (here) through versions (and re-namings) at different speeds. This is a historical decision, due to bad experieces from orthography changes, program-migrations and other reasons. There is offline-transporting of PT data into Flex, but never just-in-time so “looking up through Flex” is one option only, if keeping a forked special-Flex for that purpose on the same machine as the production-Flex is possible.
This is a very open question, no urgency for once, but any input muchly welcome. Thank you.
機器翻譯自 English
