fix: export generated preview and translate studio UI#70
Conversation
|
Heads-up: PR #55 is also open against the same single-frame export path. Both PRs touch This PR also carries the remaining Studio English UI translation work, while #55 includes the duration/export-timing fix. You and @walliai666 might want to compare approaches so effort doesn't get split unnecessarily — we'll sort out which shape lands from the maintainer side. |
|
Good fixes! Simplifying the regex to remove the 、 (ideographic comma) from the narration cleanup is more robust for international content. Translating Chinese UI messages to English improves accessibility. The retry message change is clearer. |
Summary
Fixes Studio single-frame MP4 export so it renders the generated/edited project preview HTML instead of
falling back to the selected template example.
Also translates remaining hard-coded Chinese strings in the Studio English flow.
Changes
project.lastPreviewHtmlPathfor single-frame exports when a generated preview exists.coded UI text to English.
Why
Before this change, a single-frame project could generate a custom preview, but Export MP4 rendered the
selected template source instead. For example, a generated lower-third using the Vignelli template exported
the Vignelli example rather than the generated lower-third HTML.
Verification
Passed:
./node_modules/.bin/tsc -p packages/core/tsconfig.json --noEmit./node_modules/.bin/tsc -p packages/cli/tsconfig.json --noEmitnode --test packages/cli/test/parse-format-reply.test.tstemplate source.
Notes:
pnpm typecheckandpnpm lintboth failed locally withfetch failedfrom the pnpm wrapper beforeproducing package diagnostics.
keeps the change focused.