unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: gebser@speakeasy.net
Subject: Re: How to convert .doc to plain text ascii in emacs.
Date: Sun, 2 May 2004 10:44:17 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0405021009480.7405-100000@localhost.localdomain> (raw)
In-Reply-To: <87u0z0vuln.fsf@spacecentre.se>


Thanks very much.  Your elisp works great.  There's one glitch (which I
realize is from antiword):

The three characters "\342\200\231" should be replaced by the single 
apostrophe character (').  To do this by hand, I did

M-x replace-regexp Return C-q 342 Return C-q 200 Return C-q 231 Return
Return ' Return

but this does not find the intended string.  The problem seems to be 
that C-q 342 is immediately (in the minibuffer) converted into an 'a' 
with a grave symbol over it.  Putting the point on the backslash (\) 
preceding the 342 in the antiword-converted buffer and doing "C-u C-x =" 
indeed shows this a-with-grave character to be (0342, 226, 0xe2).

To create a simple test case, do the following:

Open an empty *scratch* buffer.  Enter into it: C-q 342 Return C-q 200
Return C-q 231 Return.  The first character that appears is the 
a-with-grave; the second and third characters appear properly as 
\200\231.  

It is, I think, the failure of C-q 342 to be represented as \342 which 
is the problem.  What is the solution?


tia,
ken



[....]

  reply	other threads:[~2004-05-02 14:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28 17:32 How to convert .doc to plain text ascii in emacs Don Saklad
2004-04-28 18:13 ` Yoni Rabkin Katzenell
2004-05-01 19:02   ` Thomas Persson
2004-05-02 14:44     ` gebser [this message]
2004-05-02 19:04       ` Roodwriter
2004-05-02 19:26       ` Thomas Persson
2004-05-02  8:57 ` Tim X
  -- strict thread matches above, loose matches on Subject: below --
2004-04-28 18:02 Don Saklad
2004-04-28 18:10 ` Kin Cho
2004-04-28 18:17   ` Jay Belanger
2004-04-29 13:47     ` John Russell

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=Pine.LNX.4.44.0405021009480.7405-100000@localhost.localdomain \
    --to=gebser@speakeasy.net \
    /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).