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://www.youtube.com/watch?v=YmfzhK4aR1c
> > 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 <http://www.mulberrytech.com/xsl/xsl-list>
> > EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/554170> (by 
> > email)
> > XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> > EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/225679> (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
--~--