LiveDocs Comments - coldfusion - 6.1 - htmldocs - tags-b15.htm

coldfusion/6.1/htmldocs/tags-b15.htm

alpsauto — 2006-10-01T08:01:47

it seems even if you set suppresswhitespace="yes", your lines with coldfusion comments will still be displayed as blank lines in the view source (the carriage returns are maintained from the cf comments).

coldfusion/6.1/htmldocs/tags-b15.htm

sillyworm — 2005-02-10T10:51:51

Hi,

I'm curious as to why in the example here

you don't have variable #whitespaceSetting# in quotes. Though it works, it seems inconsistent with variable reference in most other tags. It does in fact work with quotes as well. Can you point me to a resource on this? I've seen this in a couple of other tags as well.

Thanks.

coldfusion/6.1/htmldocs/tags-b15.htm

mindtrap — 2005-01-21T07:15:50

What's the difference between:

and

I'm sure that the underlying Java code is different,.

coldfusion/6.1/htmldocs/tags-b15.htm

Amalaan — 2005-01-20T06:29:12

Apologies, please ignore my post above. I've just noticed that the example at the top of the page does indeed possess a closing slash. Is this a general rule, that all CFML 'empty elements' can be legally terminated with /> ?

coldfusion/6.1/htmldocs/tags-b15.htm

Amalaan — 2005-01-20T04:55:46

Hi,
You state:
"If you specify only the pageencoding attribute, do not use a separate end tag"
However, is it legal to use an XML-style, empty element closing slash, e..g

The reason I ask is that using a single tag without a closing slash causes the CFC "Methods View" to fail in CFEclipse v.1.1.17.2 .

coldfusion/6.1/htmldocs/tags-b15.htm

MarkZet — 2004-12-22T03:56:22

I have looked into CFMX white space suppressing by decompiling the classes in the CFCLASSES directory. There is an abundance of calls like:
_whitespace(out, "\r\n\r\n\t")
Is this in any way related to suppressWhiteSpace, and can those calls be avoided?

coldfusion/6.1/htmldocs/tags-b15.htm

mellon@mnr.org — 2004-11-18T07:25:00

Perhaps you could work around the need for a constant encoding type by making a .cfc for each supported type, and then conditionally calling the correct component.

coldfusion/6.1/htmldocs/tags-b15.htm

dmw — 2004-10-29T06:08:26

The example:

is misleading as the pageencoding paramater cannot be dynamic. This would actually generate an error 'This expression must have a constant value.'
As it cannot be dynamic and it cannot be conditional this tag is useless if you have a page which must handle multiple character sets dynamically.

coldfusion/6.1/htmldocs/tags-b15.htm

jrunrandy — 2004-10-24T17:44:56

Did you look in the Developing Globalized Applications chapter? http://livedocs.macromedia.com/coldfusion/6.1/htmldocs/i18n.htm#wp1141005

coldfusion/6.1/htmldocs/tags-b15.htm

adi_venuma — 2004-10-24T02:14:11

i need more explanations please.

coldfusion/6.1/htmldocs/tags-b15.htm

Simon.Harper — 2004-09-08T10:17:31

To be even more precise, you can do this:

.. etc.,

coldfusion/6.1/htmldocs/tags-b15.htm

spage — 2004-03-03T17:34:43

To answer my own comment, if you use the tag in a .cfc then it must be the first tag; so put after it.

coldfusion/6.1/htmldocs/tags-b15.htm

spage — 2004-03-03T17:07:41

I don't think you can use this in a .cfc to specify encoding, I put:

on the first line of a trivial .cfc on Solaris and got "JRun Servlet Error 500 Invalid CFML construct found on line 2 at column 1"

Adding a Byte Order Mark (Modify > Page Properties > Title/Encoding in Dreamweaver MX) made it work.

coldfusion/6.1/htmldocs/tags-b15.htm

chesto — 2004-01-09T09:33:38

spelling error, change "insformation" on line 2 to "information"