USFM (Customized)

Question

In P8 (Project Properties and Settings/Advanced) I see the word (customized) after the USFM.sty (and any other style chosen.) I did not customize USFM or other styles, and I cannot get rid of this customization whatever it is.
For instance, I do not get the proper indent for \q2 in Paratext 8 even if I use the same usfm.sty as in P7 where it does work as it should. When I look inside the usfm.sty, the indents are stated correctly, but it is not implemented in my text. I see no difference between q1 and q2 in spite of what is in the USFM.sty.
Any explanation for this or how to get rid of the (customized)?
Also, does it matter whether the sty file is in the My Paratext 8 Projects folder or the individual subfolders?

Answer 1

Iver+Larsen, could you give us the name of the project (assuming it’s not sensitive) so that we can check the custom.sty creation during the migration of that project.

Comments

They are Kpz, KpzBt and SpyKup.

---

I checked the Kpz project and the stylesheet it S/R’s is like the one created by 8.0. I’m not sure why it looks correct on your machine in PT7 - maybe another project overwrote it with one that more-closely resembles the default usfm.sty file.

So the good news is that the PT8 migration code seems to be working properly. The bad news is that it looks like that project might have gotten into a fighting match with another project at some point.

---

I want to say thanks to the development team for this fix. I’ve been frustrated for years by this war between different projects. It’s been frustratingly hard to try to save correct versions of usfm.sty back into the folder and hope it propagated out to the projects; it just never seems to have worked.

Also, thanks for the explanation of how PT8 deals with discrepancies during the migration process.

---

You are right that a few months ago somebody changed the USFM style in one of my many projects, but that was solved after I corrected my copy and did S/R.
It is good that you have put a stop to that kind of thing.
My question is more about how USFM and custom files interact. My recent problem was not connected to differences in the USFM in P7 and P8, but how the custom file interacts with the USFM. I could not find any difference between my P7 USFM and P8 USFM.
I have not been able to find an explanation of this interaction in the Helps, but it appears that in P7, the USFM was placed in the main folder and a custom file placed in that same folder would not take effect until it was moved into a subfolder for a particular project. In my P7 folder the USFM was in the main folder, not the project subfolders and there was a custom file in the main folder, but there were none in the individual folders. During the migration it appears that the USFM was copied to individual project folders and a custom file was also added to individual folders. That was the cause of my problem. A project folder which had no custom file before suddenly had one, and I assume this explains why there was no (Customized) in P7, but there was in P8 (until I deleted the custom.sty in those subfolders.)
Does this make sense?

---

Here is how the stylesheet hierarchy works:

1. usfm.sty (found in the My Paratext Projects or My Paratext 8 Projects folder)
2. custom.sty (found in an individual project’s folder). This overrides settings made in 1)
3. PrintDraft-mods.sty (found in the PrintDraft folder of an individual project). This overrides settings made in 1) and 2) and changes the output of PrintDraft, but doesn’t change the way things appear within Paratext itself.

You should never, ever, edit usfm.sty, and the new Paratext 8 system of doing send/receive will make sure you don’t.
You should usually edit custom.sty, and PrintDraft-mods.sty only in rare occasions.

Iver+Larsen, you are correct when you said that a custom.sty file put into the main My Paratext Projects folder will not affect things. It needs to be inside an individual project folder.

As to why you have a custom.sty file in Paratext 8, I’m pretty sure that’s because this: [quote=“anon291708, post:5, topic:1544”]
So, during migration, Paratext will take the stylesheet used by the project in PT7 and compare it to the usfm.sty file that ships with PT8. Any differences that are found are put into a custom.sty file for that project.
[/quote]
and is completely unrelated to the fact that you had a custom.sty file in your My Paratext Projects root folder prior to migration

Answer 2

When you see “Customized” it indicates that there is a custom.sty file in the project directory. I’m thinking that the migration process may create a custom.sty automatically. Check that file for any changes to the \q2.

Comments

Thanks. Deleting the custom.sty in the folders for each project solved the problem. In one of my projects there was already a custom.sty which had been renamed as custom.sty.bak, apparently by the migration process. So I deleted the new custom.sty and restored the bak file to be custom.sty.

---

I have a custom.sty file in my project folder, but there is still no (customized) showing up after usfm.sty under Project Properties and Settings > Advanced.

---

For information purposes:
In PT7, the usfm.sty file was shared with every project (as it is in PT8). However, many projects made custom modifications to usfm.sty which then got S/R’d to other projects. This created nightmares when different projects made different changes to the usfm.sty file - they would start fighting over which one would win.

In PT8, we decided to no longer have non-custom stylesheets be S/R’d. However, because projects had made changes to their stylesheets, we had to make sure those changes were not lost. So, during migration, Paratext will take the stylesheet used by the project in PT7 and compare it to the usfm.sty file that ships with PT8. Any differences that are found are put into a custom.sty file for that project. This is why some projects are seeing a custom.sty file in their project when they didn’t have one before.

(Note that any existing PT7 custom.sty file is merged into this new one - which is why the one project had a custom.sty.bak file.)

However, because of the problem in PT7 where any project’s custom modifications to usfm.sty could be propagated to other projects unintentionally, this can create a custom.sty for a project in PT8 that is not what the project intended.

Answer 3

Thanks.
One more question. Should the USFM only be in the main projects folder and not in the individual projects? If so, why did the migration put them in the individual folders as well as in the main folder?

Comments

Someone else will have to answer that.

Personally, I don’t see any usfm.sty files inside of individual project folders. I do see usfm.sty.bak files, which are presumably what the usfm.sty file in the PT7 main folder was like at the time I imported the PT8 projects.

The fact that I don’t have usfm.sty files inside individual projects makes me assume that PT is reading the usfm.sty in the main folder and ignoring any in individual folders, but that’s just a guess.

---

mnjames:

The fact that I don’t have usfm.sty files inside individual projects makes me assume that PT is reading the usfm.sty in the main folder and ignoring any in individual folders, but that’s just a guess.

The usfm.sty file used to compare against the one that ships with PT8 is the one that gets S/R’d with the PT7 project (located inside the gather directory of the PT7 project).

Most of the time, this matches the file in the root directory, but depending on when S/R’s on projects were done and which projects had conflicting usfm.sty files, they can get out-of-sync. Since the one in the PT7 project’s directory is the one that others would get if they S/R’d the project, it was chosen to be the one used during a migration.

I’m guessing this is why a custom.sty file was created in @Iver+Larsen’s case even though he can’t find any difference between the PT7 root usfm.sty file and the one in PT8.

Answer 4

I had different usfm.sty files in my My Paratext Projects and My Paratext 8 Projects folders before migration, as well as a custom.sty file in my project folder under My Paratext Projects. After migrating our project, I got a custom.sty file in the project folder under My Paratext 8 Projects. Inspecting it, I can confirm that it contains a combination of my old custom.sty file as well as the differences between my Paratext 7 and Paratext 8 usfm.sty files. Opening it, I also found it had this explanation at the top:

Custom style file created by the upgrade to Paratext 8.0. It is based upon the original style files used by your project. These files have been removed, but a backup of the files has been saved to usfm.sty.bak and custom.sty.bak.