Re: found 2 issues with the currently available documentation

--===============5358091120630974338==
Content-Type: multipart/signed; boundary="=Steve_Case_IRA_NSA_Merlin_ASPIC_UOP_Blowfish_Lon_Horiuchi_Leuken-Bad";
	micalg=pgp-sha256; protocol="application/pgp-signature"

--=Steve_Case_IRA_NSA_Merlin_ASPIC_UOP_Blowfish_Lon_Horiuchi_Leuken-Bad
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 15 Nov 2017 09:08, [email protected] said:
> 1:
> On the page `https://www.gnupg.org/faq/whats-new-in-2.1.html`, there's a =
typo: "stroing", it should be "storing"

Thanks for reporting.  I just fixed that.

> The plain text version of the FAQ at `https://www.gnupg.org/faq/gnupg-faq=
.txt` doesn't send any charset header, and Firefox incorrectly assumes it's=
 something other than Unicode, as a result the text is garbled in certain p=
laces.

For a plain text file there is no easy way to describe the encoding and
thus Firefox should use a heuristic to figure this out.  If it gets it
wrong you can change it using View->Encoding->Unicode (or wherever the
current Firefox version has moved that menu item)

After all a web browser is from browsing HTML ;-)


Shalom-Salam,

   Werner

=2D-=20
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

--=Steve_Case_IRA_NSA_Merlin_ASPIC_UOP_Blowfish_Lon_Horiuchi_Leuken-Bad
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iHUEARYIAB0WIQTX/8BjtAoilLlm20f/gK6dHew1jQUCWgyTdgAKCRD/gK6dHew1
jc5nAQDwTkluoaPavr4oe50xZmP5+Z2vPvYq2BA+jcT8yPXlXQD9Edt3pjvI7oWg
Gk+rxtZy/4geTCpgdzktYm6lRv/bCAE=
=9AIC
-----END PGP SIGNATURE-----
--=Steve_Case_IRA_NSA_Merlin_ASPIC_UOP_Blowfish_Lon_Horiuchi_Leuken-Bad--



--===============5358091120630974338==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-doc mailing list
[email protected]
http://lists.gnupg.org/mailman/listinfo/gnupg-doc

--===============5358091120630974338==--