Previously the on-device Web Speech API (Chrome/Edge/Safari) was always preferred, and the configured external transcription endpoint was only used as a fallback when the browser had no speech API at all (Firefox). Flip the priority in Composer.tsx: if a transcription endpoint is configured in Settings, use it for dictation regardless of browser support, since it's generally far more accurate. Fall back to the browser's on-device SpeechRecognition only when no endpoint is set. Update the Settings hint text and README to describe the new behavior. Rebuilt and redeployed to the repo root.
23 lines
913 B
HTML
23 lines
913 B
HTML
<!doctype html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="UTF-8" />
|
|
<link rel="icon" type="image/svg+xml" href="/favicon.svg" />
|
|
<link rel="apple-touch-icon" href="/icons/apple-touch-icon.png" />
|
|
<meta
|
|
name="viewport"
|
|
content="width=device-width, initial-scale=1.0, viewport-fit=cover, maximum-scale=1.0, user-scalable=no"
|
|
/>
|
|
<meta name="theme-color" content="#000810" />
|
|
<meta name="apple-mobile-web-app-capable" content="yes" />
|
|
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
|
|
<meta name="apple-mobile-web-app-title" content="Hermes" />
|
|
<title>Hermes</title>
|
|
<script type="module" crossorigin src="/assets/index-SBr79e_P.js"></script>
|
|
<link rel="stylesheet" crossorigin href="/assets/index-CWSassUi.css">
|
|
<link rel="manifest" href="/manifest.webmanifest"></head>
|
|
<body>
|
|
<div id="root"></div>
|
|
</body>
|
|
</html>
|