big smile
Members-
Posts
320 -
Joined
-
Last visited
Everything posted by big smile
-
publisher 1.9.0 freezes, when loading File oder pic.
big smile replied to credo's topic in V1 Bugs found on macOS
It's got a tonne of linked images. Do I need to upload those as well or just the file. Also, it's got explicit text and line drawings (but no photos). Will that be an issue? -
publisher 1.9.0 freezes, when loading File oder pic.
big smile replied to credo's topic in V1 Bugs found on macOS
I am having this problem too. My file opend fine in Publisher 1.8, but just gets stuck on loading with 1.9. The file uses pinned images heavily. -
Oh, yeah, it's not a request for that. That's a valid point and sorry for not being clear! I disagree. While switching to Designer persona indeed make this possible, it adds an extra step which when doing hundreds of pages lengthens the process. Plus, I've found switching to personas not always to be straight forward. Sometimes they switch instantly. Other times it takes several seconds for the switch to occur. And that adds a random factor which makes writing automation processes harder and more error prone.
-
With automation software, you can manipulate the selection once it's been selected before you flip to the next page. Keyboard Maestro allows manipulation via Keyboard shorts and the mouse, so there's a lot you can do. Example: I once had a project where there were hundreds of graphics in a single Affinity Designer document. And each one of these graphics had to be placed in a different corner of each page of a 180 page Publisher document (so each corner would have a different graphic). Keyboard Maestro was able to go into the Designer document, select one of the graphics, go back to publisher, put it in the corner of the publisher page (and resize it so it fitted neatly into the corner), flip to the next Publisher page, go back into Designer and then restart the whole process and do it 108 times. (This is just an example to show how flexible automation software is, I know the example doesn't relate to the current thread topic of "select same").
-
@Gabe After testing this extensively, it occurs under the following conditions: • You make a change to the (imported) source document's master pages, where those master pages are applied to other pages within the source document. (It happens even with a minor change to the master page, such as changing text). • You make a change to the (imported) source document's sections (under section manager).
-
Feedback 1: Add "all text" option The next "select object" tools are awesome. However, under "select object" there is an option of: Art text Frame Text Path text It would be good if there was an option for "all text". The reason is that imported Ai documents often have text rendered as both art text and frame text. So trying to select them all at the same time can be fiddly. Having an "all text" option would make things more straight forward. Feedback 2: Add Options to Publisher Please could you add the "Select Same" & "Select Object" to Publisher (and maybe even Photo as well). It would be very handy especially when using automation software (such as Keyboard Maestro) to work on large documents. I recently had a project where I needed to select all the text on a page (but not the images) on a 160 page document, so something like this would have been perfect. The Adobe apps allow for scripting, which Affinity does not, so anything that makes Affinity more accessible to automation software would be great (especially as Automation software is more user friendly than scripting) I know studio link can be used to access this functionality, but it would be so much more easier if it was in Publisher natively.
-
Publisher 1.8.4: PDF text is rendered as artistic text
big smile replied to big smile's topic in V1 Bugs found on macOS
@Gabe Attached is a sample. 1. Here is how it imports if you do not tick "Group lines of text in text frames" All the text layers are artistic text, so I can't resize the frames. Artistic text is a serif invention, so the original PDF wouldn't have been designed with that in mind. 2. Here is how it imports if you do tick "Group lines of text in text frames" Now it's all text frames, which is great. But the way Affinity creates the text frames is a bit messy, so headings get grouped in the same frame as body text, which means there's a lot of extra editing involved if I want to change the layout of things. In earlier versions, the text wouldn't be imported as artistic text, so it was fine. sample.pdf -
Previously, if you opened certain PDFs in Publisher and did not select "Group lines of text in text frames", it would render the text as a regular text frame. In 1.8.4 these same imported PDFs now render the text as artistic tex in Publisher. This is a bug, as artistic text is a Serif invention, so a PDF created in another app would never use artistic text. It's very annoying, because artistic text frames cannot have their dimensions adjusted (doing that just causes the text to stretch). If you have a PDF document with 100+ pages then having to copy and paste the text as a text frame is a nightmare (especially as in the past you could use automationation software such as Keyboard Maestro to batch resize the frames on multiple pages without having to copy and paste the text first). If you tick the box, "Group lines of text in text frames", then the text will not be set as artistic text. But then those text frames can cause flow problems when removing lines. Please revert it back so that all text rendered from an imported PDF is always set as a regular text frame and not artistic text.
-
This is my text 01 New Day 02 Moonlight in the dark night 03 Another Song and Dance. I need to insert a line break after the two digits. I enter the following: Find: \d\d\s Replace \d\d\n The line break gets inserted, but my numbers get replaced with dd e.g. dd New Day dd Moonlight in the dark night dd Another Song and Dance. How can I get it replaced properly, so I keep my numbers, while also having the line break. Thanks! Also, the line break seems to be a paragraph break and note a line break.
-
As discussed in this thread: Here is text with accented characters in Publisher (set at 30pt font size): Here is how it looks like when exported to PDF The font being used is Rubik from Google Fonts. However, the issue persists even if it is replaced with another font such as Helvetica. It will import fine as a PNG. The issue only occurs if the font is a certain size. Here is text from the same document set at 24pt and it is fine: I can't share the whole file, but I have attached a sample that has one of the problem headings. People in the thread have tried it on Windows and it works fine. However, I have tested it both on Mac OS 10.14.6 and 10.15 and the issue persists. sample.afpub
-
I've tried restarting the mac and also uninstalling Publisher (using Appcleaner to completely wipe out all traces of it), but the issue still persists. I can't share the whole file, but I have attached a sample that has one of the problem headings. Maybe it might help someone find a solution. sample.afpub
-
I am using Bold and Regular on Mac Os 10.14.6 I haven't set up any baseline grid. Here are my font settings in the stylesheet Font: Rubik; Font weight: Bold; Italic: Off; Font width: Normal; Font size: 30 pt; All caps; Align paragraph: Center; Leading mode: % ideal; Leading: 100 %; Space after: 15 pt Here is the character panel for the font: Here is the paragraph panel for the font:
-
I don’t think the font is the issue, because if I replace those lines with Helvetica, but keep the font size the same, the issue remains: Interestingly, with Helvetica, the issue occurs both in the Affinity Publisher document and the PDF (whereas with Rubik font it is correct in the Affinity Publisher document but incorrect in the PDF).
-
So I guess I'll have to pick another font. Odd that it displays correct in Publisher but only comes out wrong when exported into a PDF (and only from a Publisher export, as it exports fine from Affinity Photo). Interestingly, if the font is set at a lower font size then it will export correctly from Publisher: ^ This is set at 22pt and exports correctly (The screen shot is from the PDF export) ^ This is set at 30pt and it is borked!
-
The font is Rubik from Google fonts: https://fonts.google.com/specimen/Rubik I have tried using Helvetica, and the accents on that output fine when exported to PDF via Publisher. I can export from accented characters from Affinity Photo with this font just fine, so I am not sure why Publisher is misbehaving.
