Hmmm...it's possible. The form was created by someone else in our group,
and while he was only pasting from one InfoPath form to another, it's highly
possible the tag was an artifact from Word (inline comment perhaps) or
something from an earlier incarnation.
That's good to know...I was a bit surprised when I saw it; I figured any
"custom" tag generated by InfoPath that I ran into would be scoped to a
namespace, and this one wasn't!
Thanks!
Mike Sharp
> Did you happen to paste some portion of your document from a web page or
> other application? InfoPath probably won't be generating <comment> tags on
[quoted text clipped - 20 lines]
> > Regards,
> > Mike Sharp
Brian Teutsch [MSFT] - 12 Mar 2005 23:58 GMT
Actually it is scoped to a namespace. <xsl:comment> is a defined way to
store comment information in an XSL file. InfoPath doesn't make any use of
that ability, but it's possible it was preserved/converted from another
application.
Brian
> Hmmm...it's possible. The form was created by someone else in our group,
> and while he was only pasting from one InfoPath form to another, it's
[quoted text clipped - 34 lines]
>> > Regards,
>> > Mike Sharp
Mike Sharp - 23 Mar 2005 01:52 GMT
Right, <xsl:comment> is scoped, but this strange tag was simply <comment/>.
I think you hit it on the head when you suggested it got there from a
copy-and-paste operation. I heard that it happened to them again, but now
they knew to look for the tag. I think it might be comming from the
discussion server...
Thanks for your help!
Regards,
Mike
> Actually it is scoped to a namespace. <xsl:comment> is a defined way to
> store comment information in an XSL file. InfoPath doesn't make any use of
[quoted text clipped - 41 lines]
> >> > Regards,
> >> > Mike Sharp