Jump to content
You must now use your email address to sign in [click for more info] ×

Seneca

Members
  • Posts

    1,319
  • Joined

  • Last visited

Posts posted by Seneca

  1. On 9/15/2018 at 11:54 AM, Peter Kahrel said:

    In my experience, readers just get annoyed by having to go to the end of the book (or worse, to the end of the chapter in multi-authored volumes). 

    Exactly. I don't want to scout for footnotes somewhere else in the book, particularly, where there are many of them.

    Obviously, with a very few notes in the document placing them at the back of the chapter or at the end the book is acceptable and oftentimes desirable.

    And I agree with Peter. We need greater flexibility than in indesign.

  2. 12 minutes ago, musiberti said:

    I am sure that Affinity will deliver many features until the final release.

    When the first Publisher beta was released the Affinity team has said that it might be useful to some and it might not to others.
    Deep down you want this product to succeed and it's nice to see people willing it to be the top dog in publishing.

    Whether it's called Alpha or Beta it's really immaterial in this case. The product is out and people have responded.
    Some find it great as it is, others, involved in larger product find it wanting. 

    There are two outcomes here:
    1. The product fails to attract larger user base
    2. The products thrives

    Time will tell. But thankfully, there are now more options in DTP to choose from than before. :)

    And one more thing. The developers do hear us users and respond quite willingly in these forums.

  3. 15 minutes ago, robinp said:

    I just can’t see how or why  having both would be desirable.

    You are absolutely right.

    You still need to derive either from the group or from a style above.

    I think about it as a tool to organise my styles and commonalities within my style hierarchy.

    Other people may elect to completely ignore that feature and that's absolutely fine too.

    You have options there. If it doesn't fit your needs organise your styles the way you want.

    As Dave said, all styles are flattened anyway.

  4. 10 hours ago, Old Bruce said:

    Just so I am straight on this what you want is something like the second image from the text in the third image?

    Yes, sir.

    Traditionally this has been done with paragraph returns. And that's worked well. For some people there is no issue there.
    But there must be a better way. Keep the paragraphs together, which are achieved by soft returns,  and get the sense lines rules.

    Soft returns will keep indenting all the lines underneath as per my 4th picture. That's what they were designed to do.

    Of course, a script could automate that. Say replace soft returns to paragraph returns, etc.

    But I think this should be achievable without resorting to scripting.

  5. 8 minutes ago, robinp said:

    The question was what and how this differs from a ‘group style’. Anyone know?

    OK. Group Style would be in charge of holding information that pertains to a number of styles. 

    For example you have a number of Text styles that need to have common information. In this case you would want to create a group to host that information there. 

    Titles, subtitles, headings may need to have something in common so you group them in Headings Group to keep all that commonality there.

    But deriving really means specialising one style directly from a style one above the hierarchy.

  6. Hi Fixx,

    My mind wandered in that direction as well. I even thought that we should have another nonprinting character to account for that.

    1. Paragraph Return

    2. Soft Return

    3. Line Continuation Return (or something along those lines)

    Problem is that this new character would need do be adopted by Word processors, etc. and that won't happen.

    That's why I thought Publisher could augment soft returns to understand one more trick. :)

  7. 1 hour ago, robinp said:

    What is the purpose of this over the 'Based on' setting also described by others above?

    Well, Based on means that the style you want to create is more specific.

    Example: Body Text. This style is applied to the majority of your text. But there are places in your document that require space after in your paragraphs.

    So you define this new style based on Body Text except that you need to add space after, say 6pts to your new style.

    You don't need to create this new style with all the information that comes from your Body Text again. Basically you derive all that information and add some more. You specialise it.

    Styles work from General to more specific. Styles above the hierarchy are more general, because they contain the majority of the styling information you need.

  8. 1 hour ago, Petar Petrenko said:

    When adding/deleting text, the chapter pages move forward or backward but not the chapter master page.

    That's something that was at the back of my mind too. I think I saw a post about that on the Designer forum when discussing future Publisher a long time ago.

    This would really be great and would solve the problem you've raised gracefully.

    Big +1 from me.

  9. 8 minutes ago, Tom Schülke said:

    are these Styles available only in the current document , and if not, can i save them ore store them alswhere, ore can i import them from other documentes ?

    Hi Tom,

    You can't export styles at the moment but you can import them from other Publisher documents. Whether you store them separately or them being part of a Template document is immaterial in my view. A file is a file is a file. :)

    The way styles work in Publisher is a bit different. You don't have folders but you can organise them hierarchically by basing one style on another. You can also check the burger menu next to the Styles Heading and check Show Hierarchical. That might go some way of alleviating that issue.

     

  10. 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:

    1543839697_Screenshot2018-09-13at16_18_26.thumb.png.fa80a642fe3eae7eefd82a95d2cd6b26.png

     

    When this text needs to go into 2 columns it needs to look like this:

    268784930_Screenshot2018-09-13at16_20_20.thumb.png.e981d82aa42a773d8f70f4590c37ba00.png

    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:

    1188208870_Screenshot2018-09-13at16_25_12.thumb.png.af5afbed4119b3383bb94dbbbd344880.png

    Problem arises when one wants to fit this text into 2 columns:

    515013093_Screenshot2018-09-13at16_26_13.thumb.png.1658b061566430545565aabfc95667d1.png

    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:

    684777618_Screenshot2018-09-13at16_35_55.thumb.png.91415236a91a15ea6c2305b5a3d3b96e.png

    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. :)

  11. 1 minute ago, walt.farrell said:

    Publisher already allows pages of different sizes,

    Thanks Walt.farrell, I forgot about that.

    What I had mostly in mind was working on a book divided into chapters, and each chapter on a separate file.
    Once done it would be really great to be able to put the book together (in anticipation for the Book facility in Publisher).

    But like I said earlier, this should be a great feature irrespective whether the Book facility is there or not.

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.