Source Formatting isn't doing what I expect

Question

I either don't understand how it works, or it isn't working
as it should.
When I apply Source Formatting to badly formatted code, I was
expecting it
to format the td tags like this:
text
<td>
tag contents
</td>
text
In the tag library editor it says:
Line Breaks: Before, Inside, After
Contents: Formatted and Indented
Case: Lower Case
After applying source formatting all my td tags get formatted
like this:
text
<td> tag contents</td>
text
Or if there are many lines of code between the td's they get
formatted like
this:
text
<td> tag contents 1
tag contents2
tag contents3 </td>
text
What am I doing wrong?
Thanks,
Kirk

Answer 1

Randy,
OK, I see that setting. I wondered why it wouldn't behave. I
guess it was
doing what it is supposed to do.
I guess I have seen odd behavior sometimes in IE rendering
complex table
based layouts and have had to go in and remove that space
because it
rendered the space in the source code the same way it would
have rendered a
<br>.
I guess it is better to leave the setting to "No Break" but
dang, that sure
makes the source code look ugly. I like structured nested
code, it makes it
so much easier to troubleshoot.
Now I don't know what to do.
A friend of mine used to code crazily commented, extremely
structured html
code. (former VAX programmer) He had a program that would
strip out every
extra space, and all the comments before he uploaded it. He
kept two
versions, almost like a programmer keeps source code and
delivered code.
That would be a solution around my problem, but I am too lazy
to maintain
source and delivered code.
Thanks,
Kirk
"Randy Edmunds" <[email protected]> wrote in
message
news:elhsfc$5r0$[email protected]..
> Hi Kirk,
>
> Go to:
>
> Edit > Preferences > Code Format
>
> and you'll see a setting called "No break after TD"
which is on by
> default. Before you turn this off, please read on.
>
> The reason for that setting is because there is a
browser rendering bug
> where some browsers (e.g. IE) will render the break in
the source code as
> a break in the page. This change was not simply done in
the Tag Libraries
> settings to give due warning about this bug.
>
> Hope this helps,
> Randy
>