In http://svn.haxx.se/dev/archive-2009-06/0165.shtml, C. Michael Pilato penned the following enlightening piece: > Do we not having a single function that can take a array of const char *, > native encoding path-spec arguments and return an array of structures that > contain a UTF-8 const char * path field and peg revision? Seems like we > could stand to have such a thing if we don't already. We could then have > helper functions that accept one of those structures and do other > transformations on it, such as expanding shortcut URLs (^/) and IRIs > ("http://server/path with spaces") into canonical form, and so on. > > I dunno ... I guess I just figured that after 9 years, we'd know how to > consistently parse our command-line arguments. This issue exists to track the task of making the above description reality. See also issue #3416 which prompted the discussion in the first place.