PrintDraft line break and quote indent problem

Question

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:

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:

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:

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?

Answer 1

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.

Answer 2

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.

Screenshot 2018-03-09 08.09.23.png1270×980 167 KB

Answer 3

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.

Comments

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.

Answer 4

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.

Answer 5

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.

Answer 6

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?

Answer 7

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.