Here are some remarks how to use Internet standards in programming and documentation.
RFC === The only source for internet standards (RFC) is IETF and the website ietf.org. You can get all the RFCs here: ftp://ietf.org/rfc/ and all current drafts here: ftp://ietf.org/internet-drafts/ For example: ftp://ietf.org/rfc/rfc-index.txt - list of all RFCs and their status ftp://ietf.org/rfc/std-index.txt - list of all standard track RFCs ftp://ietf.org/rfc/RFCs_for_errata.txt - list of all RFCs with errata ftp://ietf.org/rfc/rfc4180.txt - Common Format and MIME Type for Comma-Separated Values (CSV) (Status: INFORMATIONAL) ftp://ietf.org/rfc/rfc1855.txt - Netiquette Guidelines (Status: INFORMATIONAL) ftp://ietf.org/rfc/rfc5321.txt - Simple Mail Transfer Protocol (SMTP) (see errata) ftp://ietf.org/rfc/rfc5322.txt - Internet Message Format (see errata) ftp://ietf.org/rfc/rfc5246.txt - The Transport Layer Security (TLS) Protocol Version 1.2 (see errata) ftp://ietf.org/rfc/rfc3977.txt - Network News Transfer Protocol (NNTP) (see errata) ftp://ietf.org/rfc/rfc5536.txt - Netnews Article Format (Usenet posts) ftp://ietf.org/rfc/rfc5537.txt - Netnews Architecture and Protocols (Usenet groups) ftp://ietf.org/internet-drafts/draft-ellermann-news-nntp-uri-11.txt - The 'news' and 'nntp' URI Schemes (to be RFC5538) RFC errata listing is generated here (ordered by RFC ids, 3 MB now): http://www.rfc-editor.org/errata_list.php For software developing only the current RFCs should be used, Non-standard solutions or obsoleted standards (eg. RFC 822 or RFC 2822) should be used only for compatibility reasons and clearly documented. Note that there are some unstandardized extensions in common use, such as PGPVERIFY mentioned in RFC 5537. Character sets ============== The names for charsets/codepages are registered by IANA here: http://www.iana.org/assignments/character-sets Note that the only names for Unicode charsets are written with dash (or standard ASCII hyphen/minus in text/plain): UTF-7, UTF-8, UTF-16, UTF-32. Only these names should be used in documentation. Use them also in developing whenever it is possible. Any other names (e.g. UTF8) should be used only for compatibility reasons and clearly documented. Microsoft naming convention use names: OEM - for DOS codepages (IANA registered IBMnnn, CPnnn charsets) ANSI - for Windows codepages (IANA registered windows-nnnn charsets) (letter A as the last letter in function name) WIDE - for UTF-16 charset (letter W as the last letter in function name) Only these names should be used in documentation. Note that "Unicode" name should never be used as a synonym for "UTF-16". -- Regards from The Harbour Project mirror in Poland Andrzej P. Wozniak ------ Darmowe statystyki stron www http://WEBstat.pl _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
