datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
Comparison · Analytics
parzer vs textshaping
A side-by-side editorial comparison of parzer and textshaping — release velocity, themes, recent moves, and the top alternatives to consider.
parzer vs textshaping: at a glance
What is parzer?
A coordinate parser whose entire job is surviving how badly humans write latitude and longitude.
parzer converts messy coordinate strings — degrees, minutes, seconds, assorted symbols, arbitrary whitespace — into decimal degrees. Development is slow and sporadic, with three-year gaps between releases, and the work splits between C++ performance in the internal scrub() path and a long tail of parsing bugs. The most recent release, 0.4.4, fixed two genuinely dangerous ones: a leading space could silently drop a negative sign, and an E in a longitude string returned NA while a W parsed fine.
What is textshaping?
Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.
textshaping is the text layout layer beneath R's modern graphics stack, feeding ragg, ggplot2 and marquee. Version 1.0.0 rewrote the shaping engine to honour the global direction of text, adding a direction argument that defaults to automatic detection, align settings that resolve against that direction, and ICU-based soft break locations that handle ideographic scripts properly. The five releases since have been consecutive bug fixes against that rewrite — bidi embedding arrangement, line positioning with mixed sizes, a weak hash in the shape cache, a signed integer overflow, and font fallback regressions.
parzer vs textshaping: editorial side-by-side
parzer
0.0ANALYTICS
A coordinate parser whose entire job is surviving how badly humans write latitude and longitude.
◆ Current state
parzer converts messy coordinate strings — degrees, minutes, seconds, assorted symbols, arbitrary whitespace — into decimal degrees. Development is slow and sporadic, with three-year gaps between releases, and the work splits between C++ performance in the internal scrub() path and a long tail of parsing bugs. The most recent release, 0.4.4, fixed two genuinely dangerous ones: a leading space could silently drop a negative sign, and an E in a longitude string returned NA while a W parsed fine.
◆ Where it's heading
The package has settled its scope — 0.4.1 explicitly rewrote the documentation to say it parses coordinates rather than validates them — and now moves only when someone finds a string it mishandles. Recent work has also been about shedding weight: Rcpp dependence reduced, the C++ requirement dropped from DESCRIPTION, suggested dependencies removed, and the vignette builder moved to Quarto. Maintainership passed to a new maintainer in 2022 and the package has stayed within rOpenSci.
◆ Prediction
The next release will most likely be another batch of parsing edge cases reported by users, since that is what every release since 0.2.0 has been. Nothing in these entries points to new functionality.
textshaping
0.0ANALYTICS
Rewrote its shaping engine for bidirectional text, then spent a year fixing what that broke.
◆ Current state
textshaping is the text layout layer beneath R's modern graphics stack, feeding ragg, ggplot2 and marquee. Version 1.0.0 rewrote the shaping engine to honour the global direction of text, adding a direction argument that defaults to automatic detection, align settings that resolve against that direction, and ICU-based soft break locations that handle ideographic scripts properly. The five releases since have been consecutive bug fixes against that rewrite — bidi embedding arrangement, line positioning with mixed sizes, a weak hash in the shape cache, a signed integer overflow, and font fallback regressions.
◆ Where it's heading
The package has moved from Latin-first layout to script-agnostic layout in two rewrites, 0.4.0 and 1.0.0, and is now in the long correctness tail that follows. The bug reports arriving from ggplot2, ragg and marquee issue numbers show how it works in practice: textshaping bugs surface as rendering defects in the packages above it, which is why so many fixes here cite another package's issue tracker.
◆ Prediction
Expect continued fixes driven by downstream rendering reports rather than new layout features, as the 1.0.x series stabilises. The font fallback path has produced two of the recent bugs and is the most likely source of the next.
Alternatives to parzer and textshaping
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 parzer or textshaping.
maplegend
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
lang
R help pages translated on demand by whichever LLM you point it at.
mapsf
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
fabletools
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all parzer alternatives → · See all textshaping alternatives →
Recent activity from parzer and textshaping
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agotextshapingFixes reverting between font fallbacks
- 9mo agotextshapingGuards against freetype version mismatches with systemfonts
- 11mo agotextshapingFixes a signed integer overflow in the previous fix
- 11mo agotextshapingFixes bidi single-line shaping and a weak shape-cache hash
- 1y agoparzerFixes dropped negative signs and mis-parsed E longitudes
- 1y agotextshapingFixes hard line breaks across multiple embeddings
- 1y agotextshapingShaping engine rewritten to honour global text direction ⚡
- 4y agoparzerScope clarified: parsing, not coordinate validation
- 5y agoparzerFaster scrub(); works around non-UTF8 locales on Windows
- 5y agoparzerFixes factor conversion in parse_llstr() on older R
- 5y agoparzerparse_llstr() parses latitude and longitude from one string
- 6y agoparzerMore degree symbols recognised; NA handling fixed in C++
Frequently asked questions
What is the difference between parzer and textshaping?
They serve adjacent needs but don't currently overlap on shipped themes. parzer and textshaping 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 parzer better than textshaping?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. parzer and textshaping 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 parzer?
Top parzer alternatives in Analytics are ranked by recent ship velocity. Browse the "parzer alternatives" section above for the current picks, or visit /alternatives/parzer for the full list with editorial commentary on each.
What are the best alternatives to textshaping?
Top textshaping alternatives in Analytics are ranked by recent ship velocity. Browse the "textshaping alternatives" section above for the current picks, or visit /alternatives/textshaping for the full list with editorial commentary on each.