Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Ben Bacarisse Newsgroups: comp.programming,alt.algebra.help Subject: Re: on cut edges and bonds, graph theory Date: Mon, 25 Sep 2017 20:44:27 +0100 Organization: A noiseless patient Spider Lines: 40 Message-ID: <87fuba1s2s.fsf@bsb.me.uk> References: <86wp4w3sz5.fsf@toledo.com> <87shfjpzgs.fsf@bsb.me.uk> <878thaq4ff.fsf@bsb.me.uk> <87efr17b3g.fsf@bsb.me.uk> <87fubgghsi.fsf@bsb.me.uk> <87k20qb3vy.fsf@bsb.me.uk> <87shfd4j8m.fsf@bsb.me.uk> <87o9pz3hoe.fsf@bsb.me.uk> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="0dea31ff92109f8b226c93a98e025a0f"; logging-data="13717"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/FhZKjqBCSzXAeme3ONxd1XvBUGUPxrlM=" Cancel-Lock: sha1:xRyh3GiUvNZxVJIWPhDTFspqlEY= sha1:bB9o5KSGwJ9mDNJ+MjRARW2Jr/Y= Xref: csiph.com comp.programming:8052 alt.algebra.help:5035 William Elliot writes: > On Sun, 24 Sep 2017, Ben Bacarisse wrote: >> William Elliot writes: >> >> >> I didn't use any non-standard proprietary control characters. >> > >> >>> The book uses an over bar for that case: [S, S?~E]. >> >>> For [A, B] to be an edge cut, A ?~H? B = V, A ?~H? >> > >> > That is what is unreadable. What you see here is was cut and >> > pasted into this reply. On the screen, ? appears as a high-bit >> > blank, ~E appears as a single character, ctrl-E and ~H appears >> > as a single character, ctrl-H. What did you type to get that? >> >> I typed the Emacs command to insert a Unicode "COMBINING OVERLINE", a >> Unicode "UNION" and a Unicode "INTERSECTION" character. My Usenet >> client then decides on the most suitable encoding for the post which, in >> this case, had to be UTF-8. That decision is then announced by adding >> the appropriate header to the post. > > The decision is just a guess because it doesn't know all the different > readers used at usenet. No, it is not a guess. It picks the first in a specified list of character encodings that can validly represent all the characters in the post. When I post plain test it uses plain text. If I need a few accents it will use ISO-8859-1. In this case it had to use the most general UTF-8. The list is of my choosing (though I think I've kept the suggested default value) so no guess is involved at all. If I want to post for the lowest common denominator reader, I ask for my post to have Content-Type: text/plain (implied charset=us-ascii) and the software will tell me if I've used any non-ASCII characters and it will ask me what to do about them. The posting format was a fully-conscious, deliberate decision of mine. I knew there would be people using software that would not see the characters I had types. -- Ben.