Tabs and spaces in code view?

[John Sitka]

I run into this about once every six months.

all of a sudden empty space starts being removed on save.

Why is this and how to prevent?

In other words I need Page Options>Code Formatting> don't touch!!

Where is that?

 

[John Sitka]

Specifically FP2003, behaviour is removing all blank/space tab after closing
..asp tag%>

so
<%else%>
some html

<%end if%>

becomes

<%else%>some html

<%end if%>

 

[John Sitka]

here is some other stuff that is related

The little code question mark image that design view uses when it dosen't
know what something is?

AND

The little slanted J used to represent script etc. well these are no longer
available.

Instead FP2003 is trying to correct these unknowns. I had it set so it
wouldn't on a previous install so it wouldn't.

Does anybody know how to set the options such that the stuff that is unknow
is interpretted as unkown the way it was in fp2002?

 

[John Sitka]

Gave up. There is no preserve HTML setting in FP2003.
Funny it did work nice for a while. I can't move
versions now until someones shows how to preserve CODE.
Even if it means disabled DESIGN view.

 

[Stefan B Rusynko]

By default FP2003 is set to preserve html,
- but not white space & tabs (not supported in html)
The white space is usually not relevant in html and coding
- how do the changes impact the performance of your code

You can always use Insert Web Component Advanced Controls Html to make sure FP ignores your code formatting




| Gave up. There is no preserve HTML setting in FP2003.
| Funny it did work nice for a while. I can't move
| versions now until someones shows how to preserve CODE.
| Even if it means disabled DESIGN view.
|
|
|
|
| | > here is some other stuff that is related
| >
| > The little code question mark image that design view uses when it dosen't
| > know what something is?
| >
| > AND
| >
| > The little slanted J used to represent script etc. well these are no
| longer
| > available.
| >
| > Instead FP2003 is trying to correct these unknowns. I had it set so it
| > wouldn't on a previous install so it wouldn't.
| >
| > Does anybody know how to set the options such that the stuff that is
| unknow
| > is interpretted as unkown the way it was in fp2002?
| >
| > | >
| > > Specifically FP2003, behaviour is removing all blank/space tab after
| > closing
| >
| > > .asp tag%>
| >
| > >
| >
| > > so
| >
| > > <%else%>
| >
| > > some html
| >
| > >
| >
| > > <%end if%>
| >
| > >
| >
| > > becomes
| >
| > >
| >
| > > <%else%>some html
| >
| > >
| >
| > > <%end if%>
| >
| > >
| >
| > >
| >
| > >
| >
| > >
| >
| >
| > > | >
| > > > I run into this about once every six months.
| >
| > > >
| >
| > > > all of a sudden empty space starts being removed on save.
| >
| > > >
| >
| > > > Why is this and how to prevent?
| >
| > > >
| >
| > > > In other words I need Page Options>Code Formatting> don't touch!!
| >
| > > >
| >
| > > > Where is that?
| >
| > > >
| >
| > > >
| >
| > >
| >
| > | > > Specifically FP2003, behaviour is removing all blank/space tab after
| > closing
| > > .asp tag%>
| > >
| > > so
| > > <%else%>
| > > some html
| > >
| > > <%end if%>
| > >
| > > becomes
| > >
| > > <%else%>some html
| > >
| > > <%end if%>
| > >
| > >
| > >
| > >
| > > | > > > I run into this about once every six months.
| > > >
| > > > all of a sudden empty space starts being removed on save.
| > > >
| > > > Why is this and how to prevent?
| > > >
| > > > In other words I need Page Options>Code Formatting> don't touch!!
| > > >
| > > > Where is that?
| > > >
| > > >
| > >
| > >
| >
| >
|
|

 

[John Sitka]

The impact is that the visual formatting of tabs and spaces is put their for
a reason...
to make logical design time "sense" of the code which you are writing.
Also have you ever used Visual Source Safe and the compare feature.
this would also be destroyed. Calling attention to changes which "aren't"
And many times code is intentionally left incorrect because it remains "in
Development"
for a couple of days, weeks, months.
So a save operation has no business changing that code. If I was to ask
frontpage to build
that's a whole different ball of wax.

But really this is even more strange because I had done an install on XP
which had a
office 2000/FP2002 then a maintain previous version install of FP2003 and
things were
as they should be tabs, and whitespace was maintained in every instance.
This is not a "non issue" , as of right now there is not a MS product to
maintain
legacy ASP applications. Oh wait there is Notepad, and windows explorer.

By default FP2003 is set to preserve html,
- but not white space & tabs (not supported in html)
The white space is usually not relevant in html and coding
- how do the changes impact the performance of your code

You can always use Insert Web Component Advanced Controls Html to make

sure FP ignores your code formatting

 

[Terry Crowley \(MSFT\)]

It is absolutely a bug if FP ever changes your HTML (including changing
whitespace) without your intention. Open/Save should always result in no
change in the HTML. This has been getting better every release since FP2000
(which was when the big leap in preservation was made) and was improved even
further in FP2003.

Can you give a precise repro scenario?

Terry

 

[John Sitka]

I hit "reply" instead of "reply to group" but just
to close this out. Terry recognized my
problem straight away and could zero
in on it. He pointed out that I was installing
off a beta disk, I was blind to that because
things were working well for so long.
Thanks Terry for pointing out the obvious and
getting me back on track.