> > > > (...) > > > > Does bacula support UTF-8 ? > > Yes, but there are problems with PostgreSQL. I assume that > these problems are due to the fact that users can create or > have created non-UTF-8 filenames, but I am not sure.
They are. PostgreSQL will validate that input into a UTF-8 database is actually UTF-8, and since bacula performs no conversion of character sets, the filenames have to be UTF-8 to work. You can switch the datbase to SQL_ASCII instead of UTF-8 to get rid of this verification. This will of course get rid of things like encoding specific sorting as well,b ut there is no way to deliver that properly for invalidly encoded data anyway. > Note, Bacula consoles display/input characters correctly > (WYSIWYG) *only* if everything is UTF-8 (on *nix machines). Doesn't it display it correctly as long as the encoding that bacula runs under is the same as the file? I think that's what I've been seeing, but I could be remembering wrong. Meaning if you run the console on the same machine that files are on, the filenames should look the same? //Magnus Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
