unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: nospam55 <nospa@no.yahoo.no>
Subject: fixing M$ character codes
Date: Sat, 03 Jul 2004 18:00:28 +0200	[thread overview]
Message-ID: <2ko3egF4flbgU1@uni-berlin.de> (raw)

Hi! Help me and the mankind ! 

I have often to correct manually dowloaded M$ - originating text , i. e. I must bother
to do the ethernal replacements

    \222 into '
    \213 into <
    etc etc

        , where the codes are taken from the well-known

               (defvar gnus-article-dumbquotes-map
                 '(("\202" ",")
                   ("\203" "f")
                   ("\204" ",,")
                   ("\205" "...")
                   ("\213" "<")
                   ("\214" "OE")
                   ("\221" "`")
                   ("\222" "'")
                   ("\223" "``")
                   ("\224" "\"")
                   ("\225" "*")
                   ("\226" "-")
                   ("\227" "--")
                   ("\231" "(TM)")
                   ("\233" ">")
                   ("\234" "oe")
                   ("\264" "'"))
                 "Table for MS-to-Latin1 translation.")

Now, the big question whose answer I didn't find on the internet 

   is there a way for having emacs fix this mess ?

My dream is to have something like 

    M-x  fix-evil-empire-nonsense  RET

that automatically does on the selected region the replacements above for us
poor humans.

Any package? Any defun ?

   Thank you :)



PS micro$oft-ware makes many people to write 

    \222 for ' apostrophe
    \202 for , comma
    \213 for < "less than"
    \233 for > "greater than"
    \224 for backslash
    \225 for asterisk
    etc etc


without they realize this :(

             reply	other threads:[~2004-07-03 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-03 16:00 nospam55 [this message]
     [not found] ` <Jym.wzfz884ct0.fsf@econet.org>
2004-07-04 13:19   ` fixing M$ character codes nospam55
2004-07-04 14:08 ` Jym Dyer
2004-07-05 10:00   ` Haines Brown
2004-07-05 10:19     ` Thomas Gehrlein
2004-07-07 15:12     ` Jym Dyer
2004-07-07 20:38       ` Haines Brown
2004-07-15 16:59         ` Jym Dyer
2004-07-04 21:06 ` Jesper Harder
2004-07-05 14:22 ` nospam55

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2ko3egF4flbgU1@uni-berlin.de \
    --to=nospa@no.yahoo.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).