XSLT/Email
am 03.11.2005 21:02:41 von tconti
Hello:
I am having a problem where I am using an xslt to format email for our
clients. 99% are OK, but there are that collection of users that
cannot traverse the refs in the email. It appears that the & gets
converted to &. I am using .Net Xslt Transform to convert
format the email. I receive this email on a daily basis and this does
not happen to me. I am running Outlook 2000. I thought it could be
due to the clients using old mail readers, but recently we had a
complaint by a client using Outlook 2000. Is there some configuration
issue on the clients mail server or reader that could be causing this?
Has anyone run into this in the past? Is there some bug with .Net
transform?
Please let me know what you think.
Tom
Re: XSLT/Email
am 04.11.2005 00:47:33 von Sam
This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.
--=_mimegpg-commodore.email-scan.com-7893-1131061655-0005
Content-Type: text/plain; format=flowed; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
X-Mime-Autoconverted: from 8bit to quoted-printable by mimegpg
tconti@hotmail.com writes:
> Hello:
>
> I am having a problem where I am using an xslt to format email for our
> clients.
Fascinating. Now, when someone explains what the FSCK does XSLT have to do
with E-mail, we'll be making progress here.
> 99% are OK, but there are that collection of users that
> cannot traverse the refs in the email. It appears that the & gets
> converted to &. I am using .Net Xslt Transform to convert
> format the email.
I'm sorry to hear that. The microsoft.public.* newsgroups are thataway â=
=92.
> Has anyone run into this in the past? Is there some bug with .Net
> transform?
I think it's safe to say that there are bugs in dot-Nyet.
> Please let me know what you think.
Well -- not that it's much of a help to you -- but the foundation of the
global E-mail infrastructure is based on open standards and free software.
Chances are fairly slim that, at least in this newsgroup, you will find
anyone with sufficient knowledge of Microsoft's proprietary software and
internal protocols that can help you. The majority of technical
contributors to this newsgroups, except for Beavis (Google search: "Usenet
Beavis"), are familiar with open standards and free software, and have only
a minimal exposure to Microsoft's bugware (and they keep trying to make it
as minimum as necessary).
I'm only guessing that you're using some dot-Nyet API to generate text/xml
MIME content, and it does not show correctly in some, or all, E-mail clients=
(not, AFAIK, there's a plethora of clients that will render arbitrary XML,
in some form or fashion). This is only a guess. There are a lot of folks
here who've wrote all kinds of assorted E-mail clients, servers, and related=
software, and I'm confident that, up until now, none of us had must use for
XSLT.
Well, yes, it could be because dot-Nyet barfed out crap -- certainly I've
seen my share of Microsoft HTML Gooâ=A2, coming out of Outlook. But it=
's
equally possible that the E-mail client has a bug. Can't really say without=
seeing the raw contents of the E-mail message in question.
So, I suppose, the only thing you could do here is post the raw E-mail
content, to check if its MIME formatting (and other characteristic) are up
to code. But that's about it.
--=_mimegpg-commodore.email-scan.com-7893-1131061655-0005
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
iD8DBQBDaqGXx9p3GYHlUOIRArOOAJsFNV3NUkg1npxwxGcD0pF+27xc1wCf cPOG
sXTvQOg08CaQAdc06ntXwNw=
=BhNo
-----END PGP SIGNATURE-----
--=_mimegpg-commodore.email-scan.com-7893-1131061655-0005--
Re: XSLT/Email
am 04.11.2005 15:14:51 von tconti
You wrote
-----
There are a lot of folks
here who've wrote all kinds of assorted E-mail clients, servers, and
related
software, and I'm confident that, up until now, none of us had must use
for
XSLT.
-----
Why do you avoid xslt for generating email?
Re: XSLT/Email
am 05.11.2005 00:34:13 von Sam
This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.
--=_mimegpg-commodore.email-scan.com-16390-1131147255-0001
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
tconti@hotmail.com writes:
> You wrote
> -----
> There are a lot of folks
> here who've wrote all kinds of assorted E-mail clients, servers, and
> related
> software, and I'm confident that, up until now, none of us had must use
> for
> XSLT.
> -----
>
> Why do you avoid xslt for generating email?
Why do I need XSLT to generate E-mail? I've been generating E-mail for over
a decade now, give or take a day. I've yet to see any need to use XSLT.
--=_mimegpg-commodore.email-scan.com-16390-1131147255-0001
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
iD8DBQBDa+/3x9p3GYHlUOIRApi/AJ9+lCgfiy+gJQEheYANvMp+koV0VACd GMGG
Q8lxp12N8F0Iw/KDElIJkE4=
=i5Fe
-----END PGP SIGNATURE-----
--=_mimegpg-commodore.email-scan.com-16390-1131147255-0001--