When a book draft is generated from a source translation that uses verse splits, the verse splits will also be present in the draft. If the draft is added to a Paratext project, the custom.vrs file for this project needs to be updated with information about the verse splits in the book draft, so that the project doesn't fail Paratext Basic Checks.
It's not likely that there's a way to automatically update the custom.vrs when the draft is generated, especially since not all drafts get added to a project, and there are different workflows that involve adding the draft to various projects. But it would be helpful to flag this potential issue for users. Some possibilities include:
- Warning message from the experiment / translate script about the verse splits.
- Remark in the draft about the verse splits.
- Auto-generating a delta custom.vrs with the changes that need to be made if the draft is added to a project.
When a book draft is generated from a source translation that uses verse splits, the verse splits will also be present in the draft. If the draft is added to a Paratext project, the custom.vrs file for this project needs to be updated with information about the verse splits in the book draft, so that the project doesn't fail Paratext Basic Checks.
It's not likely that there's a way to automatically update the custom.vrs when the draft is generated, especially since not all drafts get added to a project, and there are different workflows that involve adding the draft to various projects. But it would be helpful to flag this potential issue for users. Some possibilities include: