From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: BUG: % is comment in btx fields
Date: Tue, 9 May 2017 11:19:46 +0200 [thread overview]
Message-ID: <19so48cp6cn6u.dlg@nililand.de> (raw)
In-Reply-To: <20170508175608.54a12771@zoo.hsd1.co.comcast.net>
Am Mon, 8 May 2017 17:56:08 -0600 schrieb Alan Braslau:
> So bibtex has a funny way of dealing with comments, and do we really
> care about Scribe?
biber handles comments differently than bibtex, see e.g.
https://tex.stackexchange.com/questions/261261/are-comments-discouraged-in-a-bibtex-file
As a thumbrule one can sum the rule up that *inside* field text
comment chars should be input according the tex rule for the field
*type*. That means that normal textfields should use \%, while url's
and other verbatim-like field can use %.
> We made the choice NOT to remain *strictly* bibtex
> compatible, after all bibtex is limited to ASCII 7-bit!
That's not true bibtex has no real problem with 8-bit-encodings, and
works even quite often quite good with utf8 (when you don't try to
use at places where it can be broken into parts.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-05-09 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 21:44 Henri Menke
2017-05-08 22:05 ` Martin Schröder
2017-05-08 22:27 ` Alan Braslau
2017-05-08 23:27 ` Henri Menke
2017-05-08 23:56 ` Alan Braslau
2017-05-09 9:19 ` Ulrike Fischer [this message]
2017-05-09 0:15 ` Rik Kabel
2017-05-09 1:40 ` Henri Menke
2017-05-09 1:48 ` Rik Kabel
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=19so48cp6cn6u.dlg@nililand.de \
--to=news3@nililand.de \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).