XPost: alt.comp.os.windows-11, alt.comp.microsoft.windows   
   From: marianjones@helpfulpeople.com   
      
   >> And I noticed while walking thru that list :   
   >> " " is a thin space, not an "x".   
   >> "—" to "&" ?  Not a dash ?   
   >> '"'  with single-quotes around it instead of double ones ?   Any reason   
   >> for that ?   
   >> "apos;" ?  Why not just a single quote thats available on you keyboard ?   
   >> " " is a hard space, not a quote.   
   >> "‘" and "’" are twice in there.   
   >> "*" is a standard ASCII char ("*").  Why not use it instead ?   
      
      
   Thank you for all those suggestions, where, as always, I easily agree   
   with anyone who makes a logically sensible argument, no matter what.   
      
   1. Regarding " " is a thin space, not an "x".   
      I don't see   (thin space) explicitly listed in the macro.   
         (NO-BREAK SPACE was replaced with " ")   
         (FIGURE SPACE was replaced with " ")   
         (NARROW NO-BREAK SPACE was replaced with " ")   
      
   I haven't tested it thoroughly but this is what I'll test:   
       
       
       
       
       
       
       
      
   2. Regarding "—" to "&" ?  Not a dash ?   
      — is a legacy Windows-1252 code for an em dash.   
      In proper Unicode, the em dash is —   
      Since — represents a dash, the replacement should logically be a dash   
   (-).   
      Good catch. Here's the fixed block.   
      
       
       
       
       
       
       
       
      
   3. " is the XML entity for a double quote (").   
      In XML, both single ' and double " quotes are valid for wrapping attribute   
   values.   
      Functionally, it works fine in that Notepad++ will interpret it correctly.   
      Using single quotes around " is just a stylistic choice.   
      sParam=""" will also work.   
      
      For easier reading, I'll change it to these.   
       
       
       
       
       
       
       
      
       
       
       
       
       
       
       
      
    The change is:   
     Before: sParam='"' (single quotes around the entity).   
     Now: sParam=""" (double quotes around the entity).   
      
   4. "apos;" ? Why not just a single quote that's available on your keyboard?   
      The reason is that I was in syntax hell when I first tried it.   
      So instead of a single quote, I used the XML entity for it.   
      But you are correct that, in XML, you can safely put a literal ' inside   
      an attribute value if the attribute itself is wrapped in double quotes.   
       So sParam="'" is simpler and clearer than is sParam="'"   
      
      This is a rewritten block that takes advantage of that syntax:   
       
       
       
       
       
       
       
      
    Thanks for the advice, which I had taken the easy way out (syntactically)   
    in the past, but your suggestion is much easier for others to read.   
      
    I changed these six blocks (U+2018, U+2019, U+200C, U+200D, U+2060,   
    and BACKTICK) to use a plain ' instead of '.   
      
   5. " " is a hard space, not a quote.   
      This hard space (aka a non-breaking space) is correct but I can see how   
      it might have been mixed in with the quotes.   
      
   6. "‘" and "’" are twice in there.   
      Later in the file, I also had zero-width joiner/non-joiner and   
      word joiner sections where the replacement was also '.   
      That makes it look like the single quote replacement appears multiple times.   
      The Unicode single quotes (U+2018 and U+2019) were not repeated, AFAICT.   
      Yes there are several other blocks where the replacement was also '   
     (for zero-width joiner, non-joiner, word joiner, backtick) but those aren't   
     duplicates of U+2018 or U+2019, but they look similar since the replacement   
     is the same character.   
      
   7. "*" is a standard ASCII char ("*"). Why not use it instead?   
      I'm replacing the Unicode bullet with an asterisk (*).   
      But you're saying, I think, that * is already a plain ASCII character   
      so we don't need to encode it.   
      In the macro, I have it set as sParam="*", which will use the asterisk.   
      I agree with you that encoding ASCII characters as entities is unnecessary   
      
   Here is the new shortcuts.xml, version 1p2, with those specific fixes.   
      
       
        
        
        
        
        
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)