url encoding in links

OK So I am trying to add a link using some basic URL encoding to allow a user of an exported PDF to share a message with a link in it on WhatsApp.


The link looks something like this:


https://wa.me/?text=Hi%20have%20a%20look%20at%20this%20awesome%20link%20https%3A%2F%2Fwww.example.com%2F%3Futm_source%3Dsomesource%26utm_medium%3Dsome_medium


So it turns out that adding this kind of link works just fine in pages 5.6.2.


However, in pages 8.0 it insists on trying to decode the url I have embedded in the text element of the link breaking the Google Analytics utm tracking which contains special characters like ? and &.


This is so frustrating. I am forced to maintain outdated OSs because I am worried I will keep losing valuable functionality like this. Starting to feel a bit like Windows user.


Can you stop pages from autocorrecting this?


Apple if you are listening please stop breaking excellent tools like this. I can't even add links in Preview anymore. sad face.


Any sensible solutions to this would be most welcome.

MacBook Pro 13", macOS 10.13

Posted on May 22, 2019 1:51 PM

Reply

Similar questions

3 replies

May 23, 2019 4:51 AM in response to obbila

What your link is attempting to do is invoke an unregistered URI protocol (whatsapp://) in Safari and the browser is rejecting it. It is also referring to a secondary URI within that URL which may or may not be supported in this context. The primary problem is that unregistered protocol which is a different problem from URL percent encoding which as encoded, Pages passes into the exported PDF.


Firefox 67 is more informative:



Tested with Pages 8.0 on Mojave 10.14.5. I do not have any WhatsApp application installed, if there is one for macOS.

May 23, 2019 5:34 AM in response to VikingOSX

If you open this on an iphone or an android device when the link is encoded properly it works fine and WhatsApp is opened with the message and the appropriate link in the message (PDF generated using pages 5)


An iphone also shows you the link before you open it. In the text region for the nested link you can see that the % encoding has been converted to standard text (PDF generated with pages 8) !!! This is the link in the PDF. Anyway as Barry mentioned I should send Apple feedback, will do.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

url encoding in links

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.