David in Яuislip

<gemitus> O cara, o cara, altera cara! </gemitus>

My use of Latin was limited to quod erat demonstrandum and I don't use that much these days Accipio auctoritatem tuam - fidem Google

My previous experience with hyphenation dictionaries in the user area is that they have no effect The program comes with hyph_la.dic as Mike notes It's the only file in C:\Program Files\Affinity\Publisher\Resources\Dictionaries\la I have added la.dic, la.aff & hyph_la.dic to C:\ProgramData\Affinity\Common\1.0\Dictionaries\la\ I created a new style based on Body but with the Language and Hyphenation set to Latin As standard the word suspiramus hyphenates thus: su- suspi- suspira- suspiramus After adding sus5p5iram5us to user hyph_la.dic it now does this: sus- susp- suspiram- suspiramus Quid mirum But apart from that is it correct to hyphenate Latin at all? The language was pretty dead by about 700 AD and Gutenberg didn't print his Bible until 1455

I create a circle and duplicate it To the bottom circle I add art text Same for the top circle Now I can only select the top text unless I turn that layer visibility off If I change the order of the text layers then I can select either one with both layers visible, no need to keep changing the layer order Same behaviour in V1 Photo and Publisher

I think that this is displaying the embedded preview, you'll have your work cut out getting this result from the raw

I suspect that the raw files contain metadata indicating the film simulation. This will be applied by those programs that recognise it otherwise you just get the raw data. I doubt that Photo will ever be able to process all of the various simulations of all of the cameras out there

It imports ok into V1.10.6, not that I will ever use it, it would be like going back to a dial-up modem

'Course it ain't. Use the Help to understand the difference between Masking (raster) and Clipping (vector) then just do it 🙂 Don't use Photo for the pen work, I used Publisher because Photo pasteurises the pen line, I expect that Designer will work as well

Trace around the item with the pen, fill with a solid colour and nest the shape into the clipping position. For the cutouts make separate paths and combine with the main outline using Layer/Geometry/Merge curves, here's a quick example Reactor.zip

ImageMagick info: abridged report Format: TIFF (Tagged Image File Format) Geometry: 1280x730+0+0 Resolution: 1x1 Colorspace: sRGB Type: Grayscale Endianness: Undefined Depth: 32/16-bit Channels: 3.0 Channel depth: Red: 16-bit Green: 1-bit Blue: 1-bit Channel statistics: Pixels: 934400 Red: min: 0 (0) max: 230614 (3.51895) Green: min: 0 (0) max: 0 (0) Blue: min: 0 (0) max: 0 (0) The only way I can get that as 32bit into Photo is to do magick 32bitBedDepth.tiff 32bitBedDepthIM.exr which produces a monster file so here's a 16bit png which looks the same, zipped to avoid forum mangling 32bitBedDepth.zip

As a guess, when you want to replace an existing profile it must be in its own file. If you want to add lenses then they can be combined as you did, it's all voodoo Vignetting correction looks excellent, hope you'll send this to lensfun as it's far superior to the crap they have at present CanonEF28mmf1.8USM.xml

I'd advise a trial of DxO Viewpoint, also integrates with Photolab, dead easy and superb results

A shot in the dark as I don't have a suitable raw but I always start these files with <!DOCTYPE lensdatabase SYSTEM "lensfun-database.dtd"> <lensdatabase version="2">

Check the Help for "Exporting custom adjustments as LUTs" Possibly use a Recolour adjustment layer

It's an identity lut which will do nothing. Note that nested adjustment layers are not included when exporting LUT, the adjustments must be above the image layer Below is a comparison taken at random, mine's on the right TITLE "12&3" TITLE "Exported LUT" #LUT data points #LUT data points 0.418182 0.072727 0 0.418182 0.072727 0 0.436364 0.072727 0 0.436364 0.072727 0 0.454545 0.072727 0 0.454545 0.072727 0 0.472727 0.072727 0 0.472727 0.072727 0 0.490909 0.072727 0 0.490909 0.072727 0 0.509091 0.072727 0 0.509091 0.072727 0 0.527273 0.072727 0 0.527273 0.072727 0 0.545455 0.072727 0 0.545455 0.072727 0 0.563636 0.072727 0 0.563636 0.072727 0 0.581818 0.072727 0 0.581818 0.072727 0 0.6 0.072727 0 0.6 0.072727 0 0.618182 0.072727 0 0.618182 0.072727 0 0.636364 0.072727 0 0.636364 0.072727 0 0.654545 0.072727 0 0.654545 0.072727 0 0.672727 0.072727 0 0.672727 0.072727 0 0.690909 0.072727 0 0.690909 0.072727 0 0.709091 0.072727 0 0.709091 0.072727 0 0.727273 0.072727 0 0.727273 0.072727 0 0.745455 0.072727 0 0.745455 0.072727 0 0.763636 0.072727 0 0.763636 0.072727 0 0.781818 0.072727 0 0.781818 0.072727 0 0.8 0.072727 0 0.8 0.072727 0 0.818182 0.072727 0 0.818182 0.072727 0 0.836364 0.072727 0 0.836364 0.072727 0 0.854545 0.072727 0 0.854545 0.072727 0 0.872727 0.072727 0 0.872727 0.072727 0 0.890909 0.072727 0 0.890909 0.072727 0 0.909091 0.072727 0 0.909091 0.072727 0 0.927273 0.072727 0 0.927273 0.072727 0 0.945455 0.072727 0 0.945455 0.072727 0 0.963636 0.072727 0 0.963636 0.072727 0 0.981818 0.072727 0 0.981818 0.072727 0

