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

big smile

Members
  • Posts

    325
  • Joined

  • Last visited

Reputation Activity

  1. Like
    big smile got a reaction from bures in Canva   
    A big thumbs up to affinity for pledging to offer perpetual licenses at reasonable prices. It's pleasing that they are aware of customer concerns.
     
    Especially the perpetual licenses at a reasonable price part. Corel and Quark offer perpetual licenses, but they aren't reasonable. You still need a yearly maintenance subscription to use a lot of features or get upgrade pricing.  Their perpetual licenses are really designed to push people into subscription. 
     
    Does the Affinity Pledges make me feel better about this buy out? No. Bottom line: Canva answers to investors. And investors love subscriptions. Down the road, I could see Canva rebranding Affinity as the "Canva Pro" range to get around the pledge for perpetual licenses.
     
    I really wish Serif could have done their own IPO to remain independent. Or had been purchased by someone like Microsoft who have a (fairly) good (modern) track record for offering fairly priced perpetual licenses. I am happy that the Affinity team got the financial success they deserved. But I'm deeply heartbroken that my favorite app suite is in the hands of a company whose bread and butter is subscription. 
  2. Like
    big smile got a reaction from Xzenor in Canva   
    Genuinely heart broken about this. I know I shouldn't jump to conclusions. But every time one of my favorite independent companies gets acquired by a bigger player, it never ends well. 
    I so hope that Affinity continues to offer perpetual licenses at a reasonable price. As much as I love Affinity, it's main selling point is that it offers a perpetual licenses at a reasonable price.
    If perpetual licenses become ridiculous expensive (in an attempt to nudge people to subscription), or worse still they switch to subscription only then I will have zero reason to stick with Affinity. 
    I think for V2 everything should be fine. It's V3 and beyond that I worry will make a shift to subscription only (or a ridiculous for perpetual to nudge people to subscription).
  3. Like
    big smile got a reaction from Felledk in Feature Request: Keyboard shortcuts for transform options   
    Affinity has a real good Keyboard Shortcut option in Preferences.
    Please consider adding keyboard shortcuts for the transform options so users can set their own shortcuts for these options.
    Example:
    I can set CTRL+Alt+CMD+X for Transform X. Then in future, when I press CTRL+Alt+CMD+X, the X field in the Transform panel will become highlight and I can type in the value, without needing to use the mouse to select the field. 
    Or I could set  CTRL+Alt+CMD+9 to the top right anchor point. Then when I want to change the anchor point of an object, I can just type  CTRL+Alt+CMD+9 without having to use the mouse.
    Mock ups:

     
    ^ A mock up of how it would look. Note that there is a new "All Affinity" option so you can use the same shortcuts across all the affinity apps (Photo, Designer and Publisher).

    ^ Once you've set a shortcut, you can type it and the relevant field will automatically become selected. 
    WHY WOULD THIS BE USEFUL?
    1. Automation
    Affinity doesn’t have scripting support, but it does work very well with automation packages such as Keyboard Maestro. 
    Being able to transform objects on the page is a key automation task. At the moment, this can be achieved by using a tool such as Keyboard Maestro to access the transform panel by emulating mouse movements. However, this is very prone to failure. Being able to enter keyboard shortcuts would ensure Macros are less prone to failing.
    2. Reduce repetition
    If you have a lot of objects to transform, using the mouse gets tedious. Being able to type keyboard shortcuts is more efficient. 
    POTENTIAL DRAWBACKS AND SOLUTIONS
    Coming up with separate keyboard shortcuts for the transform panel options may be cumbersome (e.g. CTRL+Alt+CMD+X is quite the command to remember). However, because this feature would be made available via the Keyboard Shortcuts option of Preferences, the user is free to set shortcuts that work for him/her).
  4. Like
    big smile reacted to thomaso in Publisher: Use Find command to find whole words that have partial formatting?   
    If your goal is to correct these local formattings AND you have saved/named character styles assigned to the desired variations, you can use the "Reset Formatting" button to remove the style variations that are not applied as a saved style.

    If you want to remove any local formatting (character style) yo can choose the according option by reassigning a certain paragraph style.

  5. Like
    big smile reacted to walt.farrell in Publisher: Use Find command to find whole words that have partial formatting?   
    If you know for sure the kind of mixed formatting you're looking for, you could make a copy of your .afpub and try this in the copy: 
    1. Do a regular expression Find for (\w+)  with the formatting set to whatever is causing the issue. 
    Set Replace to #\1#
    2. After you run the replace operation, do another regular expression Find for (\w#|#\w)
    That should help find any words with that specific mixed formatting.
    (Untested.)
  6. Like
    big smile reacted to walt.farrell in Publisher: Use Find command to find whole words that have partial formatting?   
    I don't think that would be possible, for two reasons:
    A regular expression cannot detect the formatting of characters; that requires use of the Formatting cog for the Find term. The Formatting options do not recognize words, and cannot detect parts of strings of letters, and apply to the entire Find string.
  7. Like
    big smile reacted to David in Яuislip in Publisher: Use Find command to find whole words that have partial formatting?   
    LibreOffice might help
    Copy text from Publisher
    Paste into LibreOffice Writer
    Do Format/Spotlight Character Direct Formatting 

  8. Like
    big smile reacted to thomaso in [MacOS] All Affinity Apps: Too many Noto Fonts   
    It was discussed quite a few times. Maybe it needs more user support in this Feature Request thread, initiated by Apple's Noto fonts:
    This thread also contains suggestions for workarounds … like that quite long thread, too, for instance:
  9. Like
    big smile got a reaction from kenmcd in Affinity Publisher: How to find and replace missing fonts?   
    I think this is what must have happened. I must have had the old V1 version installed. And then after I reformatted my system, I must have installed V3.
     
    That's just a custom font file I made, when I was testing out font creation software. But it's identical to the main font. 
  10. Thanks
    big smile reacted to kenmcd in Affinity Publisher: How to find and replace missing fonts?   
    You may have created the document with an earlier version of Open Sans.
    The v1 originals and the v3 from Google Fonts have different names internally.
    The Full Font Name and the PostScript Name are different - and these are often used to identify a font.
    The font name you see in the Affinity font menu is the Font Family Name (for these fonts), and it is the same in both versions.
    So it could be confused by the different internal names.
    (note: the Affinity font matching is rather dim and should be able figure-out these things).
    You could try the v1 original fonts and see how that works.
    Download here: http://www.opensans.com/download/open-sans.zip
     
    p.s. What is "Open Sans Bold Number Lines" and may I please have a copy of it?
  11. Thanks
    big smile reacted to thomaso in Affinity Publisher: How to find and replace missing fonts?   
    So it might be a glitch in this specific document (or a different font file used initially).
    Workaround:
    1. Deactivate Open Sans from your system. (to get it listed in the 'missing fonts')
    2. In APub use Find & Replace to temporarily replace it with any other (unique) font.
    3. Activate Open Sans.
    4. Use F&R to replace the temporary font with the wanted Open Sans.
  12. Thanks
    big smile reacted to thomaso in Affinity Publisher: How to find and replace missing fonts?   
    Safe Mode resets it during the boot process, yes, and it also may reset the Affinity font cache (quit Affinity before rebooting) – but I don't know if the "Affinity Fonts Replacements" is sufficiently affected by a macOS font cache reset, I guess that is rather stored in an app preference file and thus maybe worth a try.
    As Walt already mentioned: Was this document created or worked before without issues on this computer & with the same fonts installed/activated? Or are/were various versions of this font activated on this or an involved computer?
    Can you use Open Sans in a new document?
  13. Thanks
    big smile reacted to MEB in Affinity Publisher: How to find and replace missing fonts?   
    Hi @big smile,
    Have you installed the variable font version at some point? Affinity apps currently don't support them.
  14. Thanks
    big smile reacted to walt.farrell in Affinity Publisher: How to find and replace missing fonts?   
    That's odd. It works properly for me, on both Windows and macOS. What release of Publisher are you using?
    It's also odd, of course, that it says Open Sans is missing, and offers it as a substitution. That could indicate you have some mistakes in your installed fonts, either issues in a specific font or that you have a conflicting set of fonts installed. What version of Open Sans do you have installed on that machine, and on the machine that created the file?
     
  15. Thanks
    big smile reacted to thomaso in Affinity Publisher: How to find and replace missing fonts?   
    Are possibly two different versions of the font file involved, e.g. from different computers or de-/activated by a separate font manager app?
    If not, you could try to reset fonts for Affinity:
    • Preferences > Miscellaneous > "Reset Fonts".
    • Close APub + launch it with the CTRL key pressed to cause a reset dialog window > there is an option "Reset Font Replacements".
    If this doesn't help you could reset the font cache in macOS by booting the mac in "Safe Mode". https://support.apple.com/guide/mac-help/mh21245/mac
  16. Like
    big smile got a reaction from walt.farrell in Affinity Publisher: How to find and replace missing fonts?   
    Thanks for your help. I tried all these steps but it didn’t work. I assume once I go into Safe Mode, the font cache is automatically cleared, and I don’t need to do anything?
     
    Thanks for your help. I am using Publisher 2.3.1 on MacOs 12.7.2
    I am using Open Sans Version 3.000. I'm pretty sure this document has only been ever created and used on this machine. I know a few months back I did a clean reinstall. I am not sure if this document was created before or after the clean reinstall. 
  17. Like
    big smile got a reaction from piovasco in Publisher: Have a table split across a spread's text frames?   
    In Affinity Publisher, you can have a text frame split across a spread (i.e. so there's a text frame on the left side page that is linked to the right side page). Is there any way to insert a table in the text frame, so it will be split across the spread.
    Or any other way to make a table split across a spread?
    I've got a table that won't fit on one page, so it needs to go across the two pages of the spread. But I don’t want to create two separate tables, because if I make changes on the first table, then the excess rows on the first page won't automatically transfer to the first. 
     
  18. Like
    big smile got a reaction from MiWe in Request: better handling of imported styles when copying and pasting   
    Issue:
    In my Affinity Publisher documents, I tend to use the same text styles. When copying and pasting text between the documents, the styles get duplicated with a number added at the end. This happens even if the styles are identical. Example:

    ^ These are all the same style which have been duplicated when copy & pasting between documents. 
    Solution:
    When copying and pasting between a document, Affinity should ask the user how handle duplicate styles rather than just numbering them.
     
    Here is an example of how it could work:

    This dialogue box would pop up whenever copying and pasting text in situations where Affinity would currently just duplicate the style.
    This dialogue box would be optional, activated first via an option in preferences, so users who like the current handling of style can choose not to activate the option. 

    Explanation of options:
    Merge Styles - Keep incoming definition This option will cause the two styles to be merged. All values will follow the source document.  Merge Styles - Keep local definition This option will cause the two styles to be merged. All values will follow the local document.  Create new style - This will create a new style (which is how Affinity currently handles it by duplicating the style and adding a number to the name). Additional options:
    Clear Overrides - Any differences between the local and incoming style will be discarded.  Keep Overrides - Any differences between the local and incoming style will be kept as overrides.  Save Overrides as character style - The differences can be saved as a character style.  Example:
    I have  "Document A" which has  text that has a style called "English translation". This is just Helvetica, bold text 12pt. 
    I copy and paste this text into "Document B" that already has a style called "English translation". If I select "Merge Styles/incoming" then the style from Document A will be used. If I click clear overrides, then any differences between the text in document A&B will be lost. 
    Who would this be useful for:
    This would be useful for users who regularly copy and paste text between Publisher documents. 
    History
    This feature request is actually something I requested back in 2019 for Affinity 1. I am making a new request, because the issue still plagues Affinity 2 and it's super, super annoying. It still happens even when the source and destination have the same style sheet with the same style definitions. 
    I literally spend 20% of my time using Affinity wrangling with styles. Grr!
    As a workaround, you can copy and paste into a new document, go to the text styles menu and then select "Detach and Delete all styles". And then, from there, you can copy and paste into the destination document. You can then re-apply the styles in the destination document. (If you are on a Mac, you can use Keyboard Maestro to copy and paste your text without formatting, thus saving the step of pasting into a new document). But even with this work around, it's a still a time waste!
    I appreciate that development of new features is complicated, so I just hope things work out to make having a solution viable one day, hopefully sooner than later. 
  19. Haha
    big smile got a reaction from Westerwälder in Request: better handling of imported styles when copying and pasting   
    Issue:
    In my Affinity Publisher documents, I tend to use the same text styles. When copying and pasting text between the documents, the styles get duplicated with a number added at the end. This happens even if the styles are identical. Example:

    ^ These are all the same style which have been duplicated when copy & pasting between documents. 
    Solution:
    When copying and pasting between a document, Affinity should ask the user how handle duplicate styles rather than just numbering them.
     
    Here is an example of how it could work:

    This dialogue box would pop up whenever copying and pasting text in situations where Affinity would currently just duplicate the style.
    This dialogue box would be optional, activated first via an option in preferences, so users who like the current handling of style can choose not to activate the option. 

    Explanation of options:
    Merge Styles - Keep incoming definition This option will cause the two styles to be merged. All values will follow the source document.  Merge Styles - Keep local definition This option will cause the two styles to be merged. All values will follow the local document.  Create new style - This will create a new style (which is how Affinity currently handles it by duplicating the style and adding a number to the name). Additional options:
    Clear Overrides - Any differences between the local and incoming style will be discarded.  Keep Overrides - Any differences between the local and incoming style will be kept as overrides.  Save Overrides as character style - The differences can be saved as a character style.  Example:
    I have  "Document A" which has  text that has a style called "English translation". This is just Helvetica, bold text 12pt. 
    I copy and paste this text into "Document B" that already has a style called "English translation". If I select "Merge Styles/incoming" then the style from Document A will be used. If I click clear overrides, then any differences between the text in document A&B will be lost. 
    Who would this be useful for:
    This would be useful for users who regularly copy and paste text between Publisher documents. 
    History
    This feature request is actually something I requested back in 2019 for Affinity 1. I am making a new request, because the issue still plagues Affinity 2 and it's super, super annoying. It still happens even when the source and destination have the same style sheet with the same style definitions. 
    I literally spend 20% of my time using Affinity wrangling with styles. Grr!
    As a workaround, you can copy and paste into a new document, go to the text styles menu and then select "Detach and Delete all styles". And then, from there, you can copy and paste into the destination document. You can then re-apply the styles in the destination document. (If you are on a Mac, you can use Keyboard Maestro to copy and paste your text without formatting, thus saving the step of pasting into a new document). But even with this work around, it's a still a time waste!
    I appreciate that development of new features is complicated, so I just hope things work out to make having a solution viable one day, hopefully sooner than later. 
  20. Like
    big smile reacted to MikeTO in Publisher: Restore ability to import a document into itself   
    IMO the best way is to export the cover alone as a bitmapped format (TIFF for CMYK or JPG for RGB). Although importing a PDF would work fine, this would avoid any bugs with linked PDFs and there have been a couple of those this year. Using a bitmapped format also reduces the load on Publisher. Instead of having to interpret (process) an afpub or pdf file when exporting the page with all the cover shorts to PDF, it could just include the bitmapped image which is much less work. The key of course is to ensure you choose the right resolution, not too low for your needs but not needlessly high which would bloat the file.
    Cheers,
    Mike
  21. Like
    big smile reacted to MikeTO in Publisher: Restore ability to import a document into itself   
    I think this was probably due to fixing the file locking issue so it was a necessary change. Although it worked well for your need, importing a complex document into itself can lead to crashes.
    The other recursive hole is still open though - you can import file 1 into file 2 and file 2 into file 1. I tried it with a Book for fun. I even added a cross-reference from 1 to 2 and from 2 to 1. Then I placed chapter 1 into chapter 2 and chapter 2 into chapter 1. Needless to say, saving either chapter was lots of fun. I don't recommend this. 🙂 
     
  22. Like
    big smile reacted to thomaso in Publisher: Paste a list into table   
    Yes, there is "a" way – its details depend on your platform (mac/win) and the source file type (spreadsheet, .rtf, txt. … etc.). So it appears to be a more or less complex procedure which requires to consider several if-then conditions.
    This two threads discuss this and include sucessful workflows:
  23. Like
    big smile reacted to R C-R in Publisher: Paste a list into table   
    FWIW, for me if using Safari I copy the list from the first post to the clipboard, it works fine if I first select enough cells ... but if say I paste that text into TexEdit & do not make the format Rich Text then it all ends up in the first selected cell.
    So if you copy the text from this text list.rtf file, if you then select at least two cells & paste, does it work for you?
  24. Like
    big smile reacted to anto in Publisher: Have a table split across a spread's text frames?   
    I got it wrong. Here's how to do it.

    2023-10-03 18-17-40.mp4    
  25. Like
    big smile reacted to anto in Publisher: Have a table split across a spread's text frames?   
    Try this way

    2023-10-03 17-34-25.mp4    
×
×
  • 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.