top | item 44134608 (no title) growlNark | 9 months ago Why do they use "and"? Why not use an unambiguous joining token like `/`? This just feels like an abuse of informal language to produce fundamentally formal data.As it stands, it certainly does not resemble readable or parseable english. discuss order hn newest robotresearcher|9 months ago It’s BibTex format. It’s ancient, ubiquitous, very fussy, and reads badly for humans in some cases. But it’s what we’ve been using since the 1980s.‘Better’ formats have been proposed but none have stuck nearly as well. It works, and there’s tooling for it. bowsamic|9 months ago It’s how the bibtex author field is defined. You don’t get free choice here. As far as I’m aware bibtex defines and as the separatorhttps://bibtex.eu/fields/author/ growlNark|9 months ago Yea but like... why? Typically you use human language operators to produce readable phrases, and this doesn't even approach readable english. load replies (2)
robotresearcher|9 months ago It’s BibTex format. It’s ancient, ubiquitous, very fussy, and reads badly for humans in some cases. But it’s what we’ve been using since the 1980s.‘Better’ formats have been proposed but none have stuck nearly as well. It works, and there’s tooling for it.
bowsamic|9 months ago It’s how the bibtex author field is defined. You don’t get free choice here. As far as I’m aware bibtex defines and as the separatorhttps://bibtex.eu/fields/author/ growlNark|9 months ago Yea but like... why? Typically you use human language operators to produce readable phrases, and this doesn't even approach readable english. load replies (2)
growlNark|9 months ago Yea but like... why? Typically you use human language operators to produce readable phrases, and this doesn't even approach readable english. load replies (2)
robotresearcher|9 months ago
‘Better’ formats have been proposed but none have stuck nearly as well. It works, and there’s tooling for it.
bowsamic|9 months ago
https://bibtex.eu/fields/author/
growlNark|9 months ago