Skip to content

Optimize chapter listing in quote denormalization summary remark #852

@mmartin9684-sil

Description

@mmartin9684-sil

When quotation denormalization is applied to a draft, a remark is added to the top of the draft to record that this postprocessing step was performed on the draft. The remark includes a list of the chapters that successfully had quotation marks denormalized. The chapter listing works well for smaller books, but for larger books it can be hard for users to interpret it correctly. For instance, when drafting Psalms with 150 chapters, it might be hard for the user to easily recognize chapters where the quotation marks were not denormalized successfully.

\rem Quotation marks in the following chapters have been automatically denormalized after translation: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126.

Some suggested improvements:

  • Could we use chapter range notation (e.g., "1-150" instead of "1, 2, 3, ... 150") to refer to the chapters that were / were not successfully denormalized?
  • With likely future changes related to partial book drafting, should the remark explicitly mention the chapters that were processed, and then mention the chapters that were not successfully denormalized? For example: "Quotation mark denormalization was applied to chapters 1-150. The following chapters could not be successfully denormalized: 1, 3-5, 10."

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestpipeline 6: inferIssue related to using a trained model to translate.

Projects

Status

🔖 Ready

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions