On Tue, Sep 04, 2001 at 07:51:34PM -0700, Joshua Slive wrote:

> On Tue, 4 Sep 2001, Rich Bowen wrote:
> 
> > I've been using tidy, from the w3c, for a while now, to do
> > pretty-reformatting of HTML documents. One of the things that it does is
> > lower-case HTML tags. I was wondering, in light of comments made a week
> > or two ago, whether it would be worthwhile to do this with files in the
> > docs as I a working with them?
> >
> > The downside is that it will create a diff in which every line in the
> > file changes (in most cases), and I did not want to start submitting
> > enormous diffs, without running this past folks first.
> 
> A similar question just threatened to start a flamewar on [EMAIL PROTECTED] 
> ;-)
> 
> My opinion is that it is not a big deal either way.  (It is not like
> source code where you potentially mess up everyone's patches.)  But
> I prefer not to unnecessarily reformat.  The only time I do reformat is
> when the existing format makes the doc very hard to work with.
> 
> In other words, if it makes it significantly easier for you to work
> with, then go ahead and reformat.  But don't reformat just for the
> sake of consistency.  (I don't care about consistency here because
> it is invisible to the end user.)

As you'll know, I spent a little time downgrading case on some of the 1.3
tree -- personally, I believe in consistency, but for the doco people (I
agree with Joshua above re the user).

After consulting a few fellow web developers, the trend/standard as it were
is lowercase HTML tags -- I read somewhere (probably w3c) that lowercase
tends to compress better as well.

As for the diff lines -- this is also true, but it will only happen once
per patched file.



--
----------------------------------------------------------------------------
Jason Lingohr
[EMAIL PROTECTED]
----------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to