一份良好的術語表是許多首次接觸聖經的孤立讀者理解經文的關鍵。
感謝大家。我很高興看到這個討論串，裡面充滿了「我也是這樣」的擔憂，並且已經有了許多好的建議。
我原本計畫寫一些關於操作方法的問題，可能還有一些功能請求，但這件事發生得太早了。
各位好，這些關於術語表結構的問題確實非常重要。為什麼呢？
請考慮那些非公開的專案，它們很少在論壇上有發言人。一位典型的現代讀者可能來自其他宗教。他或她可能在 Play Store 上找到了一個聖經應用程式，並作為探索者第一次閱讀聖經。
因此，我們需要一份完整且易於使用的術語表：
PT8 已經擁有強大的工具和穩固的結構，即章節和經節以及交叉引用。但術語表並未妥善利用這些功能，一些其他使用者嘗試過使用章節和經節的變通方法。
我自己嘗試建立章節時遇到了錯誤訊息：章節只能包含數字。為什麼？如果解除這個限制（請），我們就可以使用最穩固的結構「章節」，並將其分配給我們字母表中的字母。這存在很大的危險：如果允許這個想法，其他使用者可能會將路加福音（LUK）的章節稱為「5」或「五」。這將非常糟糕。我不知道為什麼，但可能很糟糕，它可能會破壞導航工具。因此，將需要另一個檢查工具來檢查「所有非術語表書籍中的非法章節編號」。
為什麼我們迫切需要連結術語表條目之間：
我們的語法在詞首位置有名词的類標記。因此，同一條目的單數和複數形式相距甚遠：S_priest（單數祭司）不在 P_priest（複數祭司）旁邊。
我們編寫術語表的方式是，將文本中最典型的「需要解釋的詞」作為術語表的關鍵詞。例如，讀者最常以複數形式遇到「法利賽人」，所以我們的描述列在「P_pharisee」下。但有些讀者可能會手動前往「S_pharisee」，然後我們需要一個連結。因為我們的類系統非常豐富，即使是母語者也不確定單數如何構成複數，有幾種選項。目前我只是寫一個特殊的箭頭符號和我想要引用的其他術語表詞彙，使用者必須自己導航以找到主要條目。
因此，章節（針對每個字母或甚至字母組合）將非常有用。並且每個術語表條目都可以具有經節的狀態。這樣交叉引用和連結就成為可能。在 PT8 中進行變通操作從不感覺完全安全。所以我懇請開發人員考慮這一點並正式實現它。
我們的術語表變得很大。20 頁印刷頁的限制不適用於我們的閱讀應用程式。我們也需要幫助來導航我們的術語表以進行日常工作，僅僅上下滾動就花費了永遠的時間。另一個使用現有章節和經節結構的理由，因為對於這些，我們在每個 PT8 視窗頂部都有穩定的導航工具，一些使用者也知道他們的鍵盤快捷鍵。
我們需要的另一個功能是進行每個術語表項目工作後續處理的方法。我想你們稱之為專案進度。請考慮我們的工作方式：
我們不會在特定的日子坐下來說「讓我們為字母 K 製作所有術語表條目。」我們更傾向於翻譯主文本，並在每個章節之後，當我們的研究和筆記還容易獲取時，選擇所有那些在翻譯和/或與他人檢查和閱讀時造成問題的詞彙。然後我們編寫這些術語表條目。由於是早期階段，我們通常每個文本章節有五到十個條目，並且隨著我們更頻繁地說「我們已經完成那個了」，它正在慢慢減少。
因此，術語表條目應該具有某種虛擬批次編號或虛擬管理章節，用於應用專案進度和檢查工具。由於我們不是按字母順序編寫它們，並且新條目不斷被添加，目前沒有東西可以追蹤。如果很快沒有進展，我將需要創建另一個私人標記並發明一行狀態，基於我們經驗證的專案進度工具中的「階段」和「任務」，但應用於個別術語表條目。
術語表不是聖經，但它是任何新讀者訪問和理解主文本的一個非常重要的關鍵。你會驚訝於我們世界這個地區有多少「基本」詞彙是未知的。因此，我們希望創建相同水平的質量並應用現有的質量控制和後續處理工具。
請為這個反饋歡喜：我的團隊同事上週從一次製作術語表條目的會議回來時非常高興。當地翻譯人員必須努力工作，並圍繞幾個新概念處理 POSS_head。但最後 PRO 說了一些像「這太驚人了，我們學到了很多，現在事情更有意義了」的話。有趣的是（或可悲的是），這次工作會議是在主文本章節已經翻譯之後進行的，所以所有詞彙和概念應該在此之前已經解釋過。似乎術語表工作正在變成我們整個團隊的迷你聖經學校。
我猜測，如果我們查看現有結構而不是發明一個單獨的系統，大多數使術語表更具功能性的工作已經完成。它可能簡單到允許章節和經節是字母數字而不是僅數字（當然要檢查不想要的副作用）。我們願意作為測試者提供幫助，因為這很重要。
感謝這個討論串中的所有想法和處理，我會熱切關注。
A good glossary is the key to to understanding scripture for many first-time isolated readers.
Thank you all. I am delighted about this thread, fulll of “me too” concerns and already full of good input.
I had planned to write up some questions about how-to and possibly some feature requests, but this has happened a few days too early.
Dear all, these questions about structuring the glossary are indeed very important. Why?
Please consider all those not-public projects, who rarely have spokespeople in a forum. A typical modern reader might be from another religion. He or she might have found a scripture app on the Play Store and is reading for the first time ever, as an enquirer.
So we need a complete and user-friendly glossary:
-
we need clickable links from the main-text to the most relevant glossary entry
-
we need an option to refer from one glossary-entry to another, also by clickable links
PT8 has already great tools and solid structures, namely chapters, verses and cross-references. But the glossary is not properly using these and some other users have tried hacks with chapters and verses.
I myself have tried making chapters and got error messages: chapters can only have digits and numbers. Why? If you lift this limit (please), then we could use the most solid structure “chapter” and assign those to the letters of our alphabet. There is a great danger: If you allow this idea, then other users might call LUK chapter “5”, LUK chapter “five”. This would be very bad. I do not why, but probably bad, it might break the navigation tools. So there would arise a need for yet another checking tool about “illegal chapter numbers in all non-glossary books”.
Why do we need urgently to link between glossary entries:
Our grammar has got the class-markers for our nouns in word-initial position. So singular and plural of one entry are very far from another: S_priest is not next to P_priest.
We write our glossary so that each “word which needs explaining” the most typical rendering in the text is the key-term for our glossary. So for example “pharisees” is most often met by a reader in the plural, so our description is listed under “P_pharisee”. But some readers might manually go to “S_pharisee” and then we need a link. Because our class-system is so rich, that even a native speaker cannot tell from a singular, how the plural is being formed, there are several options. So far I am just writing a special arrow-symbol and the other glossary term I want to refer to, and the user has to navigate himself to find the main entry.
So chapters (for each letter or even combination of letters) would be very helpful. And each glossary entry could have the status of a verse. So that cross-referencing and linking becomes possible. Hacking PT8 never feels entirely safe. So I beg the developpers to consider this and officially make it happen.
Our glossary is getting big. A limit of 20 printed pages does not apply to our reading apps. We also need help to navigate our glossary for our normal work, just scrolling up and down is taking for ever. Another reason to use the existing structures of chapters and verses, because for those, we have stable navigation tools on top of each PT8 window, and some users know their keyboard-shortcuts too.
Another feature we need is a way to do the follow-up of the work on each glossary item. I think you call this project-progress. Please consider our way of working:
We do not sit down on certain days and say “let us make all the glossary entries for the letter K.” We rather translate the main text and after each chapter, while we still have our studies and notes readily available, we select all those words which caused problems for translation and/or for checking and reading with other people. And then we write those glossary entries. Since it is early days, we typically have five to ten entries per chapter of text, and it is slowly getting less, as we can more often say “we have done that one already”.
So glossary entries should have something like virtual batch-numbers or virtual-admin-chapters for the purpose of applying the project-progress and checking-tools. Since we do not write them in alphabetical order, and new entries constantly keep being added, there is nothing at the moment to keep track. If nothing comes up soon, I will need to create yet another private marker and invent a status-line, based on our proven “stages” and “tasks” from the project-progress tools, but applied to individual glossary-entries.
Glossary is not Scripture but is a very important key for any new reader which allows to access and understand the main text. You would be surprised, how many “basic” terms are unknown in our part of the world. So we want to create the same level of quality and apply the existing tools of quality-control and follow-up.
Please rejoice over this feedback: My team colleague came back very glad last-week from a session of crafting glossary-entries. The local translator had to work hard and get POSS_head around several new concepts. But in the end PRO said something like “this is so amazing, we are learning so much and things make even more sense now”. Funny enough (or sadly) this work session was after the chapter of main text was already translated, so all the terms and concepts should have been explained before. Seems the glossary-work is turning into a mini bible-school for our entire team.
I would guess that - if we look at the existing structures rather than inventing a separate system - most of the work for a more functional glossary is already done. It might be as simple as allowing chapters and verses to be alpha-numeric rather than numeric-only (and checking for unwanted side effects of course). We are willing to help as testers, because this is important.
Thank you for all the ideas and the processing in this thread, will watch this with eagerness.
