Jump to content


  • Content count

  • Joined

  • Last visited

About SirPL

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. SirPL

    Publisher: Superscript

    That's a good point and needs to be unified. Even if it's counterintuitive, the OpenType specification does not restrict enabling super- and subscript at the same time. Each OpenType font has a list of features which order is determined by its author. The specification states that features should be applied one by one according to the order. An OpenType feature can be applied to a whole paragraph, so if some font provides superior variant only for digits and inferior variant only for letters you may want to turn both features on (for some unknown reason ). Also, for those specific features, OpenType specification says clearly: To sum up: using both features is counterintuitive, but not forbidden. According to the specification superior variants main purpose are footnote markers (besides digits also: * † ‡ § ‖) and abbreviations, i.e. latin Mˢˢʳ or french ones:
  2. SirPL

    Publisher: Superscript

    Fully agree - I apparently did not get the point of your previous post. My apologizes. To compare the terminology used elsewhere: Application Position superscript Position subscript OpenType superscript OpenType subscript InDesign Superscript Subscript Superscript/Superior Subscript/Inferior QuarkXPress Superscript Subscript OpenType > Position > Superscript OpenType > Position > Subscript Scribus Superscript Subscript Superscript (sups) Subscript (subs) So maybe the typography features can be renamed to Superior variants and Inferior variants?
  3. So as for now Published does not support allonges (various size pages) in facing pages mode. The rootcause of your problem is more or less the same as that one:
  4. Can you prepare a new document with some dummy content that reflects your problem? I am not sure if I understand it correctly - such document would definitely help.
  5. SirPL

    Publisher: Superscript

    Edit: I complelety edited my reply as it sounded rude and that definitely wasn't my intention. I feel the sections clearly distinguish those two features - Positioning and Typography. Publisher's help tries to distinguish between those two, but I must admit - the explanation isn't informative.
  6. SirPL

    Publisher: Superscript

    The Super- and Subscript buttons turn on typography features that are provided by the font you are using. For what I found if proper OpenType features (namely subs and sups) are not supported then Unicode defined super/subscript glyphs are used. In case of Arial there's only one superscript letter defined - n (Unicode glyph U+207F; for other glyph code points checkout out this post). Hence it's the only modified character. The same applies to subscript. What you want to do is to use superscript positioning instead: Note: if your font supports ordinal suffix (ordn OpenType feature), you may enable it with the button:
  7. SirPL

    Buggy Hyphenation

    You can find the correct folder location In Publisher's Edit > Preferences > Tools > Browse... in the 'Additional dictionary folder' section
  8. Hey, Serif team! Do you have plan to get such improvement implemented or you find the current approach sufficient and don't see a point in reworking Text Styles in the (near) future?
  9. Guys, any chance to get this improved in the near future? It's so small thing but annoys so much...
  10. As you probably know Publisher supports hunspell dictionaries, so you are not bound by Serif at any point. You only need to find a dictionary (or more specific - hyphenation patterns) that work with the software. I had similar problem with polish and I finally managed to find dictionary which works well, but I can't recall where I took it from. You may try to google for: site:github.com hyph_cs_CZ.dic
  11. I checked it with polish text and can't reproduce it. I suppose it may be related to the czech (am I right?) hyphenation dictionary you're using. Could you please mark the text language as some other and check if the problem exists? To do so select the faulty part of text (s + <non-breaking space> + the following letters) and in Character sidebar menu switch Language to i.e. English.
  12. As far as I know not yet. The release does not mean the product has all requested features -- it only means the currently supported features are stable. And that they would like to finally make money out of this 2 years development (if not longer).
  13. SirPL

    Some pages don't resize when changing all of them

    Two requests: May you please explain step-by-step how you resize the pages? What do you mean by "only some resize"? It's hard to help when we have so limited information. Please be more specific. Second thing: Please rename this thread to better reflect your problem.
  14. I found that Publisher has problem with certain swash fonts when Scale for descenders is enabled. APub Steps to reproduce: Detach all styles (for keeping minimal number of styles; this step is not required) Create a new character style (let's call it Drop Cap Style): Font family: Gabriola (one of Windows fonts) Variants: Stylistic Set 06 set to 1 (other set to 0) Create a new paragraph style (let's call it Drop Cap): Drop Caps: Enabled Height in lines: 3 Scale for descenders: checked Style: Drop Cap Style Now type a few lines of text starting with lowercase g. Result: Only two lines of the text are indented due to drop cap, despite of setting height in lines to 3. The same issue can be observed in Yana regular font with Stylistic Set 03 enabled, when J is a drop cap letter.
  15. Hi I found an inconsistency in the interface. Let's say I created two paragraph styles: Parent and Child which inherits from the Parent. In Parent I set "Keep with next lines" to 2. Now I am unable to set the value of the Child to 0 - Publisher allows to enter either minimum value of 1 or [No change] (= inherited 2). Windows 10, Publisher v1.7.0.283