XPost: alt.comp.os.windows-10, comp.mobile.android, misc.phone.mobile.iphone   
   From: robin_listas@es.invalid   
      
   On 2025-12-11 18:59, Marian wrote:   
   > Carlos E.R. wrote:   
   >>>> it does contain big5, that's what triggered fonts, if it remains a   
   >>>> mystery, that doesn't bother me ...   
   >>>   
   >>> Hmmm... thanks for looking since I was so sure I didn't add it that I   
   >>> didn't even bother to look. Now I'm looking at your reference   
   >>>    
   >>> MIME-Version: 1.0   
   >>> Content-Type: text/plain; charset="big5"   
   >>> Content-Transfer-Encoding: 8bit   
   >>   
   >> The server to which you upload the post can do its own changes.   
   >   
   > Thanks for your help and from the help of Andy, where I want to be very   
   > clear that I've never really understood this charset header stuff. :(   
   >   
   > What I'll do, moving forward, is when I copy from another source, I will   
   > run it thru my macro (see other post with the macro) to clean it up.   
   >   
   > That way the text I post will always be clean ASCII using only the 95   
   > keyboard characters, so the charset header line won't matter.   
      
   That's a very bad idea.   
      
   That's akin to saying you will light your fire with a flintstone instead   
   of using matches or a lighter.   
      
   Please, just use unicode, in any of the versions used by Windows or   
   Linux. Your vi is using unicode, 99.9% sure.   
      
   And then use the correct header, not a random one.   
      
   --   
   Cheers, Carlos.   
   ES🇪🇸, EU🇪🇺;   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)