Saya memiliki proyek dengan stylesheet custom.sty yang tampaknya berisi banyak hal lama, termasuk bagian ini:
...
\Marker pc
\OccursUnder mt3
\Marker b
\OccursUnder mt3
# 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.
...
Dalam proyek ini, mereka menggunakan penanda \b di Mazmur untuk menandai pemisahan bagian, tetapi semuanya muncul berwarna merah, sebagai kesalahan:

Saya asumsikan ini karena stylesheet kustom ini menyatakan bahwa \b hanya terjadi di bawah \mt3. Saya membayangkan jika saya menghapus definisi penanda \b dari custom.sty, itu akan menyelesaikan masalah tersebut.
Tetapi saya bertanya-tanya apa hal lain yang ada di stylesheet ini dari zaman dahulu (upgrade ke Paratext 8.0 disebutkan…). Jika tim ini tidak benar-benar memiliki kebutuhan gaya kustom, bisakah saya hanya menghapus file custom.sty tersebut, dan membuatnya kembali ke gaya USFM standar? Itu mungkin akan lebih melayani mereka. Apakah ada persyaratan atau jebakan yang harus saya ketahui? Perlu menjadi administrator untuk dapat mengirim perubahan itu?
I have a project with a custom.sty stylesheet that seems to have lots of old stuff in it, including this section:
...
\Marker pc
\OccursUnder mt3
\Marker b
\OccursUnder mt3
# 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.
...
In this project, they use \b markers in Psalms to mark section breaks, but they all appear in red, as errors:

I assume this is because this custom stylesheet says that \b only occurs under \mt3. I imagine if I take the \b marker definition out of custom.sty, that will solve that problem.
But I’m wondering what other stuff is in this stylesheet from ancient days (the upgrade to Paratext 8.0 is mentioned…). If this team doesn’t really have any custom style needs, can I just delete that custom.sty file, and make it revert to standard USFM styles? That probably would serve them better. Are there any requirements or gotchas that I should know about? Need to be administrator to be able to send that change?
Diterjemahkan secara otomatis dari English