On servers using for example fr_FR.UTF-8 file system encoding, Piwigo API methods return non percent-encoded URLs (containing spaces, accentuated characters, etc.). This requires third party apps to "guess" how to percent-encode each URL so that images can be downloaded.
So would it be possible to [percent-encode URLs](url https://tools.ietf.org/html/rfc3986#section-2) so that Piwigo always returns RFC compliant URIs whichever file system encoding is used?
On servers using for example fr_FR.UTF-8 file system encoding, Piwigo API methods return non percent-encoded URLs (containing spaces, accentuated characters, etc.). This requires third party apps to "guess" how to percent-encode each URL so that images can be downloaded.
So would it be possible to [percent-encode URLs](url
https://tools.ietf.org/html/rfc3986#section-2) so that Piwigo always returns RFC compliant URIs whichever file system encoding is used?
<!-- github-sync-id:369825154 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On servers using for example fr_FR.UTF-8 file system encoding, Piwigo API methods return non percent-encoded URLs (containing spaces, accentuated characters, etc.). This requires third party apps to "guess" how to percent-encode each URL so that images can be downloaded.
So would it be possible to [percent-encode URLs](url
https://tools.ietf.org/html/rfc3986#section-2) so that Piwigo always returns RFC compliant URIs whichever file system encoding is used?