X-Google-Thread: 13235db79e,920ee30987089f7e X-Google-Attributes: gid13235db79e,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news-out.readnews.com!news-xxxfer.readnews.com!panix!qz!not-for-mail From: Eli the Bearded <*@eli.users.panix.com> Newsgroups: alt.ascii-art Subject: Re: Xpn with ascii-art group Date: Thu, 4 Feb 2010 07:15:57 +0000 (UTC) Organization: Some absurd concept Lines: 70 Message-ID: References: NNTP-Posting-Host: panix5.panix.com X-Trace: reader2.panix.com 1265267757 11757 166.84.1.5 (4 Feb 2010 07:15:57 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Thu, 4 Feb 2010 07:15:57 +0000 (UTC) X-Liz: It's actually happened, the entire Internet is a massive game of Redcode X-Motto: "Erosion of rights never seems to reverse itself." -- kenny@panix X-US-Congress: Moronic Fucks. X-Attribution: EtB Encrypted: double rot-13 User-Agent: Vectrex rn 2.1 (beta) X-Comments: "(Welcome to the desert of the real.)" -- eck@panix "... terrorism is open-source war ..." -- srini@unamerican Xref: g2news1.google.com alt.ascii-art:1446 In alt.ascii-art, Daniel Berger wrote: > Anyone using XPN as a client? It underlines everything between _and_ for > me. Which screws up ascii arts. Anyone knows how to turn this off? Several clients do that. And other effects. I've never used XPN, so I don't know how to disable it there. *Bold* (with asterisks) /Italics/ (with slashes) _Underlining_ (with underscores) ObAA: Here's a bit of practical ASCII art I did several years ago. One of the wheels on my bike had become fairly badly warped. Investigation revealed a broken spoke. So I called up my friend Marc, who is much better at bike repair than I am, and talked to him about it. The general theory is that the spokes alternate going to the left and right side in the center, so when one is loose or broken the tightly attached spokes from the other side pull the rim in that direction. _ /' '\ |. .| <- Tire \~/ <- Rim T <- Spoke nipples | .^, <- Spokes (two, overlapping at top) | | .| |, | | [===] <- Axel Above, the wheel in cross-section. Below in profile (imagine it to be rounded instead of straight -- I'm being lazy with the ascii-art). Key: ! nipple of broken spoke T nipple of incidental spoke 7 nipple of spoke to tighten Y nipple of spoke to loosen #^#^#^#^#^#^#^#^#^#^#^#^#^#^#^#^#^#^#^#^#^#^#^#^#^#^# INFLATE TO 85 PSI _____________________________________________________ T Y 7 Y 7 ! 7 Y 7 Y T | | | | | | | | | | | | | | | | | | | | | | (a) (b) (c) (d) (d) (c) (b) (a) a: loosen a very little b: tighten a little c: loosen a little b: tighten most (1/2 turn or so) All fine in theory, in practice it is easy to lose track of whether clockwise or counterclockwise is tightening, and what needs to be done to what spoke. Marc told me that he had never successfully 'trued' a wheel himself. He always made things worse. I managed to keep myself from being confused by using a Sharpie (permanent felt tip marker) to note on the rim what needed to be done for each spoke. So after about twenty minutes of planning and work my wheel is a lot more balanced. Elijah ------ finds sharpies indispensible