Re: [Slightly Off Topic] mail server [was: Re: [xsl] Source code formatting]
2020-07-31 16:53:43
Yes, it's all about what happens when people start spoofing. Then: watch out.
-- Gerrit
-----Original Message-----
From: Imsieke, Gerrit, le-tex gerrit(_dot_)imsieke(_at_)le-tex(_dot_)de
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>
Sent: Friday, July 31, 2020 9:25 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [Slightly Off Topic] mail server [was: Re: [xsl] Source code
formatting]
I remember when Mulberry needed to take the difficult decision to change the
sender of each and every message to
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> (albeit prefixed
with the sender's name and actual email address).
The best solution for your and John's email clients would be if they returned
to sending with the original sender's address, but for legal and/or technical
reasons this was no longer possible.
I'm afraid there's not much they can do about it.
-- Wendell
On 31.07.2020 15:16, Geert Bormans geert(_at_)gbormans(_dot_)telenet(_dot_)be
wrote:
Hi Wendell,
Don't worry, I get all my messages from Abel (as Gerrit pointed out) I
experience similar issues as John does, I need to see my iPad or phone
to know the sender of a message I guess Gerrit is not too far of
suggesting that the first ever message I received from this address
could have been from Abel and my client remembered it I always assumed
it was a header incorrectly appreciated by some mail clients ... it is
however worrying that Abel's email address is exposed (and yours)
Might be an issue to take up with the list admins... but not until
Balisage is over ;-)
Met vriendelijke groeten,
Best regards,
Geert Bormans
----- Op 31 jul 2020 om 15:02 schreef Abel Braaksma, (Exselt)
abel(_at_)exselt(_dot_)net
xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com:
John and XSL-List,
I don't know whether to be charmed or horrified.
So who else gets all their XSL-List messages from me? (You don't have
to answer if you really don't think it's on topic.)
Regards, Wendell
-----Original Message-----
From: John Lumley john(_at_)saxonica(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>
Sent: Wednesday, July 29, 2020 1:45 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] Source code formatting
I have exactly the same problem with xsl-list read on my iPad... all the
messages now appear from Wendell Piez, so unless there is identification of
originator in the message body, I have no firm idea of who is the sender....
Unless, as in this case, I compose a reply.
Ok on Thunderbird on my Windows machine.
Sent from my iPad
On 28 Jul 2020, at 23:02, Imsieke, Gerrit, le-tex
gerrit(_dot_)imsieke(_at_)le-tex(_dot_)de
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Interesting, Geert, how your email client apparently regenerated the header
of the original message instead of just quoting it literally. Your email
client seems to hold a database of senders by email address. When
regenerating the headers, it won't use the real name under which the message
was sent, but instead it will use the stored sender name associated with
that address, which happens to be "Abel Braaksma, (Exselt)
abel(_at_)exselt(_dot_)net" for
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>. Abel might have
been the first to post to the list after you set up your email client,
therefore it stored Abel's name.
In addition to that flaw, the email client didn’t quote the original
message. But maybe this can be switched on by an option.
Sorry, probably a bit off-topic...
Gerrit
On 28.07.2020 23:44, Geert Bormans
geert(_at_)gbormans(_dot_)telenet(_dot_)be wrote:
Hi Willem,
Not sure if this would work with the particular VCS you are using,
but have you considered not to use a formatter when adding the XSLT
to the VCS, but tune the actual dif (ignoring whitespace in
attributes as an example) Delta XML have done some work in that area
for GIT I believe, maybe you find some inspiration here
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww
w
.youtube.com%2Fwatch%3Fv%3DYmfzhK4aR1c&data=02%7C01%7Cwendell.pi
e
z%40nist.gov%7Ce508c6c6180d471b198808d833827e63%7C2ab5d82fd8fa4797a9
3
e054655c61dec%7C1%7C0%7C637315982851829409&sdata=LzKbVfJklhCWYtn
u
VUYkbpn5fUIr6l4%2BGOjQ3xb8H3I%3D&reserved=0
Met vriendelijke groeten,
Best regards,
Geert Bormans
--------------------------------------------------------------------
-
---
*Van: *"Abel Braaksma, (Exselt) abel(_at_)exselt(_dot_)net"
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>
*Aan: *"xsl-list" <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
*Verzonden: *Dinsdag 28 juli 2020 23:18:00
*Onderwerp: *[xsl] Source code formatting Hi list, Like many of you,
I assume, I use a version control system when working on XSLT projects. I'm
working together with multiple people, and we run the code through an XML
formatter before checking it in to avoid formatting differences showing up
in the diffs.
The problem is that, due to attribute value normalization, carriage returns
are removed from attribute nodes during XML parsing. When using long XPath
expressions (and this has become very common in XSLT 3, especially with
higher order functions), which are split in multiple lines, this results in
huge single line outputs which are impossible to read.
It seems any sort of XML processing will irreversibly transform the
whitespace, therefore I have to choose between:
- No formatting
- Formatting using non-XML tools?
- Finding a parser that bends the rules...
Have any of you experienced the same problem and did you find a solution?
Thanks.
Willem Van Lishout
willemvanlishout(_at_)gmail(_dot_)com
<mailto:willemvanlishout(_at_)gmail(_dot_)com>
XSL-List info and archive
<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fww
w
.mulberrytech.com%2Fxsl%2Fxsl-list&data=02%7C01%7Cwendell.piez%4
0
nist.gov%7Ce508c6c6180d471b198808d833827e63%7C2ab5d82fd8fa4797a93e05
4
655c61dec%7C1%7C0%7C637315982851829409&sdata=NK3ExUHp2WLRly0pBYu
i
u7s7NduJv3nfNTSFOtw6%2B%2Fw%3D&reserved=0>
EasyUnsubscribe
<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fli
s
ts.mulberrytech.com%2Funsub%2Fxsl-list%2F554170&data=02%7C01%7Cw
e
ndell.piez%40nist.gov%7Ce508c6c6180d471b198808d833827e63%7C2ab5d82fd
8
fa4797a93e054655c61dec%7C1%7C0%7C637315982851829409&sdata=PAKO1R
n
rKYLaq4ytMT4jnuX68VsE%2FgSw9O2FRtoXUOo%3D&reserved=0> (by email)
XSL-List info and archive
<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fww
w
.mulberrytech.com%2Fxsl%2Fxsl-list&data=02%7C01%7Cwendell.piez%4
0
nist.gov%7Ce508c6c6180d471b198808d833827e63%7C2ab5d82fd8fa4797a93e05
4
655c61dec%7C1%7C0%7C637315982851829409&sdata=NK3ExUHp2WLRly0pBYu
i
u7s7NduJv3nfNTSFOtw6%2B%2Fw%3D&reserved=0>
EasyUnsubscribe
<https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fli
s
ts.mulberrytech.com%2Funsub%2Fxsl-list%2F225679&data=02%7C01%7Cw
e
ndell.piez%40nist.gov%7Ce508c6c6180d471b198808d833827e63%7C2ab5d82fd
8
fa4797a93e054655c61dec%7C1%7C0%7C637315982851839406&sdata=eYAxpw
%
2B%2BIDoprhyiPhO%2BDB6gvnsguFNlqhB%2BjJcDXfI%3D&reserved=0> (by
email <>)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [xsl] Source code formatting, Willem Van Lishout willemvanlishout(_at_)gmail(_dot_)com
- Re: [xsl] Source code formatting, Imsieke, Gerrit, le-tex gerrit(_dot_)imsieke(_at_)le-tex(_dot_)de
- Re: [xsl] Source code formatting, Geert Bormans geert(_at_)gbormans(_dot_)telenet(_dot_)be
- Re: [xsl] Source code formatting, Imsieke, Gerrit, le-tex gerrit(_dot_)imsieke(_at_)le-tex(_dot_)de
- Re: [xsl] Source code formatting, John Lumley john(_at_)saxonica(_dot_)com
- Re: [xsl] Source code formatting, Piez, Wendell A. (Fed) wendell(_dot_)piez(_at_)nist(_dot_)gov
- Re: [xsl] Source code formatting, Imsieke, Gerrit, le-tex gerrit(_dot_)imsieke(_at_)le-tex(_dot_)de
- [Slightly Off Topic] mail server [was: Re: [xsl] Source code formatting], Geert Bormans geert(_at_)gbormans(_dot_)telenet(_dot_)be
- Re: [Slightly Off Topic] mail server [was: Re: [xsl] Source code formatting], Imsieke, Gerrit, le-tex gerrit(_dot_)imsieke(_at_)le-tex(_dot_)de
- Re: [Slightly Off Topic] mail server [was: Re: [xsl] Source code formatting],
Piez, Wendell A. (Fed) wendell(_dot_)piez(_at_)nist(_dot_)gov <=
- Re: [Slightly Off Topic] mail server [was: Re: [xsl] Source code formatting], Peter Flynn peter(_at_)silmaril(_dot_)ie
Re: [xsl] Source code formatting, Dimitre Novatchev dnovatchev(_at_)gmail(_dot_)com
Re: [xsl] Source code formatting, Pieter Lamers pieter(_dot_)lamers(_at_)benjamins(_dot_)nl
|
|
|