it will probably work but I prefer to keep additions separate hence "just add dic & aff user files in C:\ProgramData\Affinity\Common\1.0\Dictionaries\en-GB" you'll have to create the en-GB directory Yes. Experimentation is the word when it comes to this, make notes of where you modify the main files and if it goes wrong you can always revert. What I have described will be simple to the experts but it took me a g e s and a g e s to work it out

Based on V1 and using English en-GB under windows Adding extra words is fairly trivial, just add dic & aff user files in C:\ProgramData\Affinity\Common\1.0\Dictionaries\en-GB Attached files contain a few photographic terms What annoyed me was that daguerre wasn't flagged as an error. The main dictionary contains Daguerre/M and daguerreotype/DSMG so whether that caused confusion I'm not sure but I cracked it by including Daguerre/W in photo.dic with a rule in photo.aff of KEEPCASE W You can't add user hyphenation dictionaries but need to modify the main file in C:\Program Files\Affinity\Publisher\Resources\Dictionaries\en-GB probably best to keep the old file as a backup in case it all goes wrong Additions to hyph_en_GB.dic photo5micro5graphy photo5sens5itive Another annoyance was photography hyphenating to pho-tography. It may be acceptable to some but not to me So, at the bottom of hyph_en_GB.dic LEFTHYPHENMIN 4 photo Now it works to my satisfaction but photon won't hyphenate to pho-ton, I can live with that What I can't fix is Wi-Fi, the main dic shows WiFi which is wrong as it's a trademark so a proper noun. Anyway, I changed that to Wi-Fi. Now I see an error if I type wifi and the suggestion is Wi-Fi, so I click that and Wi-Fi appears but still shows as an error. Weird or what? There is much scope for editing this stuff but be prepared for headaches, I haven't found a definitive guide to editing hyphen files photo.dic photo.aff

I think that's a Mac limitation Mike, this windows11 box has three extra dictionaries for en-GB and they all work. Anyway, I'm up to my eyeballs with hyphenation at the moment, that's a proper challenge

New batch job seems the way to go but bear in mind that results may need to be sharpened after downsizing You can create a macro to sharpen an image then use that in a second batch to sharpen the results from the first If you apply the sharpen macro in the resizing batch job then that will happen before the resize which isn't what you need

The Help re. data merge is pretty good. I have shown how to strip the file extension If the OP can reply with particular problems with Publisher data merge then they can be addressed but the signature needs to be fixed first

Neither can I My tuppence worth Hard to say without knowing the construction of your image and what output format you need If the specific object is a vector shape then you could export as svg and use scripting to change colours and write new svgs If it's a raster image and you want to recolour a region then you could try imagemagick with connected-components

You should be able to do that with data merge Use the spreadsheet to strip the file extension Column B formula is =MID(A2,1,C2) Column C formula is =FIND(".",A2)-1

One can only use the tools at one's disposal, it ain't like css FontMargins.html

Set the spacing based on the font size, so for a 14pt font set the left indent at 28pt

Dunno how the program works If there's an image in memory and then there's a command to do something, how Photo decides how much of the image to lay off to disk or whether that's handled by the OS in the swapfile. I suspect that it asks the OS for more memory and the OS says yeah sure but it'll be on the disk My example of drawing a line on an image that was about as large as the memory could hold caused all sorts of disk thrashing or whatever ssd's do, the fan went nuts anyway So my simple understanding is that once you're out of ram get some popcorn and be prepared for a long weight (old English industrial joke, sorry)