[bobk544]

Hello, i'm using WORD for a software program cross reference utility and when
i create a file on UNIX all of the "@b ......." references line up exactly on
the same column, so it aligns down the page in the same column.

When i copy that program source into a WORD document however, the lines
shift somewhat randomly and appear to be in different columns and that makes
it hard to read.

As you can see, i even put a period "." in place of a space to try to force
everything to line up, but WORD still seems to have adjusted the font or
spacing somehow even though the periods are the same count.

And to verify what's happening, i also put the same source into a (.txt)
file and it lined up exactly the same as on UNIX.

Is there anyway to tell WORD to use the exact formatting as say a (.txt)
file or not to modify the spacing?

Thanks for any insights on this!
BobK

97 ....if [[ ! $RBC_SRC_HOME
]].................................................. ........ @b
89-100+/70-102+/ @e
98
.....then......................................... ..................................... @b 90-101+/ @e
99 ........echo "No RBC Source Home entered, assuming RBC_HOME/src
"..................... @b
88-134+/93-104+/104+/72-104+/104+/88-104+/88-134+/91-102+/79-102+/ @e
100 ........if [[ $RBC_HOME
]].................................................. .......... @b
97-108+/99-102+/ @e
101
.........then..................................... ..................................... @b 98-109+/ @e
102
.............RBC_SRC_HOME=$RBC_HOME/src............................................... . @b 97-108+/100-131+/99-120+/ @e
103
.........else..................................... ..................................... @b 92-138+/ @e
104 ............MESSAGE="$MESSAGE,No RBC Source Home
Entered"............................. @b
93-112+/93-112+/99-134+/99-112+/99-112+/99-112+/99-134+/ @e
105
.............VALID=false.......................... ..................................... @b 94-113+/94-113+/ @e
106
.........fi....................................... ..................................... @b 96-114+/ @e
107
.....fi........................................... ..................................... @b 106-114+/ @e
108 ....if [[ ! -d $RBC_SRC_HOME
]].................................................. ..... @b
100-110+/153+/102-110+/ @e
109 ....then
.................................................. ............................
@b 101-111+/ @e
110 ........if [[ ! -L $RBC_SRC_HOME ]]
.................................................. . @b 108-116+/155+/108-112+/
@e
111
.........then..................................... ..................................... @b 109-117+/ @e
112 ............MESSAGE="$MESSAGE,RBC Source Home does not exist:
$RBC_SRC_HOME "......... @b
104-120+/104-120+/104-120+/104-120+/104-120+/157+/157+/157+/110-116+/ @e
113
.............VALID=false.......................... ..................................... @b 105-122+/105-122+/ @e
114
.........fi....................................... ..................................... @b 107-123+/ @e
115
.....fi........................................... ..................................... @b 114-123+/ @e
116 ....if [[ $RBC_SRC_HOME = $RBC_SRC_TARGET
]].......................................... @b 110-118+/112-143+/79-165+/ @e
117
.....then......................................... ..................................... @b 111-119+/ @e
118 ........if [[ $INSTALL_SRC = true
]].................................................. @b
116-132+/13-163+/84-161+/ @e
119
.........then..................................... ..................................... @b 117-133+/ @e
120 ............MESSAGE="$MESSAGE,RBC src home and src target cannot be the
same when delivery source files. ".... @b
112-139+/112-139+/112-149+/102-147+/112-149+/169+/102-147+/169+/169+/66-169+/169+/169+/169+/169+/112-149+/169+/ @e
121 ............MESSAGE="$MESSAGE, Modify src target
output."............................. @b
120-139+/120-139+/280+/120-147+/120-169+// @e
122
.............VALID=false.......................... ..................................... @b 113-158+/113-158+/ @e
123
.........fi....................................... ..................................... @b 115-141+/ @e
124
.....fi........................................... ..................................... @b 123-141+/ @e

--
bobk

[Jay Freedman]

Most of the fonts used in Word (and elsewhere in Windows) are
"proportional" fonts -- the space occupied by a letter depends on the
width of the letter, so an m is much wider than an i. If you want
everything to line up in columns, you have to format it with a
nonproportional font, which gives the same amount of space to every
letter. There are only a few common Windows fonts like that: Courier
New, Lucida Console, and Lucida Typewriter.

This has nothing to do with Windows vs. Unix -- there are proportional
and nonproportional fonts available for both. It also has nothing to
do with .txt vs. .doc format, only with the font used to view the
text. Presumably you viewed the .txt file in Notepad; older versions
of Notepad default to using Courier New font, while newer ones use
Lucida Console.

--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the
newsgroup so all may benefit.

On Thu, 8 Feb 2007 14:55:02 -0800, bobk544
wrote:

Hello, i'm using WORD for a software program cross reference utility and when
i create a file on UNIX all of the "@b ......." references line up exactly on
the same column, so it aligns down the page in the same column.

When i copy that program source into a WORD document however, the lines
shift somewhat randomly and appear to be in different columns and that makes
it hard to read.

As you can see, i even put a period "." in place of a space to try to force
everything to line up, but WORD still seems to have adjusted the font or
spacing somehow even though the periods are the same count.

And to verify what's happening, i also put the same source into a (.txt)
file and it lined up exactly the same as on UNIX.

Is there anyway to tell WORD to use the exact formatting as say a (.txt)
file or not to modify the spacing?

Thanks for any insights on this!
BobK