Outlook descriptions: working fix available — looking for testers and upstream review #949
pengusto
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Outlook/Exchange descriptions can arrive in Fossify Calendar as complete HTML documents. In my calendar, the raw tags obscure the actual event information and prevent me from comfortably using Fossify as my daily calendar.
I have prepared an implementation and an installable, unofficial build. I would appreciate testing from other Outlook users and maintainer feedback on upstream submission.
Context and prepared code
The implementation offers a native formatted description preview with paragraphs and links, readable list/widget/notification summaries, and an explicit HTML source-editing toggle. Editing another field preserves the exact original description, including surrounding whitespace. Plain-text descriptions remain unchanged. No new dependencies or data migration; no WebView or script execution.
Before / after
Matched emulator screenshots of the same synthetic Exchange-style event. Private event content has been replaced; these show the display change, not a completed Outlook server round trip.
Before:
After:
Try the unofficial build
Pengusto Calendar release and APK.
This GPL-3.0 fork installs alongside Fossify Calendar as Pengusto Calendar on Android 8 or newer. Download
Pengusto-Calendar.apkunder Assets. Grant calendar access, enable calendar synchronization in settings, and select your Android calendars. Outlook must already synchronize its events into Android calendar storage. Local-only events and settings do not transfer automatically; export local events to ICS if you need to migrate them.If you test it, please report app/Android version, sync adapter, whether the description is readable, and whether a title-only edit preserves the description when checked in Outlook. Use a disposable test event and redact private details from screenshots. The fork shares access to selected synchronized calendars, so edits can sync back to the source account.
Validation and remaining checks
Build, Android Lint and Detekt passed. 22 Android instrumentation tests passed on Android 15 ARM64, including HTML parsing, exact source preservation on title-only save, explicit source editing, and readable widget text. The published APK signature and checksum were verified; installation, update installation and calendar launch succeeded in the emulator.
Actual Outlook server synchronization and immediate startup/configuration races remain unverified. The original device observation did not record the installed version, device model or exact sync route. Existing date/time fields overlap at 200% font scale; the description preview remained readable.
Questions for maintainers
Is this approach suitable for an upstream contribution? If so, could #12 receive
help wanted, or could you indicate the preferred scope and next step? I have held back upstream submission in accordance with the contribution guidelines. The existing Calendar issue remains the tracking issue; this discussion presents the available implementation and invites community testing.All reactions