fix: add charset=utf-8 to VTT content-type to prevent ♪ encoding issues
Without charset specification, browsers/tools interpret text/vtt as Latin-1, causing UTF-8 multi-byte characters like ♪ (U+266A) to render as garbled text (♪). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
084c37d1a7
commit
8356dbdbfe
1 changed files with 1 additions and 1 deletions
|
|
@ -133,7 +133,7 @@ async def upload_file_to_gcs(file: UploadFile, destination_path: str) -> str:
|
|||
return await gcs_service.upload_file_to_gcs(file, destination_path)
|
||||
|
||||
async def upload_vtt_to_gcs(content: str, destination_path: str) -> str:
|
||||
return await gcs_service.upload_text_to_gcs(content, destination_path, "text/vtt")
|
||||
return await gcs_service.upload_text_to_gcs(content, destination_path, "text/vtt; charset=utf-8")
|
||||
|
||||
async def upload_json_to_gcs(content: str, destination_path: str) -> str:
|
||||
return await gcs_service.upload_text_to_gcs(content, destination_path, "application/json")
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue