On Tue, May 29, 2007, Paul J Stevens <[EMAIL PROTECTED]> said: > Aaron Stone wrote: >> On Tue, May 29, 2007, Marc Dirix <[EMAIL PROTECTED]> said: >> >>> *** dbmail-sievecmd *** >>> Opening connection to database... >>> Opening connection to authentication... >>> Ok. Connected! >>> May 29 20:35:52 Error:[sql] dbpgsql.c,db_query(+284): query failed >>> [INSERT INTO >>> dbmail_sievescripts (owner_idnr, name, script, active) VALUES (4,'@! >>> temp-script! >>> @', ' >>> require "vacation"; >>> require "fileinto"; >>> vacation >>> :days 1 >>> :subject "Out of Office Reply" >>> "Test vacation note. >>> >>> This is an u with '':ü >>> This is an e with '': é >>> This is an a with ^: â >> >> Are these latin1 or utf8 from your terminal? There aren't any conversions >> taking place in dbmail-sievecmd; it's basically a dumb tool for accessing >> the dbmail_sievescripts table. > > yes, but it needs to be a bit less dumb then. The infrastructure for > recoding strings is in up and running for messages. The same can (and > should) be done for sieve scripts, usernames, aliases, and anything else > that goes into the database. > > A nice little todo for a future milestone I guess.
If it is possible to ask the terminal what encoding it is using, OK, otherwise it's a best-guess. You recently did implement best-guessing for message data, so perhaps you're right that we should do that. Aaron _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
