IronPort-PHdr: =?us-ascii?q?9a23=3A72blghD+bafnmfnkBxuuUyQJPHJ1kqjoPgMT9p?=
               =?us-ascii?q?ssgq5PdaLmxZn5IUjD/q811g3TUIHS+qgCluzX9qDtWGAN5ZyMqn9EfJEfHx?=
               =?us-ascii?q?MGiMBDmQsmDYbFDEDgN/flYmQ8G9gKT15q+Xy3cABVFc/yakeUoyi06jgfSV?=
               =?us-ascii?q?3kLQQgAOPzF8bJitivkfio8sjQah9MrDSnbL58NhS7qwnK8M4MjtgqMb4/ny?=
               =?us-ascii?q?PAuWAAYOFK3SVtLFOXkQz745Kz9YRn2ypKtv8v7c9NV6nhOaMiQu8QFywoZl?=
               =?us-ascii?q?g8/9ajrhzfVU2P638bB30RiQZNChPZ4QvSUI38vyXgt+d71DLcOtf5FOpmYz?=
               =?us-ascii?q?mp4qZ1RROtsx8pbGZlokfQjME4zLhWpBuw/VpixY+RYIyUOPd6dK7HcpUWSD?=
               =?us-ascii?q?gJWMEZTCFHDo6mCulHR+McIeZVqZX8rFoSvFO/AwerHubm1j5PgDf/w6Q71+?=
               =?us-ascii?q?0rFQyO0hYnGpoCt3HdrdO9M6l3M6j9z6DSyR3Ndf5b1y385Y7EaVYmu/7NFb?=
               =?us-ascii?q?N8fMzNyFU+QhvfhwbYoojkMjWJk+UV5jnFqbowE7PyzTB/+GQT6nC1y8whi5?=
               =?us-ascii?q?fEnNcPx1TN5H8/3YA0YN21SUJ2ZdSpCpQWuyzJUuk+Cs4kXWxsvz43j7Mcvp?=
               =?us-ascii?q?vuNisD0pAPyQTSZvKdcoWO7gmlU/yea2Qd5jotaPekihC+/FL1gO71TM2c3k?=
               =?us-ascii?q?xHoyRfk9TKumtL0AbcoJviKLM17gKq3jCB0BrW4+dPLBUvlKbVHJUmx6Y5ip?=
               =?us-ascii?q?sZtUmaRH3MlU77jbGbegAfwsb0sbS1Wrz9vdfcLYJwgxCkdLkom4m/DOU0Pw?=
               =?us-ascii?q?wEUnKUv+ixhvXv+kjwQbMCifNT8OGRs5nAIewVvKO0DRVU34Av8FC4FTju3N?=
               =?us-ascii?q?kDnHYBJU5IY1rW0c65axeffbamVb+2mBy0nS1uxuzaM7GEYN2FNXXFnLr7PP?=
               =?us-ascii?q?5850Na1Asv3IVa7pNQBKsGJaG7UUvwudrESx4hZl3qhba3ToQgkN1GCgftSu?=
               =?us-ascii?q?eDPajfsEGF/Lc1Lu2FddVTpTD8bvgo5vLjiXU0g1BbcaT6uPlfIH2+APliJF?=
               =?us-ascii?q?2UJHT2hdJUW2QDpA4WQvbnhVOYUDNVa230WLgzrGJeasruHcLYS4ahjabUli?=
               =?us-ascii?q?SyBJl+aHpLB16WEHrue57CXO0DInH3QIcpgnkPUr6vTJUk3BeluVrhyrZpGe?=
               =?us-ascii?q?HT/zURqZPp0NUmr/2Wjxw58iZ4StiMy2zYBX8hhXsGHnVlucI36Vw40FqI1r?=
               =?us-ascii?q?J0xuBVBcAGre0cSR80bNbVh+UoF839HAXbcZ+MWAS6X9rgBis+K7B5i9ZcbU?=
               =?us-ascii?q?t7ENi6iQvfmSWsHvkSjbPDBZo/9r/Q0irGPN5zjXnB06Ylgh8tRc4HI2Sigu?=
               =?us-ascii?q?QmrVrpCoXEkluUm+ORTYpAh3CfzG6Y1iLOpkxcWR8qF7jDXDUfa0raoNDz61?=
               =?us-ascii?q?nNCbOjW/wrNQ5IyMjKLaUvCJWhlVJdWPLqI8jTeUq/gWq9CwyJy7WAd8ztYW?=
               =?us-ascii?q?pV0CjGCUcCmhwe5j7Xa05uVmHw/iSAVHRnDjeNKwv0/PN7qW+nQ0N81AyMY0?=
               =?us-ascii?q?B7lvK09hMTmf2AWqYT07YD628qrzR5Gkr43sqDWoTG91onLfgaP4tuhTUPnX?=
               =?us-ascii?q?jUvAF8IJG6erpvglcPKUJquUKr1xh2BohEm8UwozUmwVkXS+rQ3VVfejefxZ?=
               =?us-ascii?q?21NKfQLzy4/xm1b4bYwFzT3syX96ED87I/sVqp72TLXgIytm5q1dVYyS7W/p?=
               =?us-ascii?q?LREA8bSo78SG457RV3qavbby8x/MXTz3ImYszW+nfSntkuAuUi0BOpedxSZb?=
               =?us-ascii?q?iFGAHFGMofH8GyKeYulgvhflceMetV7qJxI9K+eq7MxvuwJOg51mHD7ywP8M?=
               =?us-ascii?q?Vn30mL7SY5VuPYw8NP3aSDxgXeHz60hQW9r8+xnppLLTQCTHaixm7jHoE0BO?=
               =?us-ascii?q?U6dNQFBGGlLtWw3ck4iJjwHXlC+xaiAVgCxcOkKy2Jd1K70gpX2kAa53egnG?=
               =?us-ascii?q?Ouxjhw2Wh4/Jra5zTHxqHZTDRCP2dKQGd4ilK1ftq6ld0XUlKpYg4lj12i/0?=
               =?us-ascii?q?monvEH9pQ6FHHaRAJzRwazN3trC/TiuKCPbsBV6Z4uvT4RV/6zMwjDF+zN5i?=
               =?us-ascii?q?AC2iamJFNwgTA2czbz5cf3hRF3hnicIXB/tzzeY84inBo=3D?=
