0 票
1.2k 次瀏覽

We’ve noticed some formatting problems in PrintDraft around \b and \q1 markers. For example, with the following text:

\v 7 Nayi mǝnafǝkkaso, awo Nawi Ishayaye kǝlandon wuljǝnadǝ jire. Tiye:
\b
\q1
\v 8 “Jama adǝ cilan wuro daraja sadi,
\q1 amma karwunjan nanin kuruwujana.
\q1
\v 9 De sullo wua ambǝnsagai,

we get the following output in PrintDraft:

image

Note the extra indent at the beginning of the first line of the quote. If we remove the \b marker, the extra indent goes away, but of course so does the space before the quote:

image

I’ve played a bit with the indent settings, and if I keep the standard indents:

\Marker q1
\LeftMargin 1.25
\FirstLineIndent -1 # 1/4 inch indent, 1 inch wrap

we still have this indent problem. But if I make the first line start at 0.4 inches or later:

\Marker q1
\LeftMargin 1.25
\FirstLineIndent -.85 # 0.4 inch indent, 0.85 inch wrap

then the problem seems to go away:

image

I’ve played quite a bit with the settings for the \b marker, to make it look a lot more like a plain \p marker, but that doesn’t seem to help.

I have this gut feel that there is something simple I’m missing, but haven’t come up with it yet. Any suggestions?

舊文章 - 以原文顯示
Paratext 由 (1.4k 點) 提出 | 1.2k 次瀏覽

7 個回答

0 票
最佳回答

When a migration happens on a project, the stylesheet used by the project is compared with the 8.0 usfm.sty file and any differences are put into the project’s custom.sty file. This is done because stylesheets were S/R’d in PT7 and there wasn’t any way to know what customizations a project might have done to their usfm.sty file. In your case, because you had an existing custom.sty file, the changes were merged into your existing file. Your file size was probably much bigger because your stylesheet must have differed a lot.

There should be a custom.sty.bak file containing the original file contents on the machine that did the migration. If you want to just go back to only overriding those settings, you can delete the custom.sty file created by the migration and go back to using the one used in PT7 (the format of the file is the same).

If you want to just take the default usfm.sty file, you can just remove the custom.sty file created by the migration.

舊文章 - 以原文顯示
由 [Expert]
(16.7k 點) 提出

已重新顯示
0 票

jeffh - what version of PT are you doing this in? I’m using 8.0.100.50 and get the results I would expect. What file are you modifying? Any changes for the Print Draft should be in PrintDraft-mods.sty

In my copy of the file there is no listing for \b so I’m assuming it gets handled by the default USFM.sty. As a test you might make sure your USFM.sty. You might remove any custom.sty you are using and then remove any PrintDraft-mods.sty and let the Print Draft recreate that file.

舊文章 - 以原文顯示
由 [Expert]
(10.0k 點) 提出
0 票

I’m using the latest Paratext .100.50, and I loaded the file that shows the error into a test project, using the standard usfm.sty stylesheet, and having PrintDraft create the -mods.sty file from scratch (so standard there as well).

I sent my test file (the book of Matthew in a language of Niger) to anon848905, and he ran a similar test and saw the same problems. This problem doesn’t show up, however, in all of the places that a \q1 block is surrounded by \b markers. So maybe there is some specific combination of markers that causes the problem? But none of my hypotheses so far have panned out.

I have now reported an error from within PT8, but if someone else wants to see that book of Matthew that shows the error to attempt to solve this reproducible problem, let me know.

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

I see the issue in the test project you submitted. If this helps, I don’t see the extra indenting if I save to RTF, nor do I see it if I change the \q1 markers to \q2.

舊文章 - 以原文顯示

Just a thought, I know \q
equates to \q1. But does dropping the 1 from the marker make
any difference?

舊文章 - 以原文顯示

\q has extra indent problem on first line, just like \q1.

舊文章 - 以原文顯示
0 票

Note that the problem goes away with \q2 because the indent is larger. If I increase the indent on \q1 the problem also “goes away”. In my playing around I think I saw that if the first line is indented 0.4 inches or more from the margin, then I don’t see the occasional extra indent on the first \q1 line after the \b.

舊文章 - 以原文顯示
由 (1.4k 點) 提出
0 票

I think this is somewhat related to this thread on PrintDraft doing strange things in PT8…

