在每个项目文件夹中都有一个 Lexicon.xml 文件（至少在进行过回译的情况下会有）。
此外，在许多项目中还有外国人参与（顾问、促进者），他们可能更需要一个“词汇表”，哪怕是一个简陋的词汇表也好。
我进行了一些思考和调研，看看如何轻松地“查看 PT 词汇表”。我的梦想是拥有一个非常简陋的 Python 插件（由我制作；好吧，在我的梦想里我可以做到），它能在右键点击某个单词时显示已输入的内容。并且可选地提供一个词汇表窗口，以便浏览或搜索……
我也开始研究专用的 XML 工具和编辑器。有些工具可以将 xml 文件转换为相当漂亮的表格。但我发现 PT 词汇表的结构并不利于这类工具，因为实际的“词元”（lexemes）更像是以“属性”而非“内容”的形式存储的。而且我目前看到的工具（价格实惠的那些）也不喜欢某些词元比其他词元具有更多义项这一事实，也就是说，合适的表格定义需要一个包含索引、条目、更多索引和更多条目的结构化系统。
在我花更多时间在这件事上之前，我想听听其他支持者和用户关于现有工具、其他人正在做什么以及是否有合适的工具浮现在脑海中的意见。
我主要合作的项目不希望将 PT 和 Flex 链接起来，因为这两个工具（在这里）以不同的速度通过版本（和重命名）进行演变。这是一个历史性的决定，源于正字法变更、程序迁移和其他原因带来的糟糕体验。虽然可以将 PT 数据离线传输到 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
