From: Ihor Radchenko <yantar92@gmail.com>
To: Dominik Schrempf <dominik.schrempf@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Question about cite_export basic
Date: Wed, 14 Sep 2022 10:57:01 +0800 [thread overview]
Message-ID: <87leqmy876.fsf@localhost> (raw)
In-Reply-To: <874jxbtly2.fsf@gmail.com>
Dominik Schrempf <dominik.schrempf@gmail.com> writes:
>> 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.
Parsing itself is not that hard, actually. We just need to follow
http://www.bibtex.org/SpecialSymbols/. However, it will be better if the
parsing is done on bibtex.el side.
If bibtex.el maintainer refuses to implement the request, we will just
do the parsing on Org side.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
next prev parent reply other threads:[~2022-09-14 2:56 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
2022-09-14 2:57 ` Ihor Radchenko [this message]
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=87leqmy876.fsf@localhost \
--to=yantar92@gmail.com \
--cc=dominik.schrempf@gmail.com \
--cc=emacs-orgmode@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/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).