thomaso
-
Posts
11,201 -
Joined
-
Last visited
Posts posted by thomaso
-
-
In case you do not look for falling snow … but rather fallen, lying, melting …
-
-
On 11/10/2023 at 12:19 AM, Chris Sutton said:
I'm considering replacing my (old) Macbook Pro
13 hours ago, Andreas Scherer said:I guess my gist is: Don't listen to the fearmongers!
Apart from the fact that Apple's silicon architecture handles RAM + GPU differently then before AND that Affinity document's content + tasks may be quite differently demanding, this site has several articles about RAM and various M-versions, for instance
https://eclecticlight.co/tag/ram/
https://eclecticlight.co/2021/03/26/how-big-should-the-memory-and-ssd-be-in-your-next-m1-mac/
-
18 hours ago, MikeTO said:
My reply was intended to state that the fact that they were capitalized was not relevant to whether or not they were flagged as misspelled because they were not in the dictionary.
Ah, I seem to have misunderstood this approach and perspective of capitals (… related to their special, seldom use in English / different to German where all nouns start with capitals).
On 11/7/2023 at 9:41 PM, MikeTO said:My book project has hundreds of people and place names in it and I've had to right-click all of them and choose "Learn" to add them to my user dictionary.
19 hours ago, MikeTO said:Publisher because it doesn't have a case sensitive search option
On 11/8/2023 at 4:44 PM, MikeTO said:request is for an option not to hyphenate capitalized words because there's no exceptions dictionary for hyphenation.
How about using the Find And Replace panel with a regex search for capitals [A-Z] ?
Possibly you could use it for easier creation of dictionary exceptions + to avoid hyphenation:• add an index marker before every capitalized word (or via TOC) -> use this resulting text to copy/paste directly into your custom dictionary file in your macOS library spelling folder?
• add a special character "soft hyphen" before every capitalized word -> and exclude it this way from getting hyphenated?
-
On 11/6/2023 at 6:21 AM, Anti-Hero Annie said:
But the filters still don't work. I selected myself in the background. I can choose the filter I want, but when I apply nothing is happening.
Selected yourself OR the background?
According to your Layers panel's thumbnails you possibly have the empty background selected for the filter. If you want to sharpen the foreground you don't need a pixel selection in this case (because the background is on a different layer).
Alternatively, if you want to blur the background you would select the middle layer (again without the need for a pixel selection). -
You might want to add your vote to this old feature request (or create a new one for V2) for a more convenient interface regarding "Lock Children". A keyboard shortcut is just one possible improvement (and requires a menu entry, instead of being in the Context Toolbar), a button in the Layers panel could be another …
-
1 hour ago, irandar said:
the Preview version looks sharper, similar to the AP file. The smaller file size gives the sharpest result in this case.
41 minutes ago, irandar said:Are you sure you did not get these images switched around?
My screenshots were done in the forum's browser window, so the file names in my screenshots appear to be yours.
To judge the sharpness of two images they both have to be displayed in the same zoom level, whereby you get the most reliable display if you set the zoom level to "Actual Pixels" (APh: shortcut 'cmd 9' | Preview: depends on your app preferences).
If, to your eyes, indeed "the smaller file size gives the sharpest result" then I don't understand your question or problem. Nevertheless, my experience is opposite to yours.
If you indeed want to reduce the file size of your exported APh image you can …
• reduce the image's pixel dimensions,
• increase the compression rate for export = reduce the "Quality" value
• choose the resampling method "Nearest Neighbour" or "Bilinear" (not "Bicubic" or "Lanczos…"). -
On 11/8/2023 at 10:44 AM, irandar said:
when I make a screenshot with Preview on Mac and then a jpeg that I always get better results than when I make a jpeg export from APv1.
15 minutes ago, irandar said:The main thing is that the Preview route gives a much better jpeg image,
How do you "make a screenshot with Preview" (or do you mean the macOS screenshot feature?) – And in what way do you mean "better"?
It is not useful to compare your results without knowing the compression rate + resampling methods in both processes. From your file names it appears that the Preview result has obviously less quality than the APh export (assuming "editnewjpg" refers to the APh result) … while it is unclear for what reason the Preview result is titled on the image with "Soften Structure".
34 minutes ago, irandar said:Not sure I understand what you are saying about the exported size.
Like with compression & resampling for a useful comparison also the image pixel dimension matters … and thus the zoom level: your recent examples have quite different size and thus they can't match in detail quality: Preview: 1474 px | APh: 5472 px width. – With other words: It is a comparison of apples with pears.
-
1 hour ago, MikeTO said:
They're not marked because of their capitals, but they are capitalized.
What is the difference between "capitals" and "capitalized"? – Are the possible names of people, geography or companies part of spelling dictionaries at all? To me it appears not to matter for spell check whether I type the names of OP's screenshot with upper or lower case.
1 hour ago, walt.farrell said:Those are styling options that simply change how the text is displayed. They don't change the actual characters, and thus don't affect spelling.
Not only is the sentence "This is One With typed Caps" in my example typed with shift key and thus not a display/style option but do not get marked by spell check, also is the selected text frame in my second screenshot switched via the style/display option "Upper Case" but obviously does influence spell checking: then none of the words gets marked, even the obvious issues like TÜPO, WHYLE, NAIME that get marked if this style option is not used – as if this "Upper Case" option would disable spell check.
-
On 11/7/2023 at 6:30 PM, David Brear said:
I get a long list of capitalised words shown as Spelling Mistakes
6 hours ago, MikeTO said:Why would anybody want an option not to spell check capitalized words?
Are you sure they are marked because of their capitals? – To me capitals don't seem to cause a spell check issue:
If just capitals would cause spell check issues: What about the style options Title Case, Sentence Case … and finally Upper Case with SPELL CHECK OF ESPECIALLY LEGAL/CONTRACT TEXT PARAGRAPHS OFTEN PUBLISHED IN CAPITALS ONLY FOR REDUCED READABILITY AND INCREASED CONFUSION.
Strangely, if I switch the text above via the Text menu to "Upper Case" then spell check seems to be fully disabled … while neither "Lower Case" does its first characters of sentences … nor does "Sentence Case" gets the odd capital 'A's marked a issues.
-
Did the .afpub behave like this from its initial .idml import – or caused by any later step?
Possible workarounds:
• Create a new empty .afpub with same page dimensions and colours space, then choose menu Document > Add Pages From File… and select the affected .afpub for import.
-> This workflow sometimes helps to fix issues, e.g. with .afpubs that don't open but cause a 'corruption' error message.• Select all text of the entire book (I assume it's a long story of linked text frames), then cut the text, paste it into a new TextEdit document, select there all text again and copy/paste back to the .afpub. If this doesn't help you could also try the process via TextEdit with a plain text file (.txt, not .rtf), while this way you will of cause lose any formatting.
-> This might help if the .idml contained a special character or formatting that APub can't handle properly, there are reports in the forum about Word.docs that cause issues if placed directly. Also I wonder what can happen with ID's GREP styles in APub (e.g., are they simply ignored or may they create any unexpected data within an .afpub?) If this workflow helps to avoid your current issue it could indicate that any special character within the text flow would influence the problem and you could try to detect the culprit to change this part within your initial but affected .afpub. -
8 hours ago, GarryP said:
I’ve never used that Autoflow feature but thanks for mentioning it; more reading for me to do.
However, like you say, I would expect a contact sheet to also include the filename
Actually it appears easier to use Data Merge, as you initially mentioned. – On mac: To get the images as data table it is sufficient to …
1. copy the images in the Finder + paste into a plain text file (txt, not rtf),
2. add a first line for APubs Fields Panel (e.g. "my images"),
3. save this text file in the folder of the images,
4. rename its suffix from .txt to .csv.This single data column can be used in APub for both: to get the images placed AND to get the file names added. Also creating the layout via the Data Merge Tool can be simpler than multiple power-duplicated & arranged copies of picture frames.
- adrianlambert and GarryP
-
1
-
1
-
16 minutes ago, KeithStoddart said:
dropped in each pic
1 minute ago, GarryP said:drop some images into some Picture Frames
Doesn't the V2 feature "Place Images Autoflow" automatically fill a set of multiple frames with a set of selected images to place?
However, IMHO a contact sheet would also display file names at least, if not even selected metadata like size or date for instance.
-
1 hour ago, GarryP said:
The developers already have a way to get the thumbnails of the pages so I would guess that those would be easier to use.
55 minutes ago, D.VE said:Whatever is easier to implement for the DEV team...
Apart from the existing previews in the Layers & Pages panel: On mac it could be possible to get all pages as previews in a Finder window via QuickLook (space key), like it works for PDF files where you can scroll through all pages in this Finder's pop-up preview.
Interestingly, Affinity apps contain an according file "QuickLook.qlgenerator".
< /Applications/Affinity Publisher.app/Contents/Library/QuickLook/QuickLook.qlgenerator >
... whereby the < /System/Library/QuickLook/PDF.qlgenerator > has a file size of 44 kB, while the Affinity version is 168 kB in size. -
-
3 hours ago, Lee_T said:
This may give a better appearance in the initial preview, but as it's RAW it doesn't affect the data captured.
Thank you for pointing out my misunderstanding. Yes, though a WB (set in the camera before capturing) gets noted in the RAW's metadata and may open a RAW accordingly this WB correction is still just a temporary setting for displaying the unmodified RAW data … and thus doesn't help here.
-
21 hours ago, Announcement said:
Calebcudjoe's workaround (significantly shifting white balance, then bring it back later) also work for me, but increase my workload significantly when I frequently shoot concerts and therefore will run into this issue frequently.
In this case
it might help* to adjust the whitebalance before shooting, i.e. from blue/pink to green/red.
*EDIT: not for the captured RAW data.https://support.usa.canon.com/kb/index?page=content&id=ART182460
-
1 hour ago, Announcement said:
Interestingly, DPP also had some issues with clipping
Oddly, Canon Asia seems to like intense blue light …
… while an issue with intense blue (… turns purple) gets discussed, for instance:
https://www.dpreview.com/forums/thread/4450750
https://www.dpreview.com/forums/post/63422607- Lee_T and Announcement
-
2
-
29 minutes ago, Announcement said:
considering the volume of images I edit and the resulting huge increase in workload this issue creates for me, I absolutely need editing software that can more accurately interpret the RAW data.
Unless it's fixed in Affinity (no one but Serif might know, if anyone), you'll probably get the most reliable result using Canon's free Digital Photo Professional app. Additionally, this is perhaps the only tool that considers/respects every camera & image setting made for your shootings. And unlike Affinity, Canon's DPP lets you apply your adjustments directly to other files, folders or collections displayed in its File Browser area like a 1-click batch option (… apart from its separate Batch feature).
-
6 hours ago, Eisbar said:
If I set "Hrvatski" (= Croatian) in the basic settings - then the word is also learned immediately. In another publisher document, I can also use the learned word. And if I unlearn it, then it is no longer available in the other documents.
So it stays that way - where is this custom-file "hr"?
I assume with "basic settings" you mean the macOS System Preferences? – I tried your workflow in macOS Mojave in Affinity and in TextEdit but without finding any hint to the file or path of a custom dictionary entry. Although "Learning" the entry "Herr-Watzki" appears to work and does not get marked again in a further spellcheck, also to me a custom Croatian file doesn't appear in the user/library/spelling folder.
Oddly, I don't see a way to "Un-Learn" nor to get the learned "Herr Watzki" as a suggestion (Vorschlag) when I mistype the new learned word with 'y'. So it appears unclear to me how this works at all or is meant to work in detail.
With a search as 'root' via FindAnyFile for Herr-Watzki as file content I am unable to detect the wanted file that would obviously or likely contain that entry (but get the .autosave files listed for Affinity and TextEdit).
A search for modified in the last 1 minute offers 95 results with most of them inside the hidden system folder structure private/var/… and pointing to various macOS internal files (e.g. 'mdworker', 'Spotlight') + a bunch of Firefox Browser caches. – Both searches let me assume that my custom Croatian dictionary entry gets stored in a fully inaccessible folder (in the Finder marked accordingly) and/or gets stored in a 'cryptic' file format (not as 'readable' text) and/or saved at a later time (e.g. after a reboot?) in an according file with a name I don't know.
So I give up with a further search for the file path. – Possibly you can get different results with TextEdit in your macOS Sonoma. I used TextEdit because, since the dictionaries are managed by macOS, the issue appears to be not Affinity related.
-
9 hours ago, Gianni Becattini said:
Even if I can understand the printer problem.
"Actually" there is none: Either the printer's imposition software will handle the inner bleed of your delivered PDF as required or they may demand a PDF without inner bleed.
The usefulness of an inner bleed depends on the type of binding (thread, glue, spiral) and the cut print sheet / page size. For thread stitching the printer's software might rather avoid to print the inner bleed. For glue and especially for spiral binding the inner bleed may be wanted if the layout has an image or coloured background across two pages / the spine of a spread, while an inner bleed may disturb if one page of a spread has colour up to the spine while its opposite page does not. In the latter case precise cutting is required, regardless of printing the inner bleed or not.
-
1 hour ago, GeirSol said:
and documents that are closed before app crash is also reopened.
If you don't get the "restore" option dialog when relaunching Affinity then you could prevent them from reopening by manually removing them from the Affinity "autosave" folder before relaunching the crashed app. The "autosave" folder is in the same parent Affinity folder where also the folder "temp" and your user preferences are stored (i.e. folders like "user", "presets").
-
In addition to Walt's hints: Document's that you close before quitting the app do not get reopened.
-
6 hours ago, Gianni Becattini said:
I get the bleed of the left page on the right page, and the bleed of the right page on the left page.
Actually the inner bleed shows the inner edge of the opposite page, not the bleed of the opposite page. – This is what you would expect if both pages would get printed on a large sheet ... just like on the layout you place the image bounding box at the spine without bleed + show the contents of the other page right next to it.
I have a publisher font style problem
in Affinity on Desktop Questions (macOS and Windows)
Posted
Every single text style uses one font only. But possibly you can create a Character Style for one of the two languages + apply this to the related text inside your paragraph. Then all text could have one Paragraph Style assigned but could appear with a quite different font where it got the Character Style assigned additionally.
Apart from that, there are various fonts that contain both Chinese + Latin characters for English (… and other scripts/languages).