emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dominik Schrempf <dominik.schrempf@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Question about cite_export basic
Date: Tue, 13 Sep 2022 15:53:13 +0200	[thread overview]
Message-ID: <874jxbtly2.fsf@gmail.com> (raw)
In-Reply-To: <87h71f26af.fsf@localhost>

Ihor Radchenko <yantar92@gmail.com> writes:

> Dominik Schrempf <dominik.schrempf@gmail.com> writes:
>
>>   title           = {{Introduction to Markov Chain Monte Carlo}},
>> ...
>> Is rendered as
>>
>> Geyer, Charles J (2011). {Introduction to Markov Chain Monte Carlo}, CRC press.
>>
>> In particular, the curly braces are printed. Curly braces are often
>> used in bib files to indicate that the capitalization is to be
>> preserved.
>>
>> Do we want to change the default behavior of the basic processor so
>> that it correctly handles these cases?
>
> This makes sense. However, I see it as something to be done by
> bibtex.el; not by Org. Or we may need to write a small exporter for
> BibTeX fields specifically. So that
> http://www.bibtex.org/SpecialSymbols/ is obeyed. We may also handle
> upcasing the title words in such exporter.
>
> For now, I reached Emacs devs asking to provide the parsing within
> bibtex.el. See https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57712
> Lets see what they reply first.
>

Dear Ihor!

Thank you for posting the BibTeX brace problem upstream. From what I can
see by reading through the conversation, we are going down a rabbit
hole. It seems to be pretty difficult to convert a BibTeX entry to a
proper ascii string (I think this is what the basic export processor is
doing). Is that true?

Not sure how to proceed. I do not think that post processing
`bibtex-parse-entry` output which seems to contain LaTeX code makes
sense.

Best,
Dominik


  reply	other threads:[~2022-09-13 14:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  9:08 Question about cite_export basic Dominik Schrempf
2022-09-09 10:20 ` Alain.Cochard
2022-09-09 10:38   ` Ihor Radchenko
2022-09-09 10:47     ` Alain.Cochard
2022-09-10  4:38 ` Ihor Radchenko
2022-09-13 13:53   ` Dominik Schrempf [this message]
2022-09-14  2:57     ` Ihor Radchenko
2024-02-29  9:25       ` Ihor Radchenko

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.orgmode.org/

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

  git send-email \
    --in-reply-to=874jxbtly2.fsf@gmail.com \
    --to=dominik.schrempf@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    /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/org-mode.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).