On Sat, May 21, 2005 at 09:21:01AM +0200, [EMAIL PROTECTED] wrote: > Hi, > > can anyone tell me why when setting utf-8 for cmd.exe, gpg switches back to > its default character set. In cmd.exe I do the follwoing to change the > codepage: > > chcp > > For Windows XP Pro wiht German locale and True Type Font Lucida Console in > cmd.exe set this gives the OEM-Multilingual Latin I charset: > > Active Codepage: 850. > > Entering chcp 650001 (which stands for UTF-8) results in: > > Active Codepage: 65001. > > I now try for example to clearsign a UTF-8 encoded text file with gpg in > verbose mode: > > gpg -vvv --clearsign test.txt > > The program's first response is: > > gpg: conversion from `utf-8' to `CP65001' not available > gpg: using character set `iso-8859-1' > > What kind of setup (charset, file encoding) would you recommend in general. > I thougt that gpg fully supports UTF-8. At least according to the manpage.
>From the error message I would guess that either `CP65001' is not as standard as it aught to be, or your setup is missing a DLL for charset conversion. There was a thread about charsets roughly half a year ago, have a look in the archives. http://lists.gnupg.org/pipermail/gnupg-users/ has one file per month, and http://lists.gnupg.org/pipermail/gnupg-users.mbox/ has a single mbox file of the whole archive. HTH //Samuel _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
