User talk:DannyS712/Easy-link

Suggestion for improvement
Hi - I like this new tool a lot. I think however that I might use it more if the links were available next to each heading - for instance, the headings display for me "History [edit|edit source]" and could display "History [edit|edit source|link]" which would be more accessible, especially for a section very far down the page, away from the current button on the menu. Is that do-able? ɱ (talk) 16:30, 31 March 2019 (UTC)
 * I use User:BrandonXLF/FloatSide.js, which means that the button is never far away - let me think about it. I don't know how to do that on a per-section level, and I'd rather keep it simple. Thanks, --DannyS712 (talk) 16:36, 31 March 2019 (UTC)
 * I could try that as a fix, could be mentioned in the instructions as an option. Just I think this tool is most useful for linking sections, so why not have it by the section headings? If possible... Thank you, ɱ  (talk) 16:42, 31 March 2019 (UTC)
 * This also only selects sections if you click on them in the TOC, which I don't often do; I think most would want a link from where they are in the section. Scrolling up to the TOC and then clicking the section and then Easy Link adds two steps. ɱ  (talk) 16:45, 31 March 2019 (UTC)

Handling special characters
Would it be possible for this script to convert URL entities to Unicode characters? For example, here, the script grabs Tr%E1%BB%8Bnh%E2%80%93Nguy%E1%BB%85n War when it would be better to grab Trịnh–Nguyễn War. Eman 235 / talk  05:29, 17 May 2019 (UTC)
 * Yeah, that's been bugging me too, but converting unicode from utf isn't the easiest as far as I know. If you have any suggested implementations, let me know; if not, it may be a while --DannyS712 (talk) 05:32, 17 May 2019 (UTC)
 * Hm, AutoEd appears to use this script (see "Task 2: Replace numeric html entities with unicode"). Eman  235 / talk  00:07, 29 May 2019 (UTC)