Date: Thu, 23 Jun 2022 04:14:40 -0400 From: grarpamp <grarpamp@gmail.com> To: freebsd-doc@freebsd.org Cc: postmaster@freebsd.org, freebsd-questions@freebsd.org, freebsd-current@freebsd.org Subject: Re: Posting Netiquette [ref: Threads "look definitely like" unreadable mess. Handbook project.] Message-ID: <CAD2Ti2-F7%2BZ3QtpV7PxfcbnaHXGLcFytRihv-cVWn=7qDdWsxw@mail.gmail.com> In-Reply-To: <20220623060320.aad6a631.freebsd@edvax.de> References: <CAD2Ti2_GFxRzAjgSwf55tC9c3jSUAzeR42xzhUgG87QZ7JT5_g@mail.gmail.com> <20220623030118.GA59423@eureka.lemis.com> <20220623060320.aad6a631.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>> the =C3=A2=E2=82=AC=C5=93> ;=C3=A2=E2=82=AC and leave empty lines betwe= en your text and the original > Seems there is a charset mismatch. > MUA displaying nonsense > Oh the joy of UTF-8... ;-) https://unicode-table.com/en/sets/quotation-marks/ The pages ... https://docs.freebsd.org/en/books/handbook/eresources/#eresources-mail https://docs.freebsd.org/en/articles/freebsd-questions/ https://docs.freebsd.org/en/articles/mailing-list-faq/ ... are intermixing standard ASCII double quotes with questionably gratuitous choice of using left and right double quotes via UTF-8, which then may get slaughtered by non UTF-8 enabled cut-paste, systems, lists, gui's, desktops, apps, and MUAs along the way. Perhaps smack the typeset within all pages back down to ASCII, except where no standard ASCII convention is available to substitute for symbols, ie: (c) is the fine sub for =C2=A9, and ASCII still fits within UTF-8 meta declarations, which may be needed for =E2=82=BF which has no ASCII substitute, and of course for presenting non ASCII languages. And perhaps systems can consider enabling UTF-8 if needed to render and handle things like =E2=82=BF, say for whenever foundation gets to accepting those easy donations and crowdfunding. No idea what the ';' in the '=E2=80=9C> ;=E2=80=9D' is doing there for. A proper page would need to add a number of the missing email formatting netiquettes (such as no HTML), and actual photo examples of former bad chaos and new good result, etc... to be considered a good format, subject, and addressing netiquette guide rule page. Consider if "FreeBSD Articles" is best hier for a page that may becoming more often directly linked or included into prospective list user's signup clickstream, quarterly admin, friendly cluebat hints, etc. And it's mostly written to apply only to -questions when it should be completely agnostic. So the pages may be currently serving lesser preventive or curative use as far as lists could go. > Unless there is a good reason to do otherwise, reply to the sender > and to FreeBSD-questions. Well for subscription-required-to-post lists, only list-reply is needed... which also follows address line bloat minimization, reduces personal reply issues, reduces "Stop copying me direct when I'm on list", etc. > Arguably these recommendations should be separated out into their own pag= e. Such soley dedicated content would make the page easier for people to link to wherever such reference is needed. The current pages don't, and they're bleeding [partially] duplicated and differing guidance content across each other. If the page was good enough, it would get picked up by search engines and other projects. [-current, and even -questions, could probably be dropped now, for -doc, or wherever else is best.]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD2Ti2-F7%2BZ3QtpV7PxfcbnaHXGLcFytRihv-cVWn=7qDdWsxw>