+1
300 次瀏覽

A few days ago, I painfully found out that the tag “nonpublishable” inside a project usfm.sty is important and is being observed by PT8. I had searched for some time why a certain field was never showing in any print-drafts until I discovered this detail.

Now today I am looking for a suitable marker to put some notes into a growing glossary. I found \rem which is tagged as “nonvernacular” and which is …

Used for adding brief comments by a translator, consultant, or support person.

The text I type into \rem gets treated by some inbuilt (vernacular?) spell checker: New words are underlined with those squiggly lines. I did some tests and right-clicked and confirmed a few words in \rem:

They do not show up in the Wordlist, which is good, because they happen to be French and dummy words. The characters also do not show up in the (vernacular) character inventory, which is also good.

Still, I looked and found my test words inside SpellingStatus.xml which does not feel right, as they are not tagged there as non-vernacular. I will quickly undo those tests and will probably need to learn to overlook all those squiggly lines inside all \rem fields.

This is not a real problem, just trying to learn more about PT8 and about using its features correctly and properly.

舊文章 - 以原文顯示
Paratext (934 點) 提出
已重新顯示 | 300 次瀏覽

2 個回答

0
最佳回答

I can confirm that \rem works the same for me. Words in the \rem marker do show the red squiggly, but do not appear in the wordlist.

We usually use \rem at the beginning of a book to give some background behind the book such as what it was adapted from, or when certain stages were completed. This is often helpful to the consultant or other remote people, and comes in handy when it has been years since a book was completed. I’m sure it could have many other uses as well.

舊文章 - 以原文顯示
(1.3k 點) 提出

Thanks for sharing.

Do you note your entries in \rem in the main language (aka vernacular) or in any of the “maintenance” languages like English?

Do you see any “danger” that anybody in the team might right-click because of the red squigglies and create false entries for the main spell checker?

Our vernacular has far too many very short words, almost like English, they all look similar: CVC or CV like cim, cɩm, cǝm, cem, cǝŋ, cɛn.

So even without mixing other languages in, it is rather dangerous for typos, because you make a typo and often the spell checker cannot warn you because that wrong word is also a valid entry. That is why my eyebrows went up, when I noticed this unexpected behaviour for \rem (and there might be other fields concerned).

I do not think, there is immediate need for action. Maybe this just needs to be documented.

舊文章 - 以原文顯示

We use the \rem marker in the vernacular. Since they’re English words, I think our translators know not to try and spell check them, so we haven’t seen much danger of teams spell checking those words. Even if they did, I don’t think it would cause issues with the way we’re handling linguistic checking. I can see how it could be more of an issue with many short words.

I think a useful feature in Paratext would be a guide to the various style markers. I’m sure there are many places to find that information, but it would be ideal if we could have a button in the top ‘style’ box where we could get a little explanation for the particular marker that is being used. It could also have this sort of information, informing the user of any relevant issue with the given marker.

舊文章 - 以原文顯示

+1

Today I was looking how to do the superscript for ordinal numbers. Started reading the official USFM reference. Found nothing. Then looked into our project usfm_custom.sty and found an existing marker \ord. I was very happy, not having expected a ready-made solution.

I get the fact that it is best to keep “data” and “rendering” appart. But for a user who cannot memorize all those markers it would be helpful to have a summary of “what is this marker” and “how is it being applied” and “where can I (legally) use this”.

舊文章 - 以原文顯示
+1

Note to self, found the below new (to me) website in this thread:

[Link Removed]

https://ubsicap.github.io/usfm/identification/index.html?highlight=rem#rem

舊文章 - 以原文顯示
(934 點) 提出

相關問題

+1
2 個回答 283 次瀏覽
Currently, \rem tags in Paratext projects are not stripped when uploaded to DBL. Private information was being stored ... to use before they upload to DBL? Jonathan+Robie
Jonathan Robie 448 提出 已提問 11月 16, 2020
0
2 個回答 338 次瀏覽
I've been beating my head against this problem, and just found a solution, so am sharing here in case ... might have. Is there documentation somewhere that explains this?
anon150053 286 提出 已提問 2月 22, 2022
0
1 個回答 545 次瀏覽
據我理解,不建議使用 SFM 標記(例如 \rem)將專案筆記直接輸入到實際的經文文本中 我理解最佳方式是使用 PT 提供的專案筆記功能 現在我們有這樣的需求:一位團隊成員通讀了整卷書,並針對回譯(back translation)中出現的 ... 如何最佳地在文本中放置 \rem 暫時性(自訂)標籤 \rem*,以處理將在幾週內解決並視為完全解決的問題
Tim 934 提出 已提問 4月 8, 2022
0
2 個回答 322 次瀏覽
I'm just learning my way around PT8, so this might be a silly question, but: Is the USFM code \rem valid in PT8? If yes, ... I have is v. 2.4. Has that been superseded in PT8?]
Paul 642 提出 已提問 11月 17, 2018
0
1 個回答 234 次瀏覽
非常感謝你,Phil。我會把這些資訊轉達給我的朋友。 請問我的朋友可以在哪裡學習如何被認可為獨立譯者? 再次感謝。
chas 113 提出 已提問 6月 20, 2023
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
They devoted themselves to the apostles’ teaching and to fellowship, to the breaking of bread and to prayer.
Acts 2:42
3,045 個問題
6,005 個回答
5,671 則評論
2,026 位使用者