Word 2003 SaveAs wdFormatDOSText bug

When I run a macro, such as this:

ActiveDocument.SaveAs FileName:="c:\temp\testdoc.txt",
FileFormat:=wdFormatDOSText

It is not removing all of the non-DOS characters.

When I do it interactively, it works, but it prompts me with Security
warnings. It appears interactively, it's setting the FileFormat=100 instead
of wdFormatDOSText, which = 4. (Obtained by recording a macro)

I need to be able to do this without security warnings and without non-DOS
characters. Anyone know of a fix?

Thanks for any help.

-cp

Klaus
Thu Apr 14 15:29:18 CDT 2005

Hi cp,

How did you determine that Word uses FileFormat=3D100 when doing the =
SaveAs in the user interface?

DOS isn't one code page. There used to be different code pages for =
different brands of computers and OS, countries...

You'd probably need to specify the code page you want in the Encoding =
parameter -- say 850 for the CP850 used a lot in US MS-DOS (as far as I =
remember).

If you don't know which code page you need:
What characters are giving you problems? (what did they look like in =
Word before, and what happened to them)
What do you want to do with the resulting text file?

Regards,
Klaus



"cp" <cp@notrealdotcom> wrote:
> When I run a macro, such as this:
>=20
> ActiveDocument.SaveAs FileName:=3D"c:\temp\testdoc.txt",=20
> FileFormat:=3DwdFormatDOSText
>=20
> It is not removing all of the non-DOS characters.
>=20
> When I do it interactively, it works, but it prompts me with Security=20
> warnings. It appears interactively, it's setting the FileFormat=3D100 =
instead=20
> of wdFormatDOSText, which =3D 4. (Obtained by recording a macro)
>=20
> I need to be able to do this without security warnings and without =
non-DOS=20
> characters. Anyone know of a fix?
>=20
> Thanks for any help.
>=20
> -cp
>=20
>=20
>

cp
Wed Apr 20 08:22:47 CDT 2005

Thanks Klaus,

I added the AllowSubstitutions=TRUE parameter to the SaveAs method and it
converted or removed characters like non-breaking space that were causing
problems. That should correct our problem.

To determine that Word was using FileFormat=100, I just recorded a macro
doing a saveas and that's what it put in the Macro.

Thanks again,
-cp


"Klaus Linke" <info@fotosatz-kaufmann.de> wrote in message
news:%23VA3nCTQFHA.3336@TK2MSFTNGP10.phx.gbl...
Hi cp,

How did you determine that Word uses FileFormat=100 when doing the SaveAs in
the user interface?

DOS isn't one code page. There used to be different code pages for different
brands of computers and OS, countries...

You'd probably need to specify the code page you want in the Encoding
parameter -- say 850 for the CP850 used a lot in US MS-DOS (as far as I
remember).

If you don't know which code page you need:
What characters are giving you problems? (what did they look like in Word
before, and what happened to them)
What do you want to do with the resulting text file?

Regards,
Klaus

Klaus
Wed Apr 20 17:02:09 CDT 2005

"cp" <cp@notrealdotcom> wrote:
> I added the AllowSubstitutions=3DTRUE parameter to the SaveAs method =
and it=20
> converted or removed characters like non-breaking space that were =
causing=20
> problems. That should correct our problem.

The non-breaking space was available in the DOS code pages I remember =
(at &xFF/255). I hate it when Word's export filters remove or change =
stuff uncontrollably, but it seems it helped you here ;-)

> To determine that Word was using FileFormat=3D100, I just recorded a =
macro=20
> doing a saveas and that's what it put in the Macro.

I didn't get that, but Word probably chooses a sensible code page from =
your Windows regional/language settings or the like.

Regards,
Klaus

cp
Fri Apr 22 15:43:37 CDT 2005

Klaus,

Well, I may have spoken too soon. Now we get ? wherever a non-breaking
space was, whereas in previous versions of Word we got a space. I posted
another thread, Saveas wdFormatText problem (Word 2003), with more detail to
the microsoft.public.word.conversions group to see if anyone has a
workaround.

Thanks again,
-c


"Klaus Linke" <info@fotosatz-kaufmann.de> wrote in message
news:uAUqaSfRFHA.1528@TK2MSFTNGP09.phx.gbl...
"cp" <cp@notrealdotcom> wrote:
> I added the AllowSubstitutions=TRUE parameter to the SaveAs method and it
> converted or removed characters like non-breaking space that were causing
> problems. That should correct our problem.

The non-breaking space was available in the DOS code pages I remember (at
&xFF/255). I hate it when Word's export filters remove or change stuff
uncontrollably, but it seems it helped you here ;-)

> To determine that Word was using FileFormat=100, I just recorded a macro
> doing a saveas and that's what it put in the Macro.

I didn't get that, but Word probably chooses a sensible code page from your
Windows regional/language settings or the like.

Regards,
Klaus

Klaus
Fri Apr 22 17:24:31 CDT 2005

Hi cp,

Looks like a bug in the text converter to me, if you choose "US ASCII" =
as the text filter.
Don't know which code page that is, but all US code pages I checked have =
^255 for the non-breaking space.

Can you use "OEM USA" instead? it doesn't have that problem, and =
converts the non-breaking space properly into ^255.

Or if you really don't mind to get rid of the non-breaking spaces, you =
could search replace them (^s in "Find what") with spaces before saving. =


Regards,
Klaus



"cp" <cp@notrealdotcom> wrote:
> Klaus,
>=20
> Well, I may have spoken too soon. Now we get ? wherever a =
non-breaking=20
> space was, whereas in previous versions of Word we got a space. I =
posted=20
> another thread, Saveas wdFormatText problem (Word 2003), with more =
detail to=20
> the microsoft.public.word.conversions group to see if anyone has a=20
> workaround.
>=20
> Thanks again,
> -c
>=20
>=20
> "Klaus Linke" <info@fotosatz-kaufmann.de> wrote in message=20
> news:uAUqaSfRFHA.1528@TK2MSFTNGP09.phx.gbl...
> "cp" <cp@notrealdotcom> wrote:
> > I added the AllowSubstitutions=3DTRUE parameter to the SaveAs method =
and it
> > converted or removed characters like non-breaking space that were =
causing
> > problems. That should correct our problem.
>=20
> The non-breaking space was available in the DOS code pages I remember =
(at=20
> &xFF/255). I hate it when Word's export filters remove or change stuff =

> uncontrollably, but it seems it helped you here ;-)
>=20
> > To determine that Word was using FileFormat=3D100, I just recorded a =
macro
> > doing a saveas and that's what it put in the Macro.
>=20
> I didn't get that, but Word probably chooses a sensible code page from =
your=20
> Windows regional/language settings or the like.
>=20
> Regards,
> Klaus=20
>=20
>