MSGID: 2:280/464.113 5c74dca9   
   REPLY: 2:20/228 000c67ff   
   TZUTC: -0800   
   RFC-3339: 2019-02-26 06:28:57.217017564+00:00   
   CHRS: UTF-8 4   
   LANG: en_CA.utf8   
   MøøSGID: 2:280/464.113 5c74dca9-0cef6cdc   
   Hey Holger!   
      
   Note that I am replying on a different machine this time since I am in the   
   middle of a major overhaul on the raspi3b+ which will take at least another 32   
   hours.  The Swedish, Danish, and Spanish MøøSGing configurations are on that   
   machine.  This machine is the English jobber.  I also have a Dutch jobber on a   
   totally different machine - also a x86_64-pc-linux-gnu host - but I decided to   
   reply on this one instead.   
      
    MK>> That translates to the '÷' character in utf8 - usually written   
    MK>> as U+00F7 or \u00f7 in bash.   
      
    HG> This is also a new sign for my UTF conversion whatever use I may   
    HG> have.   
      
   An excellent online source for utf8 characters is http://www.utf   
   -chartable.de/ as they give the 8 bit codes that show up in hex editors to the   
   corresponding utf8 characters.  For example U+00F7 will show up as a hex 'c3   
   b7' pair whereas the small slashed 'o' characters in Møøse show up as 'c3   
   b8' hex pairs.  So in bash speak this should produce the utf8 division sign;   
      
   -={ ':read !echo -e "\u00f7 \xc3\xb7"' starts }=-   
   ÷ ÷   
   -={ ':read !echo -e "\u00f7 \xc3\xb7"' ends }=-   
      
   Imagine that!!!  It works!!!   
      
   Offhand I am thinking it might make the basis for converting utf8 to whatever   
   8 bit codepage you are using by just replacing 'c3 b8' combinations with a   
   single hex character that represents the divide sign in your codepage of   
   choice.  So for CP850 a conversion vector would look something like this;   
   's/\xc3\xb7/\xf6/g' which will replace ALL U+00F7 characters with a single f6   
   character.  For the Møøse that would be 's/\xc3\xb8/\x9b/g' and then   
   everyone will be happy including the Germans.  ;-)   
      
    HG> If I translate that german line to swedish, norwegian or danish   
      
   Yes that can definetly screw things up.  I've done it from english to whatever   
   and then from whatever back to english and gotten strange results.  Let's try   
   it here;   
      
   -={ ':read !trans -b -no-ansi -s english -t swedish "A Møøse once bit   
   my sister ..."' starts }=-   
   En möse hade en gång min syster ...   
   -={ ':read !trans -b -no-ansi -s english -t swedish "A Møøse once bit   
   my sister ..."' ends }=-   
      
   We're already off to a bad start but let's leave the möse alone for now;   
      
   -={ ':read !trans -b -no-ansi -s swedish -t english "En möse hade en   
   gång min syster ..."' starts }=-   
   A muzzle once had my sister ...   
   -={ ':read !trans -b -no-ansi -s swedish -t english "En möse hade en   
   gång min syster ..."' ends }=-   
      
   That didn't work out so well but what about this?;   
      
   -={ ':read !trans -b -no-ansi -s swedish -t english "En Møøse hade en   
   gång min syster ..."' starts }=-   
   A mousse once had my sister ...   
   -={ ':read !trans -b -no-ansi -s swedish -t english "En Møøse hade en   
   gång min syster ..."' ends }=-   
      
   Not much better is it?  Oh well ... despite this I am sticking with the   
   Møøse.  If you have a better Swedish translation I would like to see it but   
   the Møøse stays, no matter what my sister or anyone else has to say about it.   
      
   Life is good,   
   Maurice   
      
   ... A Møøse once bit my sister ...   
   --- GNU bash, version 5.0.2(1)-release (x86_64-pc-linux-gnu)   
    * Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)   
   SEEN-BY: 15/2 103/705 123/1970 154/10 203/0 221/0 226/17 229/107 426   
   SEEN-BY: 229/452 616 240/5832 249/206 317 400 280/464 5003 292/854   
   SEEN-BY: 310/31 317/3 322/757 342/200 393/68 396/45 423/120 633/280   
   SEEN-BY: 712/848 770/1 2452/250 3828/7 5020/545   
   PATH: 280/464 229/426