<p dir="ltr">I have a naive question? There is a possibility of calling PERL or Python from latex using perltex package. Is this possible in xetex? Will this feature be good enough?<br>
Best,</p>
<div class="gmail_quote">On 2 Jul 2015 20:58, <<a href="mailto:xetex-request@tug.org">xetex-request@tug.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send XeTeX mailing list submissions to<br>
<a href="mailto:xetex@tug.org">xetex@tug.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://tug.org/mailman/listinfo/xetex" rel="noreferrer" target="_blank">http://tug.org/mailman/listinfo/xetex</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:xetex-request@tug.org">xetex-request@tug.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:xetex-owner@tug.org">xetex-owner@tug.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of XeTeX digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: \(pdf)mdfivesum (Apostolos Syropoulos)<br>
2. Re: \(pdf)mdfivesum (Joseph Wright)<br>
3. Re: \(pdf)mdfivesum (George N. White III)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 2 Jul 2015 14:53:16 +0000<br>
From: Apostolos Syropoulos <<a href="mailto:asyropoulos@yahoo.com">asyropoulos@yahoo.com</a>><br>
To: "XeTeX (Unicode-based TeX) discussion." <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Subject: Re: [XeTeX] \(pdf)mdfivesum<br>
Message-ID:<br>
<<a href="mailto:1865847164.1043798.1435848796532.JavaMail.yahoo@mail.yahoo.com">1865847164.1043798.1435848796532.JavaMail.yahoo@mail.yahoo.com</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
> If MD5 is necessary for compatibility with some existing standard, so be<br>
> it; but it's not secure anymore and it shouldn't be used in any new<br>
> design<br>
> where there's a concern about possible deliberate tampering, as opposed to<br>
> accidental errors. SHA1 is deprecated, too. I think SHA256 is the<br>
> current "best practice."<br>
><br>
<br>
<br>
<br>
So someone will step in and implement this primitive but then we will realize we<br>
need another primitive to handle the more advanced sha256. Programming languages<br>
<br>
have libraries for this and they do not modify the language to handle every new<br>
feature. So the best solution is to introduce some library mechanism that would<br>
<br>
make it possible to introduce new commands without affecting the kernel.<br>
<br>
A.S.<br>
<br>
<br>
----------------------<br>
Apostolos Syropoulos<br>
Xanthi, Greece<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Thu, 2 Jul 2015 16:09:36 +0100<br>
From: Joseph Wright <<a href="mailto:joseph.wright@morningstar2.co.uk">joseph.wright@morningstar2.co.uk</a>><br>
To: <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Subject: Re: [XeTeX] \(pdf)mdfivesum<br>
Message-ID: <<a href="mailto:55955430.9060908@morningstar2.co.uk">55955430.9060908@morningstar2.co.uk</a>><br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
On 02/07/2015 05:54, <a href="mailto:mskala@ansuz.sooke.bc.ca">mskala@ansuz.sooke.bc.ca</a> wrote:<br>
> If MD5 is necessary for compatibility with some existing standard, so be<br>
> it; but it's not secure anymore and it shouldn't be used in any new design<br>
> where there's a concern about possible deliberate tampering, as opposed to<br>
> accidental errors. SHA1 is deprecated, too. I think SHA256 is the<br>
> current "best practice."<br>
<br>
Depends what you are using it for. Collisions are possible in MD5 so<br>
it's no longer suitable for cryptographic applications. Here, however,<br>
we are talking about avoiding the more prosaic issues of people having<br>
not-quite matching sources. (We are *not* talking about signing<br>
documents.) For the use case I have in mind MD5 will happily do the job.<br>
--<br>
Joseph Wright<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Thu, 2 Jul 2015 12:23:45 -0300<br>
From: "George N. White III" <<a href="mailto:gnwiii@gmail.com">gnwiii@gmail.com</a>><br>
To: "XeTeX (Unicode-based TeX) discussion." <<a href="mailto:xetex@tug.org">xetex@tug.org</a>><br>
Subject: Re: [XeTeX] \(pdf)mdfivesum<br>
Message-ID:<br>
<CAKTOP46Kqbef4c4n-tU+ZAJHPBJfWXLviwP1WAMKyco8X6md=<a href="mailto:Q@mail.gmail.com">Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Thu, Jul 2, 2015 at 12:09 PM, Joseph Wright <<br>
<a href="mailto:joseph.wright@morningstar2.co.uk">joseph.wright@morningstar2.co.uk</a>> wrote:<br>
<br>
> On 02/07/2015 05:54, <a href="mailto:mskala@ansuz.sooke.bc.ca">mskala@ansuz.sooke.bc.ca</a> wrote:<br>
> > If MD5 is necessary for compatibility with some existing standard, so be<br>
> > it; but it's not secure anymore and it shouldn't be used in any new<br>
> design<br>
> > where there's a concern about possible deliberate tampering, as opposed<br>
> to<br>
> > accidental errors. SHA1 is deprecated, too. I think SHA256 is the<br>
> > current "best practice."<br>
><br>
> Depends what you are using it for. Collisions are possible in MD5 so<br>
> it's no longer suitable for cryptographic applications. Here, however,<br>
> we are talking about avoiding the more prosaic issues of people having<br>
> not-quite matching sources. (We are *not* talking about signing<br>
> documents.) For the use case I have in mind MD5 will happily do the job.<br>
><br>
<br>
Maybe your use case is enough at present, but the other use cases (some<br>
already mentioned) may become important in the future. It makes sense<br>
to implement MD5 in a way that anticipates future additions/enhancements.<br>
<br>
--<br>
George N. White III <<a href="mailto:aa056@chebucto.ns.ca">aa056@chebucto.ns.ca</a>><br>
Head of St. Margarets Bay, Nova Scotia<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://tug.org/pipermail/xetex/attachments/20150702/e21e9128/attachment.html" rel="noreferrer" target="_blank">http://tug.org/pipermail/xetex/attachments/20150702/e21e9128/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
XeTeX mailing list<br>
<a href="mailto:XeTeX@tug.org">XeTeX@tug.org</a><br>
<a href="http://tug.org/mailman/listinfo/xetex" rel="noreferrer" target="_blank">http://tug.org/mailman/listinfo/xetex</a><br>
<br>
<br>
------------------------------<br>
<br>
End of XeTeX Digest, Vol 136, Issue 7<br>
*************************************<br>
</blockquote></div>