Re: enforcing US ASCII limitation

Subject: Re: enforcing US ASCII limitation
From: Sandy Harris <sandyinchina -at- gmail -dot- com>
To: TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 6 Mar 2012 10:57:07 +0800

On Tue, Mar 6, 2012 at 5:56 AM, Robert Lauriston <robert -at- lauriston -dot- com> wrote:

> I'm open to suggestions. Currently I'm saving as .rtf, opening in
> Word, and saving as Text with Layout (*.ans).

If you program at all, it is pretty easy to write a checker program.
Read the file, check every character, print an error message if
you find a bad one, giving the line number.

C has a macro isascii() for the test; I'd imagine many other languages
have something similar. Failing that, ASCII is a 7-bit code, so the top
bit of every byte should be zero; that is easy to test.

Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.

Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Previous by Author: Re: Many many big pills
Next by Author: Re: Got a simple system to track system text?
Previous by Thread: RE: Importing Word Files with Hidden Text into RoboHelp 9
Next by Thread: Seeking advice on leading an interview for a technical writer position in English

What this post helpful? Share it with friends and colleagues:

Sponsored Ads