Hello,
I am using the latest 2.0.0 version and I believe uri::decode is not behaving as expected. For example the code
```
utility::string_t text = web::uri::decode(L"J'ai+besoin+de+trouver+un+personnage+%C3%A9trange");
```
I expect to return "J'ai besoin de trouver un personnage étrange" and not "J'ai+besoin+de+trouver+un+personnage+étrange".
Is this the expected behavior or a bug?
Thanks,
Pedro
Comments: Hi Steve, Actually you are right and I believe we also found a minor bug in our JS library not properly encoding the URL. Having a decode_plus might help, but I am not sure how generalizable it would be. Btw, strangely .NET API ``` HttpUtility.UrlEncode("J'ai besoin de trouver un personnage étrange") ``` generates this "J%27ai+besoin+de+trouver+un+personnage+%c3%a9trange" I guess you can close this as by design. Thanks, Pedro
I am using the latest 2.0.0 version and I believe uri::decode is not behaving as expected. For example the code
```
utility::string_t text = web::uri::decode(L"J'ai+besoin+de+trouver+un+personnage+%C3%A9trange");
```
I expect to return "J'ai besoin de trouver un personnage étrange" and not "J'ai+besoin+de+trouver+un+personnage+étrange".
Is this the expected behavior or a bug?
Thanks,
Pedro
Comments: Hi Steve, Actually you are right and I believe we also found a minor bug in our JS library not properly encoding the URL. Having a decode_plus might help, but I am not sure how generalizable it would be. Btw, strangely .NET API ``` HttpUtility.UrlEncode("J'ai besoin de trouver un personnage étrange") ``` generates this "J%27ai+besoin+de+trouver+un+personnage+%c3%a9trange" I guess you can close this as by design. Thanks, Pedro