From: Rasmus <rasmus@gmx.us>
To: help-gnu-emacs@gnu.org
Subject: Re: Long file names in Dired
Date: Fri, 24 Apr 2015 12:19:22 +0200 [thread overview]
Message-ID: <87vbgl25hx.fsf@gmx.us> (raw)
In-Reply-To: 87618lvpf5.fsf@mbork.pl
Marcin Borkowski <mbork@mbork.pl> writes:
>>> I. HATE. BIBTEX. WITH. A. PASSION.
>>> [...]
>>
>> I find the format OK. I can't imagine a vastly superior format for
>> metadata...
>
> 1. Multiple authors are separated with the five-character string
> " and ".
I type quickly enough for this not to bother me. Perhaps ";" would be
better, but for the sake of comparability I can live with " and ". OTOH
it may make human parsing more easy when reading the bib file.
> Can you imagine a more stupid idea? What if you want to quote
> an anonymous report whose author field should say "National Aeronautics
> and Space Administration"? Yes, you /can/ quote the " and ", but this
> shouldn't be even needed.
Author = {{National Aeronautics and Space Administration}}
> 2. BibTeX separates the author name into (at most) four components,
> called "first", "last", "von" and "jr". No support for: Chinese names
> (not fitting into this format)e and names in some other languages (I'm
> forgetting now which ones).
Another flaw is the auto-guessing of names e.g. for three names one must
use "last, first middle" vs "first last" or "last, first" for two names.
> 3. What about alphabetic sorting in various languages?
This is orthogonal to the format. I believe Biber reads unicode.
> 4. Since BibTeX is aimed (after all) at a typesetting system, what about
> diferent hyphenation patterns? Imagine an article written in Polish,
> citing a paper by a German (so the name should be hyphenated differently
> than the rest of the document), the paper being in English, and
> published by an Italian university. Where's support for that (i.e.,
> language field for the author, title etc.)?
Biblatex will read language field. I don't know how it uses it. In any
case, that's orthogonal to the bibtex format as a "database".
> (Not to mention several authors from various langauge backgrounds.)
If there's a name you can't type, I guess it's the fault of unicode.
> 5. What about all these funny characters not found in English, and in
> particular sorting using them? (See the docs for the xindy indexing
> tool for examples of nontrivial problems regarding locale-aware
> sorting.)
This is a flaw with the bibtex program. Biber is better.
BTW: Emacs 24 can't do local-aware sorting (but string-collate-lessp is in
25). This would suggest to me that it's a nontrivial problem.
> 6. What about custom citation styles? Have you seen the syntax of the
> bst files? If yes, you know the pain, and if not, you'd better not look
> at them, for your own good...
Yes. I used to use custombib or whatever it was called to generate bst
files. Pain.
Again, this is orthogonal to the bibtex file-format.
> 7. BibTeX is not really "case-sensitive" or "case-insensitive", it's
> "case-destroying". IOW, /you have to quote capital letters in titles/
> so that BibTeX doesn't convert them to lowercase.
I think you can use: {{}}.
> BTW, BibLaTeX addresses (AFAIK) problems 3, 5, 6 and 7.
Would 3 not be biber? For 4 perhaps you can use the langid field (pp. 24
in the "texdoc biblatex" in TL14). I don't know if it's as extensive as
you need.
> The amsrefs package addresses problems 1, 2, 4, 6 and 7.
I don't know it. The AMS math packages are good quality.
> Again: nice, and thanks for the tips. But still, BibTeX is a wrong tool
> for that.
I'm using the *format*, not the binary "bibtex". Biber is good, and via
reftex Emacs has good support for the bibtex format.
> Note that no BibTeX based solution helps /if I want to be able to move
> files between directories/.
In the above system you'd move *folders* rather than files. An entry is a
container (folder) of:
{metadata, article, notes, data/program}
You could have that in a single file (tar), but why bother?
—Rasmus
--
And when I’m finished thinking, I have to die a lot
next prev parent reply other threads:[~2015-04-24 10:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1494.1429830642.904.help-gnu-emacs@gnu.org>
2015-04-24 1:26 ` Long file names in Dired Emanuel Berg
2015-04-24 9:01 ` Marcin Borkowski
2015-04-24 9:12 ` Rasmus
2015-04-24 9:37 ` Marcin Borkowski
2015-04-24 10:19 ` Rasmus [this message]
2015-04-24 21:02 ` Marcin Borkowski
2015-04-24 21:10 ` Marcin Borkowski
[not found] ` <mailman.1511.1429866115.904.help-gnu-emacs@gnu.org>
2015-04-25 1:29 ` Emanuel Berg
2015-04-25 8:18 ` Marcin Borkowski
[not found] ` <mailman.1581.1429950075.904.help-gnu-emacs@gnu.org>
2015-04-25 11:20 ` Emanuel Berg
2015-05-03 22:59 ` Marcin Borkowski
[not found] ` <mailman.2273.1430694000.904.help-gnu-emacs@gnu.org>
2015-05-04 0:22 ` Emanuel Berg
2015-05-04 0:41 ` Emanuel Berg
2015-04-23 23:10 Marcin Borkowski
2015-04-24 0:38 ` Bob Proulx
2015-04-24 6:29 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbgl25hx.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.