# Oneboxing PDF: herschrijf URL-escaped tekens naar hun oorspronkelijke waarde

**URL:** https://meta.discourse.org/t/oneboxing-pdf-rewrite-url-escaped-characters-to-their-original-value/207719
**Category:** Feature
**Created:** [31 oktober 2021 om 13:51 UTC](https://meta.discourse.org/t/oneboxing-pdf-rewrite-url-escaped-characters-to-their-original-value/207719 "2021-10-31T13:51:53Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![guidoleenders](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/guidoleenders/32/196268_2.png) [@guidoleenders](https://meta.discourse.org/u/guidoleenders)
#### Post date: [31 oktober 2021 om 13:51 UTC](https://meta.discourse.org/t/oneboxing-pdf-rewrite-url-escaped-characters-to-their-original-value/207719/1 "2021-10-31T13:51:53Z")

</div>

When a PDF is oneboxed, the URL is used to determine the onebox contents (see [Oneboxing of PDFs and other attachments](https://meta.discourse.org/t/oneboxing-of-pdfs-and-other-attachments/55972)). The URL seems to be used as basis of the contents.

However, characters that are special for a URL do not seem to be correctly translated.

For example, the URL [https://documentation.invantive.com/2017R2/exact-online/Exact%20Online%20API%20Data%20Model.pdf](https://documentation.invantive.com/2017R2/exact-online/Exact%20Online%20API%20Data%20Model.pdf) leads to box with “%20” in it:

 ![Onebox translation error Exact Online data model](https://global.discourse-cdn.com/meta/original/3X/4/7/475192351134051a1e2e6089fcf0f56de39a25f2.png)

I propose to rewrite the escaped characters back to their original character, such as “Exact Online API Data Model.pdf” in this case.