URL convert # sign to %23
See original GitHub issueI have issue with converting #
within URL:
Example:
<a href="https://speakasap.com/ru/cz/seven/1/#exercises">Try it</a>
weasyprint generates wrong link: https://speakasap.com/ru/cz/seven/1/%23exercises instead of https://speakasap.com/ru/cz/seven/1/#exercises
Means sign #
is converted by weasyprint to %23
There is only manual workaround: https://community.adobe.com/t5/acrobat/ist-replaced-by-23-in-urls-gt-error-404/td-p/5811448?page=1 (if weasyprint uses some Adobe API?)
_Originally posted by @speakASAP in https://github.com/Kozea/WeasyPrint/issues/1121#issuecomment-665544600_
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
URL Decode and Encode - Online
Decode from URL-encoded format or encode into it with various advanced options. Our site has an easy to use online tool to convert...
Read more >The '#' char gets converted to %23 causing the GET Request ...
I use URLComponents with URLQueryItems to build the request URL. During this process the # char gets converted to %23 which I think...
Read more >HTML URL Encoding Reference - W3Schools
Character From Windows‑1252 From UTF‑8
space %20 %20
! %21 %21
" %22 %22
Read more >How to prevent '#' from getting converted to '%23' in URL?
A webpage launched from terminal, via a URL containing a # , has the # character converted to %23 . I want the...
Read more >Opening google url with hash (#) fails; gets converted to %23
macos - Opening google url with hash (#) fails; gets converted to %23 - Super User. Stack Overflow for Teams – Start collaborating...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You’re not the only one: https://discussions.apple.com/thread/251041261
I see now. Thanks for help!
I use Apple Preview Version 11.0 (999.4) for opening PDF - INCORRECT Also I tried Safari Version 13.1.1 (15609.2.9.1.2) - INCORRECT
But Google Chrome opened it correctly - I just checked.
Seems it is an issue with Apple but not with the WeasyPrint…
Many thanks guys!