Search the Community

Ive been editing Liturgical Texts for as long as I remember and one issues that has not be solved adequately (that I know of) is sense lines. Let me explain what I mean. Liturgical texts are usually paragraphs that have been split into independent lines for better legibility. One can also think of poetry here, which liturgical texts are really part of. Example follows: When this text needs to go into 2 columns it needs to look like this: As you can see longer lines need to wrap underneath the top lines to emphasise the fact that this is just a continuation of the previous line. This is what's called sense line. However, it seems to me that it's really wrong to divide this text into separate paragraphs by inserting paragraph returns after each line. This text is really one paragraph that was divided into lines for better legibility. In fact, there is no full stop after each line. What you get is a comma and the next lines starts with a small letter. This is horrible when one spell-checks this text because each line gets flagged as error. (In some cases/programs can instruct spell-checker to ignore that). What should be really possible is to have each line separated by a soft returns to emphasise the fact that all these lines are part of one paragraph. And indeed this is possible today: Problem arises when one wants to fit this text into 2 columns: As is clearly seen from he picture above the sense lines have been lost. There is no way of representing these lines as sense lines when soft returns are used as end of lines. Indeed, one can say that this is precicely how soft returns should work. What I would love to see though is to have an option to instruct Publisher to treat soft returns as paragraph returns. What should be possible is to have this: To me this picture communicates very clearly that we are dealing with paragraphs and that these paragraph still obey sense line rules. I wonder how other members of this community have been dealing with this and whether it's worthwhile for the Affinity Team to take this on. Or is this just an edge case that's not worth the bother. I would love to have Treat soft returns as paragraph returns tick mark option when defining styles in Publisher to remedy this. That would really be awesome and would solve one of the few outstanding issues in publishing I've had for years.