e0984a43a9
This deprecates the use of the external pandoc-citeproc
filter; citation processing is now built in to pandoc.
* Add dependency on citeproc library.
* Add Text.Pandoc.Citeproc module (and some associated unexported
modules under Text.Pandoc.Citeproc). Exports `processCitations`.
[API change]
* Add data files needed for Text.Pandoc.Citeproc: default.csl
in the data directory, and a citeproc directory that is just
used at compile-time. Note that we've added file-embed as a mandatory
rather than a conditional depedency, because of the biblatex
localization files. We might eventually want to use readDataFile
for this, but it would take some code reorganization.
* Text.Pandoc.Loging: Add `CiteprocWarning` to `LogMessage` and use it
in `processCitations`. [API change]
* Add tests from the pandoc-citeproc package as command tests (including
some tests pandoc-citeproc did not pass).
* Remove instructions for building pandoc-citeproc from CI and
release binary build instructions. We will no longer distribute
pandoc-citeproc.
* Markdown reader: tweak abbreviation support. Don't insert a
nonbreaking space after a potential abbreviation if it comes right before
a note or citation. This messes up several things, including citeproc's
moving of note citations.
* Add `csljson` as and input and output format. This allows pandoc
to convert between `csljson` and other bibliography formats,
and to generate formatted versions of CSL JSON bibliographies.
* Add module Text.Pandoc.Writers.CslJson, exporting `writeCslJson`. [API
change]
* Add module Text.Pandoc.Readers.CslJson, exporting `readCslJson`. [API
change]
* Added `bibtex`, `biblatex` as input formats. This allows pandoc
to convert between BibLaTeX and BibTeX and other bibliography formats,
and to generated formatted versions of BibTeX/BibLaTeX bibliographies.
* Add module Text.Pandoc.Readers.BibTeX, exporting `readBibTeX` and
`readBibLaTeX`. [API change]
* Make "standalone" implicit if output format is a bibliography format.
This is needed because pandoc readers for bibliography formats put
the bibliographic information in the `references` field of metadata;
and unless standalone is specified, metadata gets ignored.
(TODO: This needs improvement. We should trigger standalone for the
reader when the input format is bibliographic, and for the writer
when the output format is markdown.)
* Carry over `citationNoteNum` to `citationNoteNumber`. This was just
ignored in pandoc-citeproc.
* Text.Pandoc.Filter: Add `CiteprocFilter` constructor to Filter.
[API change] This runs the processCitations transformation.
We need to treat it like a filter so it can be placed
in the sequence of filter runs (after some, before others).
In FromYAML, this is parsed from `citeproc` or `{type: citeproc}`,
so this special filter may be specified either way in a defaults file
(or by `citeproc: true`, though this gives no control of positioning
relative to other filters). TODO: we need to add something to the
manual section on defaults files for this.
* Add deprecation warning if `upandoc-citeproc` filter is used.
* Add `--citeproc/-C` option to trigger citation processing.
This behaves like a filter and will be positioned
relative to filters as they appear on the command line.
* Rewrote the manual on citatations, adding a dedicated Citations
section which also includes some information formerly found in
the pandoc-citeproc man page.
* Look for CSL styles in the `csl` subdirectory of the pandoc user data
directory. This changes the old pandoc-citeproc behavior, which looked
in `~/.csl`. Users can simply symlink `~/.csl` to the `csl`
subdirectory of their pandoc user data directory if they want
the old behavior.
* Add support for CSL bibliography entry formatting to LaTeX, HTML,
Ms writers. Added CSL-related CSS to styles.html.
5.1 KiB
5.1 KiB
% pandoc -f biblatex -t markdown -s
@comment{
Adapted from biblatex-example.bib
Formatted with pandoc and chicago-author-date.csl, 2013-10-23:
(Padhye, Firoiu, and Towsley 1999)
Padhye, Jitendra, Victor Firoiu, and Don Towsley. 1999. “A Stochastic
Model of TCP Reno Congestion Avoidance and Control.” Technical report
99-02. Amherst, Mass.: University of Massachusetts.
Formatted with pandoc and apa.csl, 2013-10-23:
(Padhye, Firoiu, & Towsley, 1999)
Padhye, J., Firoiu, V., & Towsley, D. (1999). *A stochastic model of TCP
Reno congestion avoidance and control* (technical report No. 99-02).
Amherst, Mass.: University of Massachusetts.
}
@Report{padhye,
author = {Padhye, Jitendra and Firoiu, Victor and Towsley, Don},
title = {A Stochastic Model of {TCP Reno} Congestion Avoidance and
Control},
type = {techreport},
institution = {University of Massachusetts},
date = 1999,
number = {99-02},
location = {Amherst, Mass.},
hyphenation = {american},
sorttitle = {A Stochastic Model of TCP Reno Congestion Avoidance and
Control},
indextitle = {Stochastic Model of {TCP Reno} Congestion Avoidance and Control,
A},
annotation = {This is a report entry for a technical report. Note
the format of the type field in the database file
which uses a localization key. The number of the report is
given in the number field. Also note the
sorttitle and indextitle fields},
abstract = {The steady state performance of a bulk transfer TCP flow
(i.e., a flow with a large amount of data to send, such as FTP
transfers) may be characterized by three quantities. The first
is the send rate, which is the amount of data sent by the
sender in unit time. The second is the throughput, which is
the amount of data received by the receiver in unit time. Note
that the throughput will always be less than or equal to the
send rate due to losses. Finally, the number of non-duplicate
packets received by the receiver in unit time gives us the
goodput of the connection. The goodput is always less than or
equal to the throughput, since the receiver may receive two
copies of the same packet due to retransmissions by the
sender. In a previous paper, we presented a simple model for
predicting the steady state send rate of a bulk transfer TCP
flow as a function of loss rate and round trip time. In this
paper, we extend that work in two ways. First, we analyze the
performance of bulk transfer TCP flows using more precise,
stochastic analysis. Second, we build upon the previous
analysis to provide both an approximate formula as well as a
more accurate stochastic model for the steady state throughput
of a bulk transfer TCP flow.},
file = {ftp://gaia.cs.umass.edu/pub/Padhey99-markov.ps},
}
^D
---
nocite: '[@*]'
references:
- abstract: 'The steady state performance of a bulk transfer TCP flow
(i.e., a flow with a large amount of data to send, such as FTP
transfers) may be characterized by three quantities. The first is
the send rate, which is the amount of data sent by the sender in
unit time. The second is the throughput, which is the amount of data
received by the receiver in unit time. Note that the throughput will
always be less than or equal to the send rate due to losses.
Finally, the number of non-duplicate packets received by the
receiver in unit time gives us the goodput of the connection. The
goodput is always less than or equal to the throughput, since the
receiver may receive two copies of the same packet due to
retransmissions by the sender. In a previous paper, we presented a
simple model for predicting the steady state send rate of a bulk
transfer TCP flow as a function of loss rate and round trip time. In
this paper, we extend that work in two ways. First, we analyze the
performance of bulk transfer TCP flows using more precise,
stochastic analysis. Second, we build upon the previous analysis to
provide both an approximate formula as well as a more accurate
stochastic model for the steady state throughput of a bulk transfer
TCP flow.'
annote: This is a report entry for a technical report. Note the format
of the type field in the database file which uses a localization
key. The number of the report is given in the number field. Also
note the sorttitle and indextitle fields
author:
- family: Padhye
given: Jitendra
- family: Firoiu
given: Victor
- family: Towsley
given: Don
genre: technical report
id: padhye
issued: 1999
language: 'en-US'
number: '99-02'
publisher: University of Massachusetts
publisher-place: 'Amherst, Mass.'
title: A stochastic model of TCP Reno congestion avoidance and control
type: report
---