Hstrutz Posted January 11 Share Posted January 11 In Publisher when adding hyperlinks (for example email) to a document's object/text: how to also add/include a Subject line? Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted January 11 Share Posted January 11 (edited) 9 hours ago, Hstrutz said: how to also add/include a Subject line? You can try email@address.here.com?subject email@address.here.com?subject=the.subject which should work if there are no spaces in "the.subject". For spaces, you could try %20 which might work. Edited January 11 by walt.farrell Fixed the syntax. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
thomaso Posted January 11 Share Posted January 11 1 hour ago, walt.farrell said: You can try email@address.here.com?subject which should work if there are no spaces in "subject". Could you upload a PDF where it works for you? While the hyperlink opens a new email window I don't get a subject text filled (V1, mac, Outlook). Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
Staff Dan C Posted January 11 Staff Share Posted January 11 The mailto link needs a slightly different format( "email address"?subject="subject", using %20 for 'space' characters in the subject), as shown below: email@address.here.com?subject=This%20is%20a%20test Which when clicking on the link in the exported PDF, provides the following in Outlook for me: I hope this clears things up walt.farrell, _考槃 and thomaso 1 2 Quote Please note - I am currently out of the office for a short while whilst recovering from surgery (nothing serious!), therefore will not be available on the Forums during this time. Should you require a response from the team in a thread I have previously replied in - please Create a New Thread and our team will be sure to reply as soon as possible. Many thanks! Link to comment Share on other sites More sharing options...
thomaso Posted January 11 Share Posted January 11 37 minutes ago, Dan C said: ?subject="subject" Perfekt, thank you! Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
lacerto Posted January 11 Share Posted January 11 Perhaps there is some reason for making this feature less powerful in version 2, but at least in Windows 1.x version (1.10.6), the full email url syntax was still supported and worked without any obvious issues: Note how in the body part even line break works. Perhaps there was some security concern, or possibly IDML compatibility based cause (as InDesign only supports the sender address and subject line)? Quote Link to comment Share on other sites More sharing options...
Staff Dan C Posted January 11 Staff Share Posted January 11 I'm not personally aware of any changes between supported Email Hyperlink properties between V1 and V2, however testing the same email hyperlink shown in your above screenshots fails to be accepted in 2.3 - it appears as soon as there are multiple '@' symbols within the Hyperlink, Publisher deems this invalid. I'm getting this logged with the team now, as it may be an oversight of the panel, rather than a decisive removal lacerto and MikeTO 2 Quote Please note - I am currently out of the office for a short while whilst recovering from surgery (nothing serious!), therefore will not be available on the Forums during this time. Should you require a response from the team in a thread I have previously replied in - please Create a New Thread and our team will be sure to reply as soon as possible. Many thanks! Link to comment Share on other sites More sharing options...
lacerto Posted January 11 Share Posted January 11 49 minutes ago, Dan C said: it appears as soon as there are multiple '@' symbols within the Hyperlink, Publisher deems this invalid Note though that it (both versions 1 and 2) still accepts multiple email addresses separated by a semicolon (the delimiter might depend on regional settings?) so it is not just the number of addresses as parameters, but possibly a deliberate omission of cc and bcc fields (probably not very often needed, though bcc can be quite convenient sometimes). Dan C 1 Quote Link to comment Share on other sites More sharing options...
Hstrutz Posted January 11 Author Share Posted January 11 Thanks, I will try that complicated coding, which in Indesign (sorry to mention this application again) is an included user friendly option. Also "Alt" is available in the URL part of hyperlinking. Dan C 1 Quote Link to comment Share on other sites More sharing options...
Hstrutz Posted January 11 Author Share Posted January 11 Dan C and walt and tomaso and others, thanks, I tested "email@address.here.com?subject=This%20is%20a%20test" and it worked, a temporary workaround until the developers will make this more user friendly walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
lacerto Posted January 12 Share Posted January 12 15 hours ago, Dan C said: I'm getting this logged with the team now, as it may be an oversight of the panel, rather than a decisive removal @Dan C, I just ran another test, and if you replace the @ signs in cc and bcc with %40, all the mail fields work fine, and you can have multiple receiver addresses marked with @, so having email@address.here.com;another@mail.com;third@testing.com?subject=This%20is%20a%20test&cc=secondary%40mail.com&bcc=hidden%40mail.com&body=This%20is%20body%20text entered in the Email-type of Hyperlink box, gives you this: The screenshot above is from macOS Mail (Sonoma 14.1.2), but it works the same on Windows (Outlook in latest Office 365 on Windows Pro 11 tested). So the only difference to version 1 seems to be that in version 2 the additional parameters &cc and &bcc require the @ sign to be url coded as %40. Quote Link to comment Share on other sites More sharing options...
Staff Dan C Posted January 12 Staff Share Posted January 12 6 hours ago, lacerto said: So the only difference to version 1 seems to be that in version 2 the additional parameters &cc and &bcc require the @ sign to be url coded as %40. Many thanks for letting me know! I'll be sure to update the developers with this information now, as I'm not 100% certain of the expected behaviour when entering an Email Hyperlink in V2 - personally I'd expect both '@' and '%40' to be supported Quote Please note - I am currently out of the office for a short while whilst recovering from surgery (nothing serious!), therefore will not be available on the Forums during this time. Should you require a response from the team in a thread I have previously replied in - please Create a New Thread and our team will be sure to reply as soon as possible. Many thanks! Link to comment Share on other sites More sharing options...
lacerto Posted January 12 Share Posted January 12 1 minute ago, Dan C said: personally I'd expect both '@' and '%40' to be supported Yes, it is not clear why this changed (but is still supported when entering multiple receiver addresses) -- perhaps it is related to just requiring in actual parameter part only valid url-encoded special characters, and accordingly spaces, too, needing to be encoded (version 1 allowed space characters e.g. in at least the subject parameter). Quote Link to comment Share on other sites More sharing options...
Staff Affinity Info Bot Posted March 11 Staff Share Posted March 11 The issue "Email Hyperlinks with multiple email addresses (CC & BCC) fail to validate / export" (REF: AF-1736) has been fixed by the developers in internal build "2.5.0.2317". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.