Nothing. But that’s not human readable. I want the users to be able to read the url. hidr%C3%A1ulica is perfectly readable for a computer or a web developer. But a normal user will see that as an error. In latin america, replacing á with a in urls is the default. It’s so normal that actually, hidr%C3%A1ulica on a url is seen as an error, and from a clients perspective, it’s unacceptable. Normal users will never see that url and think: “oh, that’s fine… that’s just an accented a”. 
You know what I mean? It’s not a technical requirement.
Also, I may have explained poorly. I meant that http://localhost:1313/familias/hidráulica/ wouldn’t be a valid url. Not that http://localhost:1313/familias/hidr%C3%A1ulica is not valid. That’s perfectly valid because it is url encoded. I meant that parameterize and urlize don’t share the same purpose.
0.26. I would also expect that behavior as default. That’s why I see this as a possible improvement that would benefit many developers.
Again, thanks for your time and your help. I really appreciate it.