From: "Paul E. McKenney" <paulmck@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
rcu@vger.kernel.org
Subject: Re: [PATCH 07/10] docs: RCU: RTFP: fix bibtex entries
Date: Tue, 21 Apr 2020 17:42:08 -0700 [thread overview]
Message-ID: <20200422004208.GI17661@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200421212850.616db8b0@coco.lan>
On Tue, Apr 21, 2020 at 09:29:06PM +0200, Mauro Carvalho Chehab wrote:
> Em Tue, 21 Apr 2020 10:52:25 -0700
> "Paul E. McKenney" <paulmck@kernel.org> escreveu:
>
> > On Tue, Apr 21, 2020 at 10:43:29AM -0700, Paul E. McKenney wrote:
> > > On Tue, Apr 21, 2020 at 07:04:08PM +0200, Mauro Carvalho Chehab wrote:
> > > > There are several troubles at the bibtex entries with
> > > > prevent them to be processed by LaTeX:
> > > >
> > > > - On LaTeX, comment lines start with '%', but here, comments
> > > > are starting with "#";
> > > > - Underlines should be escaped.
> > > > - While the best would be to use \url{} for all URL entries,
> > > > let's do it at least for a couple that would otherwise
> > > > produce errors on LaTeX.
> > > >
> > > > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> > >
> > > Another approach might be just to link to a public repo containing
> > > cleaned-up versions of these bibliography entries:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/perfbook.git/tree/bib/RCU.bib
> > >
> > > That would have the advantage of keeping this information in only one
> > > place, and reducing the number of updates required.
>
> Yeah. I didn't know you had it somewhere else.
>
> > >
> > > Thoughts?
> >
> > OK, I should have read the next patch in the series, where you convert
> > into a Sphinx-compatible bibliography. Except that you had to convert
> > the bibtex entries by hand to produce the Sphinx-compatible entries?
>
> No, but it still required a lot of manual work.
>
> I manually converted the file to ReST. That was the easiest part.
>
> Then, I used sphinx-build to convert it into a LaTeX file and changed
> the produced .tex for it to use the .bib file.
>
> The last step was the hardest one. I'm not familiar with LaTeX. I did
> several attempts to produce an output with the same kind of captions
> as the original file, but I was unable to generate it.
>
> So, I ended doing the final step the hard way: I used XeLaTeX to produce
> a PDF file. Then, I manually copied the entries from the output back into
> the ReST file, carefully adjusting the captions, in order for them to
> point to the right places.
>
> Before that, I tried to use a few Sphinx BibTeX extensions, but they
> are not complete: they were unable to parse some types of entries.
> If I'm not mistaken (I did it some time ago, on another computer),
> the ones I tested crashed when trying to parse some entries, like
> '@Conference'.
OK, that sounds decidedly non-trivial. :-(
> > That will get a bit ugly when it comes time to add more entries.
> >
> > Or was the conversion of bibliography entries automated?
>
> I suspect it should be possible to automate it, but, as I said,
> I'm not too familiar with LaTeX.
In the meantime, would it work to just reference the RCU.bib URL above?
Thanx, Paul
next prev parent reply other threads:[~2020-04-22 0:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 17:04 [PATCH 00/10] Manually convert RCU text files to ReST format Mauro Carvalho Chehab
2020-04-21 17:04 ` [PATCH 01/10] docs: RCU: convert checklist.txt to ReST Mauro Carvalho Chehab
2020-04-21 17:04 ` [PATCH 02/10] docs: RCU: convert lockdep-splat.txt " Mauro Carvalho Chehab
2020-04-21 17:04 ` [PATCH 03/10] docs: RCU: convert lockdep.txt " Mauro Carvalho Chehab
2020-04-21 17:04 ` [PATCH 04/10] docs: RCU: convert rculist_nulls.txt " Mauro Carvalho Chehab
2020-04-21 17:04 ` [PATCH 05/10] docs: RCU: convert torture.txt " Mauro Carvalho Chehab
2020-04-21 17:04 ` [PATCH 06/10] docs: RCU: convert rcuref.txt " Mauro Carvalho Chehab
2020-04-21 17:04 ` [PATCH 07/10] docs: RCU: RTFP: fix bibtex entries Mauro Carvalho Chehab
2020-04-21 17:43 ` Paul E. McKenney
2020-04-21 17:52 ` Paul E. McKenney
2020-04-21 19:29 ` Mauro Carvalho Chehab
2020-04-22 0:42 ` Paul E. McKenney [this message]
2020-04-21 17:04 ` [PATCH 08/10] docs: RCU: convert RTFP.txt to ReST Mauro Carvalho Chehab
2020-04-21 17:04 ` [PATCH 09/10] docs: RCU: stallwarn.txt: convert it " Mauro Carvalho Chehab
2020-04-21 17:04 ` [PATCH 10/10] docs: RCU: rculist_nulls.rst: don't duplicate chapter names Mauro Carvalho Chehab
2020-04-21 17:58 ` [PATCH 00/10] Manually convert RCU text files to ReST format Paul E. McKenney
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=20200422004208.GI17661@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=corbet@lwn.net \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mchehab+huawei@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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.
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).