6 ms·
Just because your users are dealing with logfiles, their users should still be able to use č ƒ ø or whatever unicode character in the filename or url - which wi
by selectnull 10y ago
Just because your users are dealing with logfiles, their users should still be able to use č ƒ ø or whatever unicode character in the filename or url - which will consequently end up in a log file.
- viraptor 10y agoMost logs are actually bytestrings. If they include user-controlled strings, they will likely have to be parsed as binary blobs to accommodate that.
- 1ris 10y agoMany logs are localised - and contain unicode.
- viraptor 10y agoThere's a difference though. Does the log format itself in some unicode encoding, or does it just embed some utf-X encoded strings? If you just embed some user input and assume it will decode properly, you're likely to run into issues at some point when someone provides explicitly-broken encoding.
- jcranmer 10y agoTrue story: I once broke build automation by including non-ASCII text in the commit message. Just because something is internal doesn't mean that it won't have Unicode.