XPost: alt.comp.os.windows-10, alt.comp.microsoft.windows   
   From: marianjones@helpfulpeople.com   
      
   R.Wieser wrote:   
   >> So I agree with you that the essential trio was posted before I   
   >> was positive it worked in all cases - which it didn't - so I replaced   
   >> it.   
   >   
   > Next time its a good idea to either leave such an "the essential trio"   
   > conclusion out until you make sure, or include an "has yet to be tested"   
   > remark.   Now you have presented it as an "this is how it works" thing,   
   > which will only confuse the people who try to use it. :-|   
      
   Rudolph,   
      
   I agree with anyone who states a logically sensible view, where I agree   
   fully with you that I goofed by stating the trio would work for all cases.   
      
   I normally don't explain things like I'm going to, but I was getting ready   
   to go to the doctor's office for my sudden hearing loss and I was hurrying   
   to post the results of the tests which I had to back down from since I   
   published them too soon (as I found out in my own testing the trio   
   problem).   
      
   While we "can" eliminate the repetition of the six steps, for simplicity, I   
   fell back to the six-step method for each character to be translated to   
   ascii.   
      
   I'm sure if we looked at the problem we could do a dictionary lookup, but   
   the system is already working (and has worked for years) so there's no   
   reason to do so.   
      
   There's even likely a Windows program I can pipe my posts thru to do the   
   conversion, I'll wager, but I don't know of that program (so I wrote it).   
      
   In summary, thanks for catching that I was premature on the trio.   
   I've removed it in favor of the half dozen.   
      
   >   
   >>> Also, replacing something with itself doesn't really do much. :-)   
   >>   
   >> I'm not sure what you mean by that since the replacement is to change   
   >> Unicode characters (for the most part) into 7-bit ASCII characters.   
   >>   
   >> So, in the sense that a curly quote is changed to a regular quote, you   
   >> could argue it's replacing itself, but in reality it's a different   
   >> character.   
   >   
   > Nope, that isn't what I'm talking about : I see at least one replacement   
   > where the 1602 is the same as the 1601.  Not really usefull.   
      
   I thank you for all your suggestions, where I "think" I've implemented all   
   of them. Can you take a look at the file I posted yesterday with updates?   
      
   >   
   >> If you're on the Android newsgroup, you'll see more clearly why it   
   >> matters.   
   >> We've had a discussion about charset Usenet headers in recent days.   
   >   
   > I see that you are replacing slim double-quotes with single-quotes, but   
   > thats a matter of taste.  No matter what you do, that choice can work for   
   > you as easily as against you (ask yourself how I know.. :-) ).   
      
   What I'm replacing isn't for looks. It's for charset compatibility.   
   I don't care what a quote looks like, as long as it's a keyboard character.   
      
   >   
   >>> Seeing the "action" lines having four different indentations looks ugly.   
   >>> Same for wrapping replace-blocks (those 6 lines you spoke of) with empty   
   >>> lines.  Either do it everywhere, or do it nowhere.   
   >>   
   >> Good point. That's my actual code so I didn't clean it up for   
   >> presentation.   
   >   
   > Yeah, I noticed.   Next time do (clean up) though.   You're posting a   
   > *tutorial*, which should be easy to read, and not include visual hurdles   
   > like that.   
      
   I was in a rush, and it's working code (see the latest post where I cleaned   
   it up). As always, I agree with anyone who makes valid sensible statements.   
      
   Remember though, I don't get paid for this. I volunteer my time for you. :)   
   If someone paid me for a tutorial, it would look beautiful! :)   
      
   >   
   >> There's no "arrow" or "degree" symbol on the keyboard.   
   >   
   > Feel free to quote where I said so or even just suggested as such.   
      
   I didn't say you said that. I'm just pointing out the goal is to convert   
   any text to text that is found on a keyboard. In the case of a degree   
   symbol or an arrow bullet, we have to decide how to represent it.   
      
   >   
   > Besides that, for the degree symbol open notepad, press-and-hold the ALT   
   > key, type 0176 on the numeric keypad and than release the ALT key (°).   For   
   > the arrow you might try 175 (no leading zero)  (»).   
   > Warning : What the displayed char actually looks like depends on the active   
   > code-page.   
      
   Again, the goal is to convert any text to that which is on a keyboard.   
   >> I'll take them each on their own merits in a moment, as I appreciate the   
   >> help,   
   >   
   > Good.  Everything that makes a tutorial concise and therefore easier to read   
   > (no "why is it different here?" distractions) is a win for the ones your aim   
   > it at - and by association yourself.   
      
   I very much appreciate the work you did to COMPREHEND the work that I had   
   done. I was actually very HAPPY you criticized the work I had done.   
      
   Notice that I spent a LOT Of effort (hours) cleaning it up.   
   As you had suggested.   
      
   We all need to keep in mind I'm not paid, and neither are you.   
   We're working to improve tribal knowledge together.   
      
   Now people can convert copy and pasted text to keyboard characters.   
   >   
   >> not only for me, but for everyone as we all can use this sanitizer.   
   >   
   > :-)  Most people do not use npp (me among them), so its of zero use to them.   
   > Other people will have zero need to flatten UTF-8 (html ?) documents into   
   > ASCII, so its of zero use to them either.  Others will have theit own   
   > programs/scripts to do such flattening (me among them), so its of zero use   
   > to them either.  That leaves a rather small audience, not much of an "all"   
   > at all, but more like a niche ...   
      
   But for those who have a need to convert arbitrary text to keyboard text,   
   it's useful (if they're on Windows).   
      
   Thanks for spending the effort to UNDERSTAND the code. I appreciate any   
   help anyone gives because I'm a team player. That's what I love about   
   Usenet. We're all improving the tribal knowledge together.   
      
   Now anyone, who wants to, can instantly convert arbitrary text to keyboard   
   text (assuming the character set we've defined is good enough of course).   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)