https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22223
--- Comment #19 from David Cook <[email protected]> --- Actually, after re-reading those specifications, I think maybe we *should* keep the "url" filter in the Template Toolkit template. If we consider the staff interface to be the "URI producer", then technically the problem is with storing URLs that contain encoded information. That said, maybe we would be better off storing encoded URLs in MARC 856$u, and then either passing those through to the interface with $raw, or decoding on the backend and then re-encoding using Template Toolkit. Technically, https://www.loc.gov/marc/bibliographic/bd856.html doesn't say anything about percent encoding, although all the examples contain percent encoded examples. That goes back to the URI standard that says a URI is always "encoded". Maybe we should be decoding it prior to putting it through the filter. Let me have a think about that... -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
