unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Emanuel Berg <moasenwood@zoho.eu>
To: help-gnu-emacs@gnu.org
Cc: emacs-devel@gnu.org
Subject: Biblatex issue with pdflatex and biber and special chars
Date: Thu, 18 Apr 2019 04:45:03 +0200	[thread overview]
Message-ID: <861s20821c.fsf@zoho.eu> (raw)

Biblatex won't compile with pdflatex and
biber [versions in Elisp code, last] if a book
entry key contains wierd chars. This wasn't an
issue until I upgraded my system, but now
it is.

I think the effect of this workaround should be
added to
`bibtex-autokey-titleword-change-strings' by
default, as wierd chars in keys in
computer systems (keys that are never shown
anyway) are only confusing and, as we have seen
now, from time to time cause problems.

It once worked, so it isn't a bug in Emacs, it
is either a bug or a policy change in the
pdflatex a/o biber camps, but still, I don't
think it makes any real sense having such chars
in keys.

Note that this only affects the *key*
themselves, not the Biblatex entries (examples
below) nor the PDF output [1] once compiled.


    @book{3-x-kapuscinski,
      author     = {Ryszard Kapuściński},
      ISBN       = {978-91-7429-206-0},
      publisher  = {Bonnier},
      title      = {3 x Kapuściński},
      year       = 1993
    }

    @book{med-ornen-mot-polen,
      author     = {Salomon August Andrée and Knut Frænkel and Nils Strindberg},
      ISBN       = {91-7102-085-3},
      publisher  = {Niloé (Bonniers)},
      title      = {Med Örnen mot polen},
      year       = {1978 (1930)}
    }


;; away with Swedish chars
;; and other special chars
;; as DNC w/ either
;; pdfTeX 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian)
;; kpathsea version 6.2.2
;; or
;; biber version: 2.7 (beta)
(cl-loop
 for (r w)
 in `(
      ("ä" "a")
      ("Ä" "A")
      ("å" "a")
      ("Å" "A")
      ("é" "e")
      ("ö" "o")
      ("Ö" "O")
      ("ń" "n")
      ("ś" "s")
      ;; add more here
      )
 do  (map-put bibtex-autokey-titleword-change-strings r w) )


[1] http://user.it.uu.se/~embe8573/books/books.pdf

-- 
underground experts united
http://user.it.uu.se/~embe8573




                 reply	other threads:[~2019-04-18  2:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=861s20821c.fsf@zoho.eu \
    --to=moasenwood@zoho.eu \
    --cc=emacs-devel@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).