Problem with hotspot and web link

HCL Domino Domino Forum
1

Hi,

I have a Support call from the client that has an issue with accent in French. the links work fine on the web, but if he put that link on a Link Hotspot I can see the link being good, yet when launched it gives a problem with changing the accents.

Here is an example. http://ABC/ABCintranet.nsf/ContentF/examinateur?open&lang=F&count=10&category=01_Matériels+médicaux@

when I clique this link on the web it works fine but when I clique the hotspot then on the web I get this;

http://ABC/ABCintranet.nsf/ContentF/examinateur?open&lang=F&count=10&category=01_Matériels+médicaux@

is there a way to keep the link as is from the hotspot so that it does not change the accents when launching the link?

any ideas,

thanks

Alena

2

Subject: problem with hotspot and web link

If the link works, there is nothing wrong with the link. URLs cannot use the accented characters, so they have to be URL-encoded (the browser does that automatically when you click the link).

3

Subject: RE: problem with hotspot and web link

ok so when the user clicks on the left navigator of the web site in French the url ends up being http://ABC/ABCintranet.nsf/ContentF/examinateur?open&lang=F&count=10&category=01_Matériels+médicaux@

that works well…

But if the user enters that link in a hotspot in an email as the same link http://ABC/ABCintranet.nsf/ContentF/examinateur?open&lang=F&count=10&category=01_Matériels+médicaux@ you would think that it works well , but when the user clicks on the Hotspot Notes modifies it to http://ABC/ABCintranet.nsf/ContentF/examinateur?open&lang=F&count=10&category=01_Matériels+médicaux@

then somehow the page is not recognized as it should say http://ABC/ABCintranet.nsf/ContentF/examinateur?open&lang=F&count=10&category=01_Matériels+médicaux@

4

Subject: RE: problem with hotspot and web link

It should work regardless. In fact, the entire URL (after the protocol, server, and server root virgule) could consist of nothing but escaped characters and the server should be able to recognize it. There is, however, no guarantee that accented characters would make it through every hop in the request path.

Oh – I just noticed that you have %A9 for the e-acute. It should be %E9. Maybe a charset issue?