I’ve just spent an hour comparing all the settings files used with PrintDraft in PT7.6 and PT8.0
Hopefully my hour of pain will prevent someone else having to spend that much time searching for clues.

For some (unknown) reason, the PDFs were coming out great in 7.6. but had minor issues in 8.0 (wrong fonts on verse numbers, strange spacing on \s lines, etc.). I had almost given up when I noticed that one of the PrintDraft settings files calls the custom.sty file (from the main project folder, not from the PrintDraft folder).
My old (7.6) file was just 3kb, but the new (8.0) file was a massive 17kb - so I guessed something in there was causing the trouble. And yes, as soon as I swapped one file out for the other, I was finally able to create a “perfect” PDF in PT8.0

When I look at the PT8 version of custom.sty, there are a load of extra markers with additional “occurs under” settings. Presumably this is something related to the enhanced checks in PT8, but it seems to be tripping up PrintDraft.

Has anyone else come across this? What is the solution? I have tried “blending” the two files, but still have trouble with a faulty PDF. For now, the only way to get a successful PDF is to put the old/short custom.sty file back.

舊文章 - 以原文顯示
由 (3.2k 點) 提出
已重新顯示
0 票

Just to say that I don’t think Mark’s issue is the same problem that I’m having. My project is just using the standard usfm.sty file. There is a custom.sty file in the My Paratext 8 Projects root, but it is small, just has some color definitions, and I don’t see reference to it anywhere in PrintDraft.

But I do still have this problem! If I export to RTF, it appears fine. If I set the View in PT8 to Preview or Formatted, it appears fine. But if I PrintDraft, XeTeX produces a PDF where certain \q1’s that show up after a \b have too much indent. Is there anyone else who might be able to help?

舊文章 - 以原文顯示
由 (1.4k 點) 提出
0 票

Just in case anyone has this problem again… On the XeTeX list I found out that putting an extra blank \p before the \b seems to make it behave. Not pretty to have that in Paratext, but if you are doing any pre-processing of your texts before you typeset them, you might be able to add them there.

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

相關問題

0 票
5 個回答 1.1k 次瀏覽
我們在腳註中使用單引號來表示單字的意義 例如: ... \ft "Messiah" in Hebrew means 'Anointed One'. \f* 當我們執行引號檢查(Quotation check)時,它會將這些識別為引號中的引號或引號中的引號中 ... 引號中的引號 ' 引號 必須在以下位置使用延續符號:p p/q1 b/q1
anon469793 155 提出 已提問 1月 29, 2020
0 票
1 個回答 138 次瀏覽
我發現 v7(至少)有一個錯誤,導致無法將引號(斜體)格式化為耶穌的話(紅色)。但我現在在 v9.5 中也无法做到這一點。我嘗試了所有順序的標記,但似乎無法讓一個引號同時也是耶穌的話。我做錯什麼了嗎?這是一個功能還是一個錯誤?有變通方法嗎?
ASmith 171 提出 已提問 7月 10, 2025
0 票
1 個回答 152 次瀏覽
我發現早期版本(至少是 v7)的 PT 中有一個錯誤,導致耶穌的話標記內的引文無法顯示顏色。然而,我在 v9.5 中似乎無法使其正常工作。我嘗試將 wj 標記放在 qt 標記內部和外部,但兩者都不起作用。看來我只能得到引文(斜體)或耶穌的話(紅色),無法同時顯示兩者。有人能幫忙嗎?
ASmith 171 提出 已提問 7月 10, 2025
0 票
2 個回答 577 次瀏覽
當引文包含其他標記(例如 \pg…pg*)時,使用 \qt 會收到錯誤訊息。這是否表示 \qt 不能與其他標記一起使用?這實在令人失望。有沒有辦法規避這個問題?這個錯誤的目的是什麼?
Clear7419 251 提出 已提問 9月 14, 2022
0 票
2 個回答 462 次瀏覽
I'm having a problem with quotation rules where when there is an OT quote embedded in someone's speech. The following is ... to implement that I still couldn't get things to work.
fhardison8588 111 提出 已提問 1月 26, 2022
Welcome to Support Bible, where you can ask questions and receive answers from other members of the community.
Dear friends, since God so loved us, we also ought to love one another.
1 John 4:11
3,082 個問題
6,049 個回答
5,711 則評論
2,048 位使用者