Got it. Don't know why anyone would use a period as a list separator,
but...

Got it. Don't know why anyone would use a period as a list separator,
but...
I'd say Word can't resolve the conflict between decimal and list separator
being the same?

I don't know either, but I would guess that the problem described in the KB
articles has more to do with
a. conflict between the various different separators as defined in regional
settings
b. and/or conflict between those separators and the ones assumed by Word -
in which case the standard settings for some non-US regions may cause the
problem. There is (or was - haven't checked specifically in Word 2003)
definitely some hard-coding in Word concerning regional options somewhere in
this area, as Word is definitely not completely locale-neutral when it comes
to applying numeric formatting defined in \# switches.

--
Peter Jamieson - Word MVP
Word MVP web site http://word.mvps.org/

"Cindy M -WordMVP-" wrote in message
news:VA.0000968d.017dfcd1@speedy...
Hi Peter,

Starting with the US regional options, if I change the list separator to
"."
then try { = 0 } I get the error in Word 2003.

Got it. Don't know why anyone would use a period as a list separator,
but...
I'd say Word can't resolve the conflict between decimal and list separator
being the same?

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Sep 30 2003)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail :-)