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

Search the Community

Showing results for tags 'character style'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 8 results

  1. When I create a cross reference with a character style override with the to non-breaking option set to true, the cross-reference still flows to the other line by itself. I have to manually add the character override for non-breaking, which is counter intuitive as I now have to do this manually. Video to illustrate 2023-09-23 14-50-53.mp4 Sorry my OBS settings were suboptimal. Steps to recreate: 1. Create a new text frame and add a line of text 2. Create a second text frame and add text to reference in the cross reference 3. Go back to the first frame, add the cross reference and reference the text in the second frame 4. Create a character style like this: 5. And cross-reference style like this: 6. Notice how, if you resize the text frame, the cross-reference still moves to the second line by itself. This means I have to manually hunt these down and apply a non-break character override to such cross-references, which defeats the purpose of applying a character style override to the cross-reference in the first place.
  2. A bug in Publisher v1 and v2 causes the table of contents (TOC) layout to go berserk when refreshed because it sponges up unrelated character/paragraph styles from the document. During a TOC refresh, the update function superimposes whatever character or paragraph style is used last in the document on top of the actual TOC styles. This should never happen since Publisher uses independent TOC styles to generate a TOC. For example, if I apply a red character style somewhere in the document and then proceed to refresh the TOC, the entire table of contents will turn red. The same goes for paragraph styles. If I apply a numbered list style somewhere in the document and then go to the TOC to reload it, every TOC entry will start with a number. The TOC only sponges up style settings which are undefined in a TOC style (or its ancestor's TOC style) but defined in the last used document style. With undefined settings I mean unchecked settings or [No Change] settings, anything that can inherit a value. So if I explicitly set the base TOC style to use black text, the unrelated red character style can no longer affect my TOC layout. This workaround works but is impractical for documents that use numerous styles. Since any of these could affect the TOC at some point, you'd need to overrule quite a few settings. Luckily, there's a more suitable workaround, albeit a bit silly. Workaround: Make sure nothing in the document is selected. Go to the Text Styles panel. Set the Paragraph and the Character style to [No Style]. Click somewhere in the TOC to make it active. Refresh the TOC from the Table of Contents panel. The TOC now exclusively uses TOC styles. This behaviour must be a bug. I can't think of any reason why this would be a feature. It appears that forum user Loquos experienced the same issue last November, so I'm pretty sure it's not my setup at fault. Steps to reproduce the problem: Create a new document. Place two regular text frames on the page. From the Table of Contents panel, insert a TOC in frame one. Add a few lines in frame two and apply the default Heading 1 style to each. Go to frame one and refresh the TOC. Edit the TOC style 'Base' and disable the tick mark next to the text colour setting (character fill). Type some text in frame two. Add a new character style and set its text colour to red (character fill). Apply the red style to the text you typed in step seven. Update the table of contents in frame one. The new character style colours the contents red, even though it is entirely unrelated to the TOC layout. When I tried to reproduce the bug in a new document, I noticed that even though the Base style for the TOC is based on [No Style], it is far from empty. Almost every setting in the Base style has a default value. This explains a lot. I tend to defenestrate the default styles when I create a new document. My styles only have values for the settings I need. They don't have default values for unused style elements. This likely caused these daft TOC layouts, but that's beside the point. My approach should've worked just as well. After all, a TOC should never sponge up settings from a random document style. It doesn't make sense, but it is what's going on. I'm using macOS 12.6.3 and the latest Affinity Publisher (2.0.4). I always use the Table of Contents panel to update the TOC. I did not try the Preflight panel's TOC update feature. Hardware acceleration does not affect the issue. Neither does it help to unplug all external hardware. The problem exists in both Publisher v1 and v2. It would be great if the Affinity team could look into this peculiar behaviour and hopefully fix it! Thank you!
  3. Hi, I am working on a document where occasionally, the lines are too long to have the cross-reference on the same line. In this case, only the cross-reference moves over to the new line, but I want to last word of the sentence to also be moved over. Is there a way to make sure the cross-reference is a non-breaking character of some sort? I don't want this: But I do want this (without changing the column or text frame size):
  4. Hey everyone, I've been working with Affinity Publisher for quite some time now (actually I'm a day one user) and before that I worked over half a decade with the equivalent of the big A. So, I'd like to think I already have some experience with DTP software. Still, here I am coming back to questions that arise every now and then when working with interdependent Text Styles. (Some things I never quite get used to, heh. 😅) Question: Is there any documentation or overview of the different options (I know, there are a lot) or a section in the FAQ or help file that I missed that helps to explain them and the context/requirements? Just as an example: I am currently stuck and wondering how (and if at all) I can combine a pragraph style with a character style, So if I change the character style, all the associated paragraph styles adapt as well? Thanks for pointing me in the right direction! For those wondering what the heck is he talking about, here's a screenshot of the first tab in the left list – there are many more options:
  5. Hello, so, this was found in AP Beta 1.9.0.829 on MacOSX 10.11.6. Since I am interested in underline options in 1.9, I defined Character Style with underline options, clicked OK and close the Character Style window. Later I tried to make some adjustements, so I double-clicked the Character Syle in the panel, which evoked the Character Style window, but previously defined options weren't there.
  6. Hello Everyone Could anyone help me understand the function of "Alternates" and "Variants" in the Character Style or point me to a Tutorial on how to use? I don't get its purpose yet and I can't find anything useful on the Internet. Thanks a lot! Cheers, Christian
  7. So for example 'Calibri' doesn't support the checkmark character (U+2713), but Publisher automatically substitutes it with another font that supports that glyph -- for me, it is 'MS UI Gothic'. Of course, one may argue that using 'fake glyphs' implicitly is not necessarily the desired way to handle missing characters, but I think it is the expected behavior here. Problem: These unsupported-but-substituted characters temporarily become 'unknown' characters after using the Update Character Style function. Creating the problem: New document Frame Text Tool, text: some text [checkmark character] font: 'Calibri', though the [checkmark character] character implicitly becomes 'MS UI Gothic' Choose a character style (e. g. the built-in 'Emphasis' style) Modify the style of the text (e. g. increasing the font size) Update Character Style This is the result: some text [question-mark-in-a-square character] If I export it to .jpg or .pdf, it remains the same. Workarounds: If I save the file, then close, and reopen it, everything is good again. An easier way: Text menu -> Reapply Text Styles. [Windows 10, Affinity Publisher 1.7.0.399]
  8. Hi, Working on a document converted from PDF, I had some images cause a freeze any time I applied a text wrap to them. Also, I made bulleted lists using a character style on the bullet, with different font, size, color and baseline. The character style doesn't update automatically and the bullet baseline jumps erratically high, like 20 pt when it should be -3-ish. BTW, I managed to get Finnish hyphenation working on a semi-decent level using the attached Public Domain library. The library makes Publisher crash as is, but when you remove the first charset line, it works just fine. The library is not perfect, but it's a good start. Should you be able to tap into the OS X library, that would be just smooth too, but I understand it's not as simple as one would like to think . Sorry to include multiple topics in one post, bit of in a hurry here and wanted to contribute… Asukkaan_opas_01_2019.afpub fi_FI.zip
×
×
  • 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.