← Back to home
Comparison · Analytics

r2rtf vs textreuse

A side-by-side editorial comparison of r2rtf and textreuse — release velocity, themes, recent moves, and the top alternatives to consider.

r2rtf vs textreuse: at a glance

Featurer2rtftextreuse
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesclinical-reporting, rtf, internationalization, document-conversiontext-reuse, minhash, lsh, r-package
Last editorial update45m ago3h ago
WebsiteVisit →Visit →

What is r2rtf?

The clinical-report table engine learned Chinese, then learned to leave RTF entirely

r2rtf builds the RTF tables, listings and figures that go into clinical study reports, and its recent releases have been about widening who and what it can serve rather than changing how tables are composed. The 1.2.0 release added internationalization — a SimSun font path for Chinese characters plus hyphenation control — and 1.3.0 followed with write_docx() and write_html(), turning the LibreOffice conversion the package had documented into exported functions.

Read the full r2rtf trajectory →

What is textreuse?

A dormant text-matching package revived, shipped as 1.0.0, and kept current with the tidyverse.

textreuse detects reused and quoted passages across document collections using minhash and locality-sensitive hashing, with local alignment for inspecting the matches it finds. After years of inactivity, the package reached a 1.0.0 CRAN release in May 2026 that folded accumulated feature work into one version — encoding control on corpus construction, deterministic skipped-document bookkeeping, and an align_local() that returns an empty alignment instead of erroring on non-matching texts. The 1.0.2 release since then is pure compatibility maintenance.

Read the full textreuse trajectory →

r2rtf vs textreuse: editorial side-by-side

R
r2rtf
ANALYTICS
0.0

The clinical-report table engine learned Chinese, then learned to leave RTF entirely

◆ Current state

r2rtf builds the RTF tables, listings and figures that go into clinical study reports, and its recent releases have been about widening who and what it can serve rather than changing how tables are composed. The 1.2.0 release added internationalization — a SimSun font path for Chinese characters plus hyphenation control — and 1.3.0 followed with write_docx() and write_html(), turning the LibreOffice conversion the package had documented into exported functions.

◆ Where it's heading

Two threads run through the window. One is output reach: RTF remains the composition target, but the artifacts that come out of it now include DOCX and HTML, and page numbering can be made table-relative across multi-page tables. The other is durability under a moving R and font stack — the ANSI/Unicode converter was rebuilt, the LaTeX mapping table generated from code rather than shipped as sysdata, unlist() usage fixed for R 4.5, and graphics-device leaks that produced stray Rplots.pdf closed off.

◆ Prediction

Having exported DOCX and HTML conversion, the likely next step is filling in what those formats lose relative to RTF — pagination and footnote fidelity are the obvious gaps. The i18n path currently covers Chinese only, so additional font families are the other plausible direction.

T
textreuse
ANALYTICS
2.5

A dormant text-matching package revived, shipped as 1.0.0, and kept current with the tidyverse.

◆ Current state

textreuse detects reused and quoted passages across document collections using minhash and locality-sensitive hashing, with local alignment for inspecting the matches it finds. After years of inactivity, the package reached a 1.0.0 CRAN release in May 2026 that folded accumulated feature work into one version — encoding control on corpus construction, deterministic skipped-document bookkeeping, and an align_local() that returns an empty alignment instead of erroring on non-matching texts. The 1.0.2 release since then is pure compatibility maintenance.

◆ Where it's heading

The arc here is restoration rather than expansion. The work has gone into making the package survivable — silencing deprecated dplyr and tidyr selection and many-to-many join warnings, moving from dead Travis and AppVeyor configs to GitHub Actions, and validating across five R platform and version combinations. Release notes now lead with verification evidence rather than features, which is the signature of a maintainer stabilizing an inherited codebase.

◆ Prediction

Expect continued compatibility releases tracking tidyverse deprecations; nothing in these entries indicates new hashing or alignment capability is planned.

Alternatives to r2rtf and textreuse

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either r2rtf or textreuse.

See all r2rtf alternatives → · See all textreuse alternatives →

Recent activity from r2rtf and textreuse

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 20d agotextreuseCompatibility pass for current dplyr and tidyr
  2. 3mo agotextreuseCRAN resubmission fixing a moved README URL
  3. 3mo agotextreuse1.0.0 consolidates years of accumulated feature work
  4. 7mo agor2rtfDOCX and HTML output become exported functions
  5. 11mo agor2rtfChinese character support arrives via an i18n font path
  6. 1y agor2rtfText colour fixed for figures encoded into RTF
  7. 1y agor2rtfFootnote handling fixed for R 4.5.0
  8. 1y agor2rtfUnicode converter rebuilt and mapping table made inspectable
  9. 2y agor2rtfUTF-8 conversion fix and LibreOffice 7.6 support
  10. 10y agotextreuseMinhashes split out from hashes in document objects

Frequently asked questions

What is the difference between r2rtf and textreuse?

They serve adjacent needs but don't currently overlap on shipped themes. textreuse is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is r2rtf better than textreuse?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. textreuse is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to r2rtf?

Top r2rtf alternatives in Analytics are ranked by recent ship velocity. Browse the "r2rtf alternatives" section above for the current picks, or visit /alternatives/r2rtf for the full list with editorial commentary on each.

What are the best alternatives to textreuse?

Top textreuse alternatives in Analytics are ranked by recent ship velocity. Browse the "textreuse alternatives" section above for the current picks, or visit /alternatives/textreuse for the full list with editorial commentary on each.