Releases: bbottema/rtf-to-html
Release list
v2.0.2
Outlook plain-text RTF rendering
- Avoid wrapping Outlook
\fromtextconversion output in<pre style="white-space:pre-wrap">; use<div style="white-space:pre-wrap">instead so line breaks are preserved without browser-default monospace font and margins. - Added regression coverage for the Simple Java Mail rendering report.
v2.0.1
rtf-to-html 2.0.1 fixes JPMS compatibility for the 2.0 line.
The jar now publishes the valid automatic module name org.bbottema.rtftohtml instead of the hyphenated artifact name, allowing module-info.java consumers to place it on the module path (#15).
The RTF parser and converter APIs introduced in 2.0.0 are otherwise unchanged.
v2.0.0
rtf-to-html 2.0.0 is a breaking overhaul that turns the project into a general-purpose RTF parser and HTML renderer with an Outlook/Exchange extension.
- Replaced the old RTF2HTMLConverter surface with RtfToHtmlConverter, StandardRtfToHtmlConverter, and OutlookRtfToHtmlConverter.
- Added a public parser and document model for groups, control words, control symbols, text, escaped bytes, binary payloads, and source offsets.
- Added standards-oriented rendering, Outlook encapsulated-RTF handling, image extraction, charset and Unicode fallback, and byte-input support.
- Moved the classic regex and JEditorPane converters to the legacy package.
- Resolved long-standing conversion gaps including formatting, images, generators, newlines, and Outlook line controls (#2, #3, #4, #5, #6, #7).
Callers must migrate from the removed 1.x converter API to the new converter types. See #16 and the repository architecture guide.
v1.1.1
rtf-to-html 1.1.1 fixes duplicated numbering in converted lists.
Legacy hard-coded bullet/list numbering is removed when HTML list structure already supplies numbering, preventing doubled markers in modern viewers (#14). The 1.x converter API is unchanged.
v1.1.0
rtf-to-html 1.1.0 substantially improves multilingual RTF decoding.
- Mixed-charsets are decoded using the active font and document font table (#9, #10).
- RTF code-page and font information now drive charset selection, with additional handling for Russian, Hebrew, Japanese, Arabic, and symbol fonts (#12, #13).
The existing 1.x converter API remains available.