We should allow the user to customize the subdivisions of their own milestones for display, instead of forcing exactly 50 cell chunks. For example, Luke 1 has 80 verses and so we split it into [1-50 and 51-80]. But [1-38 and 39-80] or [1-45 and 46-80] would be more preferable breaks.
Or, suppose a translator imports an unwieldy .docx document, and it contains logical breaks every 20-60 cells or so. Since we force their pages to be exactly 50 cells each, the divisions are arbitrary, and for a document with hundreds or thousands of cells, this system feels pretty clunky when the user only sees breaks that are meaningless to them.
If we simply let the user edit where we sub-divide their milestones/chapters, this solves the issue. Merely a rendering thing, nothing deeper. We can also go slightly beyond this and allow them to name their subdivisions—this makes the breaks still way more useful to them. Really, they should divide their documents before importing them, in many cases, but if they don't, this will hopefully help life be less painful for them.
Requirements:
- Let the user adjust the start and/or end of the rendering subdivisions in a milestone that is subdivided
- Enforce same subdivisions to be rendered on the source and target
- Make subdivisions nameable
We should allow the user to customize the subdivisions of their own milestones for display, instead of forcing exactly 50 cell chunks. For example, Luke 1 has 80 verses and so we split it into [1-50 and 51-80]. But [1-38 and 39-80] or [1-45 and 46-80] would be more preferable breaks.
Or, suppose a translator imports an unwieldy .docx document, and it contains logical breaks every 20-60 cells or so. Since we force their pages to be exactly 50 cells each, the divisions are arbitrary, and for a document with hundreds or thousands of cells, this system feels pretty clunky when the user only sees breaks that are meaningless to them.
If we simply let the user edit where we sub-divide their milestones/chapters, this solves the issue. Merely a rendering thing, nothing deeper. We can also go slightly beyond this and allow them to name their subdivisions—this makes the breaks still way more useful to them. Really, they should divide their documents before importing them, in many cases, but if they don't, this will hopefully help life be less painful for them.
Requirements: