On Wed, Apr 22, 2015 at 11:16:21 -0700, Gavin Cannizzaro wrote: > What puzzles me is that Tup seems to be dealing with the correct bytes when > passing the command to the shell, but the issues arise when internalizing > the name for the graph database. > > I'd be happy to find that this was something I'm doing wrong though -- I > also have trouble FTP-ing those files :(
It appears Tup is trying to enforce an encoding for filenames in the database (which is probably from the schema used). On *nix, filenames are arbitrary byte strings (except NUL and '/') and there is no encoding specified (and using the locale environment is not trustworthy either). Windows *does* have an encoding for the filenames, but it is some bastardization of UTF-16, so probably also best treated as an array of arbitrary shorts there as well. --Ben -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
