PDF XChange Forum

Here is a PDF with a wrong formatted link in the upper right corner: it should be a mail-link, but now it is a "semi formatted web-link".

PDF Viewer tries to handle it and displays an error message, Editor does nothing.

Maybe that's an example to check the handling of this kind of semi-errors ("semi" because browsers can handle it).

regards

Peter

Hi Peter,

Thanks for the post - Can you send a screen-shot of what you're seeing? The two email addresses are not formatted as links at all, for me.

Cheers,

I suppose the semi-handling of the URL in PDF-XChange Viewer is because it interpretes "office @ austrosteel.at" as a link, while it should not (do so).

At my opinion the problem is only due to the (one) spacing character before and the one after the ampersand.
When you remove these spaces, everything works like expected.

So, the correctly formatted e-mail address is "office@austrosteel.at".

Best regards.

Hi Willy,

Have just checked the Viewer here and it looks like it incorrectly recognizes the link. However, this would not be changed as the Viewer is no longer under active development.

Both the Editor and Adobe do not recognize this as a link and rightly so, as there are spaces between different parts of the link. Once these spaces are removed, the Editor and Adobe both handle these links correctly.

Cheers,

What I wanted to say is that links like this - without http, without www - can happen sometimes. And although they are "wrong", the software could be a bit of fault-tolerant and suppose "this could be a http://www.... link".

Viewer nearly gets it (the first message shows that it realizes it as a link), Editor realizes nothing. So maybe this could be improved (at least with an informative dialogue instead of doing nothing).

Here is what I see (and I'm sure you see the same thing):
http://autode.sk/1Tf72hr

Peter

Hi Peter,

As mentioned in my previous post, that is exactly what I see, but the Editor handles this correctly. This should not be recognized as a link, as recognition of links formatted in such a manner, will cause the Editor to incorrectly recognize other text as links.

i.e. system.out.prtln <-- That is a small snippet of some simple Java code. In instances such as that, it's extremely difficult, if not impossible, to programmatically differentiate between austrosteel.at and system.out.prtln.

Adobe does not recognize this link either and for the same reason. The only links that will and should automatically be parsed (provided the options to do so are enabled) are the following:

- Literal links (i.e. http://, https://, wwww., test@test.com, etc.).
- IP addresses (i.e. 192.111.1.01)

Thanks,

However, it is possible to ask that such links
_ _
in the "Type the URL" field of the "Add Action: "Open a Web Link"" dialog box be interpreted by the PDF-XChange Editor application as "https://..." rather than "file :///..."?

Hello, Jensen Head

I am afraid not, this is dictated by the PDF Spec, and you will see adobe does the same, we need to ensure consistency with our competitors in this particular area. If you wish to make a web-link point to an external location, simply include the "http://" or "Https://" before the URL in question, and then the link functions in any spec respecting software (including us and Adobe) will work as desired: Kind regards,

TrackerSupp-Daniel wrote: ↑Wed Jan 18, 2023 9:23 pmyou will see adobe does the same

I've seen many times that Adobe is too big to keep bugs out of their products (and they do, and the old bugs have been in their products for years, passing from version to version). And I have seen many times that you do something better than Adobe does, even if it violates their status as an ideal team and an ideal product (no, both statements are not true). I mean, don't look up to Adobe. Be better than them. Their product has long stopped in its development. He has not offered anything fundamentally new for a long time. It has become ossified and is degrading to the casual level of housewives. Please stop limiting yourself to the level of Adobe. Let them realize that you have outstripped them for a long time, and try to catch up with you. Or admit that they themselves are not able to do it.

Hello Jensen Head,

We appreciate the kind words!
When we see that something can be done better, and are allowed to do so without stretching or even breaking the PDF specification - we would consider doing so. But in this instance Dan is right that there is a prescribed default behaviour, and that has to be followed.
The PDF specification was initially written by Adobe, but it is now an ISO spec on it's own - and any respectable software like ours would need to adhere to the ISO definitions at 100%.

Kind regards,
Stefan