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

Raul Ciannella

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by Raul Ciannella

  1. 3 hours ago, MikeTO said:

    I think it's the same bug I reported just recently so I've added it to that thread and asked Serif.

     

    Thank you. It might also be caused by Affinity thinking the apostrophe is just another valid character to apply hyphenation to. The fact the problem is solved by changing prefix from 2 to 3 characters might imply that. Moreover, languages like Catalan have special phonetic graphic sign like the "l·l" (a double L with a dot in the middle, as in the word "il·lustració"). When hyphened, Affinity will wrongly separate the "l·" from the other "l". It could also be a fault in the Catalan Hyphenation dictionary. 

  2. 41 minutes ago, MikeTO said:

    I'm unable to duplicate this. Could you please share a test document? I assume you have Character > Language > Spelling set to Català.

    How are you typing that apostrophe?

    Could you select the apostrophe and press Ctrl+U and then tell us what unicode value it is?

    Here's a document I created which breaks properly with language set to Català.

    test-catala.afpub

    Good luck

    OK, I modified a little your doc and placed the apostrophe example in the first line.

    test-catala.afpub

  3. Hi everybody.

    Not related to the previous topic, but regarding the same file. I'm doing a galley proofreading of the book and noticed that Publisher often leaves isolated letters (or letters with an apostrophe, hanging at the end of the line (as in the example) which is not really right. Is there an automatic way I can tell Publisher not to separate the letter+apostrophe with the following word? I created a "do not divide" character style but still I have to go word by word.

    Thank you.

     

     

    Screenshot 2024-03-28 at 17.44.00.png

  4. 13 minutes ago, kenmcd said:

    The good news is it looks like you have the OpenType feature Scientific Inferiors (sinf) enabled on the Index text.
    So turn that Off in the Typography Panel and you should be fine.

    2024-03-21_12-56-43.thumb.gif.f5b385e6a3f464c30408ed8e0122e20a.gif

    sinf.thumb.png.73988a6a56f44134085591be35f2ef3e.png

     

    Pensum Pro is an advanced text font - with lots of OpenType features.
    They linked both Subscripts (subs) and Scientific Inferiors (sinf) to a full set of figures, currency signs, lowercase a-z, punctuation, dashes, etc. (61 glyphs).

    The bad news is - the names are even more of a mess than I initially thought (looked closer today).
    And if you are using the OTF fonts, they could be even worse (more name fields).

    I only installed the Regular, RegularItalic, and Bold.
    Messed-up names fields can result in the wrong fonts in a PDF.
    So test Export to PDF now.
    If you have any issues, please come back.

     

    That's great, thank you. I don't know how the scientific inferior got enabled at all! But you're right about the fonts, Affinity recognizes Pensum Pro as regular/bold as one font and the italic as a separate font. I did some pdf export tests and they look ok. I really like the font, pity it causes all those issues.

    Thanks again, if something comes up I'll let you know.

  5. 2 minutes ago, kenmcd said:

    If you can disable the Italic, you can try that.
    Shut down Affinity first (so the font cache will be rebuilt when opened).
    Then disable or un-install the Italic.
    Then restart Affinity and see if the TOC is OK.
    If the TOC is OK, then a name conflict is probably the issue.
    If the TOC is not OK, then my guess was apparently wrong.

    The Pensum Pro has "Regular Italic" in the Typographic Style name.
    Usually this is just "Italic".
    This may be confusing Affinity.
    And both the Full Font Name and the PostScript Name fields also include "Regular" in them.
    Also may confuse Affinity.
    When Affinity gets confused, odd things happen.

    I could test it locally with the local fonts with a test document.
    And I could test-modify the Italic and see if the issue goes away.

    You're probably right. The thing is that now I've basically finished the lay-out and I'm afraid if I disable the italic it will mess with the body as well, which works fine at the moment 

  6. Hi, 

    I'm currently working on a book. I've rented a font (Pensum) from Fontstand and using it with Affinity Publisher v2 (Mac). Everything works fine with titles and body paragraph styles, but when I tried to use it with the Table of Content styles it doesn't recognize the font. The name is there but the result is weird and misplaced characters from another font. If I change to an installed font (say Palatino) everything is fine again. Just wanted to know if ti was a bug or I was doing something wrong.

     

    Thank you, 

    Raul.

×
×
  • 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.