Skip to content

webui: fix two strings that rendered wrong - #413

Closed
CryptVenture wants to merge 1 commit into
0xShug0:mainfrom
CryptVenture:pr/webui-string-fixes
Closed

webui: fix two strings that rendered wrong#413
CryptVenture wants to merge 1 commit into
0xShug0:mainfrom
CryptVenture:pr/webui-string-fixes

Conversation

@CryptVenture

Copy link
Copy Markdown
Contributor

Split out of #373 as requested. Two string fixes, nothing else; the package resolver, the catalog entries, the request wiring and the transcript display are separate PRs.

The changes

Hero subtitle rendered its lookup key. The workflow tabs are keyed conversion and separation, while studio.subtitle.* was defined only for vc and sep. The Voice conversion and Source separation tabs printed studio.subtitle.conversion and studio.subtitle.separation verbatim where their description should be. Adds the two missing keys.

Double-encoded ellipsis in the models-folder status line. folder… is what a UTF-8 ellipsis looks like after being decoded as Latin-1. Replaced with the character itself.

Validation

npx svelte-check --tsconfig ./tsconfig.json
# 153 FILES 0 ERRORS 0 WARNINGS

Scope

Two English strings in i18n.ts, one status line in +page.svelte. No behaviour change. The generated bundle is deliberately excluded — it is not byte-reproducible, so regenerating it in each PR of this split would make the PRs conflict; happy to send one bundle-regeneration PR once the series lands.

  - The Voice conversion and Source separation tabs are keyed 'conversion' and
    'separation', while the subtitle lookups were only defined for 'vc' and
    'sep'. Both hero subtitles rendered their raw lookup key. Adds the two
    missing keys with the same text the other tabs use.
  - The models-folder status line carried a double-encoded ellipsis
    ("folder…"), which is what a UTF-8 ellipsis looks like after being
    decoded as Latin-1. Replaced with the character itself.

Validation:
  npx svelte-check --tsconfig ./tsconfig.json     # 153 files, 0 errors
@CryptVenture

Copy link
Copy Markdown
Contributor Author

Closing for now to stay inside the 3-concurrent-PR policy (see the discussion on #422). Nothing is wrong with the change and CI is green on it; I will reopen it as review slots free.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant