← Back to home
Comparison · Analytics

r2rtf vs taxizedb

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

r2rtf vs taxizedb: at a glance

Featurer2rtftaxizedb
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-reporting, rtf, internationalization, document-conversiontaxonomy, biodiversity-data, sqlite, ropensci
Last editorial update1h ago4h 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 taxizedb?

Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.

taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.

Read the full taxizedb trajectory →

r2rtf vs taxizedb: 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
taxizedb
ANALYTICS
0.0

Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.

◆ Current state

taxizedb queries taxonomic databases locally rather than through rate-limited web APIs, which is what makes it usable for millions of name lookups. Version 0.2.0 established the current design: every source stored as SQLite, no credentials or ports needed, plus name-to-ID mapping functions and ports of the core taxize verbs. The most recent release changes how those databases arrive — instead of downloading a preprocessed SQLite file from the cloud, db_download_*() now fetches raw data and converts it locally for every source, because the cloud path kept breaking.

◆ Where it's heading

The package is trading convenience for independence. Each release removes another thing that has to be working elsewhere for the package to function: hosted database preparation is gone, and where a provider disappears the package documents it rather than pretending otherwise — db_download_tpl() is now defunct because The Plant List no longer exists, though previously downloaded copies still query fine. Release cadence is slow, with multi-year gaps and a maintainer handover in 2023.

◆ Prediction

Expect further releases to track data sources appearing and disappearing rather than adding features, since that has driven every recent change. Local conversion also shifts cost onto users, so build time and memory for the larger sources are the plausible next thing to need attention.

Alternatives to r2rtf and taxizedb

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 taxizedb.

See all r2rtf alternatives → · See all taxizedb alternatives →

Recent activity from r2rtf and taxizedb

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

  1. 7mo agor2rtfDOCX and HTML output become exported functions
  2. 9mo agotaxizedbDatabases now built locally from raw data, not the cloud
  3. 11mo agor2rtfChinese character support arrives via an i18n font path
  4. 1y agor2rtfText colour fixed for figures encoded into RTF
  5. 1y agor2rtfFootnote handling fixed for R 4.5.0
  6. 1y agor2rtfUnicode converter rebuilt and mapping table made inspectable
  7. 2y agor2rtfUTF-8 conversion fix and LibreOffice 7.6 support
  8. 3y agotaxizedbPatch release for a maintainer change
  9. 5y agotaxizedbtaxa_at() retrieves ancestors at a named rank
  10. 5y agotaxizedbFixes failing tests
  11. 6y agotaxizedbSQLite everywhere, three new sources, taxize verbs ported
  12. 9y agotaxizedbTracks the dplyr split that introduced dbplyr

Frequently asked questions

What is the difference between r2rtf and taxizedb?

They serve adjacent needs but don't currently overlap on shipped themes. r2rtf and taxizedb are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is r2rtf better than taxizedb?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. r2rtf and taxizedb are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 taxizedb?

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