1
0
mirror of git://git.gnupg.org/gnupg.git synced 2024-07-03 02:58:57 +02:00

UTF-8 uid, OS X sed problems

This commit is contained in:
Nils Ellmenreich 2001-06-13 13:07:48 +00:00
parent 01fe1dd2a9
commit 505527a4ae
2 changed files with 36 additions and 4 deletions

21
doc/FAQ
View File

@ -2,8 +2,8 @@
GNUPG FREQUENTLY ASKED QUESTIONS
Version: 1.4
Last-Modified: Jun 2, 2001
Version: 1.5
Last-Modified: Jun 13, 2001
Maintained-by: Nils Ellmenreich <nils 'at' gnupg.org>
@ -88,6 +88,8 @@ you could search in the mailing list archive.
6.14) Some dates are displayed as ????-??-??, why?
6.15) I still have a problem. How do I report a bug?
6.16) Why doesn't GnuPG support X509 certificates?
6.17) Why do national characters in my user ID look funny?
6.18) I get 'sed' errors when running ./configure on OS X ...
7. ADVANCED TOPICS
7.1) How does this whole thing work?
@ -703,6 +705,21 @@ in it - why?
They are both public-key cryptosystems, but how the public keys are
actually handled is different.
6.17) Why do national characters in my user ID look funny?
According to OpenPGP, GnuPG encodes user id strings (and other
things) using UTF-8. In this encoding of Unicode, most national
characters get encoded as two- or three-byte sequences. For
example, &aring; (0xE5 in ISO-8859-1) becomes &Atilde;&yen; (0xC3,
0xA5). This might also be the reason why keyservers can't find
your key.
6.18) I get 'sed' errors when running ./configure on OS X ...
Please install GNU sed and use it instead of the broken OS X sed.
7. ADVANCED TOPICS
7.1) How does this whole thing work?

View File

@ -13,8 +13,8 @@ The most recent version of the FAQ is available from
[H H1]GNUPG FREQUENTLY ASKED QUESTIONS[H /H1]
Version: 1.4[H p]
Last-Modified: Jun 2, 2001[H p]
Version: 1.5[H p]
Last-Modified: Jun 13, 2001[H p]
Maintained-by: [$maintainer]
@ -672,6 +672,21 @@ in it - why?
They are both public-key cryptosystems, but how the public keys are
actually handled is different.
<Q> Why do national characters in my user ID look funny?
According to OpenPGP, GnuPG encodes user id strings (and other
things) using UTF-8. In this encoding of Unicode, most national
characters get encoded as two- or three-byte sequences. For
example, &aring; (0xE5 in ISO-8859-1) becomes &Atilde;&yen; (0xC3,
0xA5). This might also be the reason why keyservers can't find
your key.
<Q> I get 'sed' errors when running ./configure on OS X ...
Please install GNU sed and use it instead of the broken OS X sed.
<S> ADVANCED TOPICS
<Q> How does this whole thing work?