Message-ID:  <201811262244.wAQMi0DM029290@freefriends.org>
Date:         Mon, 26 Nov 2018 22:44:00 GMT
Reply-To:     Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender:       Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From:         Karl Berry <karl@FREEFRIENDS.ORG>
Subject: Re: bibtex futures: url, doi, ?
To:           LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <0629820000734093.WA.sergio.callegarigmail.com@listserv.uni-heidelberg.de>
Precedence: list
Envelope-To: <rainer.schoepf@gmx.net>
Status: R

Hi Sergio,

    a new bibtex release capable of utf-8 sorting and to provide some
    new fields for doi and url.

Well, I was just throwing out some ideas. Oren was looking for feedback.
So far I think the most likely outcome is "do nothing". It's unclear
whether changes like this would cause more problems than they would solve.

    It seems to me that most of these issues are ready solved by pybtex

I didn't know about it. Thanks for mentioning it. It has some nice
features. Clearly no new processor can "solve" the question of new
fields in the standard styles.

As for Unicode sorting, I could not discern how to tell pybtex to do
it. There is a bare statement it is "Unicode aware" but I found no
examples.

    The second one is to support other "transformation machineries"

Have extended machineries been implemented, or just the framework?
Again, I could find no particular doc or examples. Maybe I missed it.

    The only potential issue with pybtex seems to be that its
    implementation is in python and I do not know if this is accepted

There is no problem in principle with Python in TeX (Live). There are a
number of Python programs in TL now. However,

(1) it would need to be uploaded to CTAN first (which would be nice in
any case; maybe the author would be willing? Can you ask?)

(2) for TL, the program would need to be "self-locating" based on $0 and
not require users to run setup.py or anything else. I couldn't tell if
that would "just work" or not.

Thanks again for mentioning it ... but also, this is not the list to
follow up with these details about pybtex. Please reply to me
individually, ok? --thanks, karl.