From owner-freebsd-questions@FreeBSD.ORG Thu May 27 03:03:06 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D926B106564A for ; Thu, 27 May 2010 03:03:06 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 999ED8FC1E for ; Thu, 27 May 2010 03:03:06 +0000 (UTC) Received: from r55.edvax.de (port-92-195-249-33.dynamic.qsc.de [92.195.249.33]) by mx02.qsc.de (Postfix) with ESMTP id 9F01D1E60C; Thu, 27 May 2010 05:03:03 +0200 (CEST) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id o4R332e1002179; Thu, 27 May 2010 05:03:03 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 27 May 2010 05:03:02 +0200 From: Polytropon To: Gary Kline Message-Id: <20100527050302.da39c258.freebsd@edvax.de> In-Reply-To: <20100527013843.GA40751@thought.org> References: <20100527013843.GA40751@thought.org> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Mailing List Subject: Re: any shortcuts to doc to ascii? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 03:03:06 -0000 On Wed, 26 May 2010 18:38:47 -0700, Gary Kline wrote: > > > guys, > > is there anything that can take these hex triplets such as > > We Don\xe2\x80\x99t > > and render them back to the ascii or keyboard equivalents? > in this case, the \x99 would be an apostrophe. > thus: > > > We Don't > > tia, > > gsry > > ps: even lynx -dump messes up, i believe. i'm trying to go from > DOC back to typewriter.... Yes, even a typewriter is better than DOC. :-) To process DOC files into ASCII, there are several ways, with different complexity: Most complex ones: Use OpenOffice or Abiword, open the file and save it as ASCII. Included "special characters" should be in regular ASCII representation now. Better: Use (from ports) catdoc or antiword. I'm not sure in how far conflicting codepages may be involved. It is known that "Windows" does have problems supporting standards, and this applies to character sets and language variations, too. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...