Improvements:
-
Docker timezone support for localized log timestamps: The Docker image now installs
tzdata, allowing the full IANA timezone database to be used inside the container instead of being limited to UTC. AddedTZconfiguration guidance to.env.exampleplus both compose files, and updateddocker-entrypoint.shto apply/etc/localtimeand/etc/timezoneautomatically whenTZpoints to a valid zoneinfo entry. -
Backward-compatible timezone-aware logger: Application log timestamps are no longer hard-coded to UTC when
TZis configured. The logger now preserves the existingtoISOString()UTC output whenTZis unset or invalid, but switches to local ISO-8601 timestamps with an explicit UTC offset when a valid timezone is provided. Added regression coverage for UTC fallback, valid named zones, and non-hour offsets such asAsia/Kathmandu.
Bug Fixes:
-
Fixed blackhole theme on Sub Toolbox pages, duplicate-looking theme toggle states, and theme persistence drift across pages: The app had split third-theme identifiers (
blackholeon config surfaces vstrue-darkon most toolbox/tool pages), so selecting the third theme on the config page could make toolbox pages fall back to their default styling and make the toggle look like it had "light" twice. Theme handling is now unified so manual theme choices persist across the config page, Sub Toolbox, individual tool pages, SMDB, translation history, and the subtitle selection page, while each page still maps the shared saved preference to the theme token its CSS expects. Added legacy compatibility for older savedtrue-darkvalues, removed the last page-local toggle implementation that could drift from the shared logic, and fixed Quick Setup's config-page blackhole styling so its overlay/banner now match the active third theme correctly. Also stopped the shared toggle from writing a theme preference on first load when the user has not explicitly chosen one, so system theme following still works until a real manual selection is made. -
Fixed translation history page stale-load latency and removed broad Redis history scans from the normal stale path: The
/sub-historypage already had a fast-path aggregated store key, but once that cache aged past 15 seconds it fell back to scanning history entry keys and re-reading them one by one. On larger Redis datasets this still made stale page loads feel heavier than they should. Added a per-user Redis sorted-set history index (histidx__{userHash}) that is updated alongside each history entry write. History reads now use this bounded recent-entry index when the store key is stale, and only fall back to the legacy SCAN-based recovery path if no index exists yet. This keeps normal history-page work to a small, fixed set of recent entries instead of walking the broader history keyspace. -
Fixed History-page Retranslate not actually starting a new translation or creating a visible new history card: The old
/api/retranslateroute only purged cache and returned a translation URL, but the history page never navigated to that URL, so clickingRetranslateoften did nothing user-visible and did not create a fresh history entry. The route now validates concurrency correctly, purges stale cache if present, creates a brand newprocessinghistory entry immediately, and then starts a fresh background translation using the same history request ID so the entry is later updated tocompletedorfailedinstead of disappearing. The History page button now sends the card metadata the backend needs, reloads the page after a successful start so the new card appears right away, and all retranslate copy/tooltips/messages were updated to describe the real behavior (Start a fresh translation) instead of the confusing oldCache clearedwording. Also fixed an async safety bug where cache-reset/retranslate concurrency checks calledcanUserStartTranslation()withoutawait, weakening those guards. -
Fixed backend/default workflow mismatch so XML Tags is now the true default everywhere: The frontend already defaulted to
translationWorkflow: 'xml', but backend config loading still defaulted to'original', and theTranslationEngineconstructor also fell back to'original'when the workflow was missing or invalid. This created an inconsistent default depending on whether a request used saved config, normalized config, or direct engine construction. Updated bothgetDefaultConfig()andnormalizeConfig()insrc/utils/config.js, plus the engine-level fallback insrc/services/translationEngine.js, so XML Tags is now the consistent default across addon translations, file upload defaults, and engine initialization. -
Fixed ASS/SSA + "Send Timestamps to AI" dropping AI-adjusted timings during ASS reassembly: The ASS-aware translation path previously rebuilt every
Dialogue:line with the original ASS start/end times, even when theaiworkflow returned corrected SRT timecodes.reassembleASS()now parses translated SRT timeranges and writes the translated start/end times back into the ASSStartandEndfields while preserving original spacing and document structure. This restores the intended timing behavior of theaiworkflow for ASS/SSA passthrough translations instead of silently degrading it to text-only reassembly. -
Fixed ASS/SSA helper position mapping around
\N,\n, and\h, and preserved drawing-mode payloads correctly: The original helper recorded tag positions before normalizing ASS escape sequences, which could shift tags after translation when earlier line breaks or hard spaces were present. It also treated drawing-mode (\p) vector payloads as ordinary translatable text. ReworkedassTranslationHelper.jsso it extracts normalized clean text and a unified list of preserved raw ASS segments, including override tags and drawing payloads, using positions based on the normalized text stream. Re-insertion now maps those preserved segments proportionally back into the translated line, keeping drawing commands intact and out of the translation request while avoiding post-\Ntag drift. -
Fixed weak ASS/SSA detection in the make-translation route: The addon translation path used an inline case-sensitive content check for
[Script Info]plus[V4+ Styles]/[V4 Styles], which missed valid lowercase or variant ASS/SSA payloads. Replaced that check with the shareddetectASSFormat()utility fromsrc/utils/subtitle.js, so the ASS-aware wrapper path now reliably activates for both ASS and SSA inputs that the rest of the codebase already recognizes. -
Fixed stale ASS/SSA passthrough semantics and workflow copy on the main config surface: The old config page still rendered the checkbox as "Convert ASS/SSA to VTT" with the box checked by default, even though the JS logic already treated checked as passthrough. Updated
public/partials/main.htmlso the control is rendered asASS/SSA Passthrough, unchecked by default, matching the stored config semantics (convertAssToVtt: truemeans conversion enabled;falsemeans passthrough). Also updated the main-page description, the URL-extension helper text, and locale workflow copy so they no longer claim translations always auto-convert, and so workflow labels/tooltips consistently describe XML Tags as the default, Original Timestamps as legacy, and JSON as a supported workflow option.