On 02.09.2017 17:17, Branko Čibej wrote:
On 02.09.2017 17:12, [email protected] wrote:+svn_boolean_t +svn_utf__fuzzy_glob_match(const char *str, + const apr_array_header_t *patterns, + svn_membuf_t *buf) +{ + const char *normalized; + svn_error_t *err; + int i; + + /* Try to normalize case and accents in STR. + * + * If that should fail for some reason, continue with the original STR. + * There is still a fair chance that it matches "*.ext" pattern despite + * being "broken" UTF8. */What evidence do you have for this statement? It is, quite frankly, completely bonkers. "Broken," as you put in quotes, means it's not UTF-8. What kind of UTF-8 do you think there's a fair chance it'll match then?
I've encountered old repositories where some path names were apparently not converted properly into UTF8 but contained whatever locale-based strings the client sent. Those would still match "*.someExtension" and similar patterns despite having non-UTF8. I would like to cover those as well. I see 3 options here: 1. Make these cases a non-match, hiding them in the output. 2. Handle these cases in the callers, duplicating that part. 3. Keep it as it is. -- Stefan^2.
