walt.farrell

Welcome to the Serif Affinity forums, @Mr. Ross. The usual recommendation I've seen for this situation is that one contact Serif directly via email to affinity@serif.com for assistance.

Welcome to the Serif Affinity forums. The FAQ has some suggestions that might help:

That's under your control in the More... options in the File > Export dialog. The default is ZIP compression, which for me gives somewhat better size results than choosing NONE, and much better than choosing LZW, for the 16-bit image I just tested with.

Just a comment to note that the view rotation function has been improved in the 1.9 beta. Still nothing that would allow you to add "drag" to your own shortcuts, but it's possible to rotate freely, in other than 15-degree increments. It's mentioned in this announcement for Designer beta 1.9.0.780:

Thanks. I agree that the Paragraph Panel topic covers it adequately. Perhaps the Flow Options section of the Paragraph Formatting topic could specifically mention the description in the Paragraph Panel topic?

If you purchased from the Affinity Store originally, then you can login to the Store at https://affinity.store/account/downloads and you will find download links, and the related product key and email address. (Note: the Affinity Store login is separate from the Affinity forums login.) Google translation: Jeśli pierwotnie dokonałeś zakupu w Affinity Store, możesz zalogować się do Sklepu pod adresem https://affinity.store/account/downloads, a znajdziesz tam linki do pobrania oraz powiązany klucz produktu i adres e-mail. (Uwaga: login do Affinity Store jest niezależny od loginu do forum Affinity).

Most of that work can be done in Publisher as easily as in Designer, if it's vector work. If you also work in Designer's Pixel Persona, though, you'd also need Photo. With the combination of all 3 applications, you have everything that exists in the Photo Persona of Photo and the Designer Persona of Designer. You're missing the other Personas from Photo and Designer, so you won't have the Export Persona, Liquify Persona, Tone Map Persona, but you'll have the illustration tools you need. And you'll have the expanded text tools. If you haven't tried that as a workflow yet, I'd recommend trying it. I've found it useful.

There's a preference that requries the use of the Shift key in order to cycle through the tools associated with a shortcut: Perhaps that will help.

You're welcome.

My camera's raw files are smaller than yours, and so my .afphoto files are also smaller. For one typical file, 4948 x 3280 px, RGBA/16 after developing: .nef file: 19,225 KB .afphoto file: 139,368 KB Just based on calculations, it appears my camera uses about 10 bits per pixel in the raw image. So, for the raw file: 4948 * 3280 * 10 /1024 / 8 gives a rough size for the .nef file of 19,811 KB which is in the right ballpark. And for the .afphoto file, 4948 * 3280 * 64 / 1024 / 8 gives 126,792 KB which is also in the right ballpark. 139,368 - 126,792 leaves 12,576 KB unexplained. If I delete the snapshot and save it again the size is 111,280 KB, so the snapshot part of it is about 28,088 KB. 139,368 / 19,225 tells me that my .afphoto is about 7x the size of the initial raw file.

Bug reports are entered into a queue, and processed (as I understand) approximiately in the order they were created, though it may vary a bit depending on which members of the staff are free to work on them. In normal times I have had some take a few days, but some take a week or more before Serif could get to them. You started this thread on Dec. 20, and Serif started their annual company closure on Dec. 24. It will end tomorrow, Jan. 4.. Since Dec. 24 they've been operating with only minimal staff available, so they will be behind on processing reports for awhile after they return.

Thanks. A rough calculation: The file from your camera is 7698 * 5320px at 16 bits per pixel which is approximately 80MB. The .afphoto file is 7698*5320px with 4 channels (R, G, B, A) per pixel. At 16 bits per channel per pixel (i.e., 64 bits per pixel), this is approximately 320MB, or 4x larger than the raw image. Additionally, the .afphoto file will contain an initial Snapshot, which I would guess accounts for the additional data required to get to your total of 5x the size of the raw image file.

I don't think there's a term shown in that diagram. And I'm not sure if there's a term in general. To further confuse things, here is an A with diaeresis (aka umlaut) and a combining overline, followed by one with 3 combining overlines. I don't think there would be specific terms for the height lines when multiple combining items are added to a single letter.

As a Windows user I'm not really familiar with how those shortcuts would work on a Mac. But unless you've configured Affinity's Preferences to enable the standard Mac text shortcuts I wouldn't expect Cmd+PageDown to select anything. Also, unless you've changed the standard Affinity keyboard shortcuts Cmd+PageDown should simply move you down a page without doing any selecting. So we probably need more information about those options to know how it should be behaving. Someone with a Mac will need to point out where those settings are, if you need additional info about that.

Thanks, but the Affinity settings don't really give the needed information for the .afphoto file. What are your settings for the Develop Assistant? (View > Assistant Manager, then you may need to click on the Develop Assistant button). With an image in the Photo Persona after you've Developed it, what does the Context Toolbar show when you have the Pan Tool (Hand) selected? Did you do anything after pressing Develop and before you did the File > Save to create the .afphoto file?

The letter must be typed first. The combining characters are applied to the character that precedes them. But for me, the combining overline is properly centered on the letter: (These are spaced letters, each with the combining overline following it. The spaces are not necessary, and are there only for clarity. Font is Arial.)

Depends on which height one uses For some font metrics I would expect tee and el to have the same "height", and for this purpose they do.

Ignoring the Pring dialog for the moment, what units does Affinity Photo show in the main window when you have the rulers displayed, or when you use Document > Resize Document? If it shows cm there, it should show cm in the Print dialog. What Paper Size are you specifying in the Print dialog's Layout tab? Have you clicked the Properties button in the Print dialog and verified that your printer is set to use the corresponding paper size? What scaling option have you chosen for the Fit Type option in the Print dialog? Some screenshots might be helpful.

Welcome to the Serif Affinity forums. What are the pixel dimensions of that image? What color format is your .afphoto file (RGB/8, /16, or /32)? Have you done anything to the .afphoto file after you pressed the Develop button?

Was this in a new document, or in the InDesign template you Opened? If it's from that template your document default is coming from there. With the cursor in your text, look in the Character panel, Language section. What language is specified for Spelling?

At least on Windows, Affinity will (as far as I know) convert your document to RGB to send it to the printer driver, and it will be up to the printer driver to re-convert it to the color format the printer needs. Possibly whatever PDF printer driver you've chosen is maintaining it as RGB?

It almost sounds like you are using File > Place rather than Document > Add Pages from File... (which is the document merge function). Can you provide some more details of exactly what you're doing so we can better understand your workflow?

Correct. But fortunately you have Publisher, and can just do your work there

Good idea; thanks. Not perfect, though, as the combining overline is sensitive to the height of the letter it's applied to:

You might also consider saving your snippets as artistic text, then: Inserting the text cursor into a text frame where you want to put your snippet; Dragging the asset over the cursor; Clicking the Pin Inline button on the Toolbar; Adjusting the size of the snippet if needed to make it fit as you want it to.