Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] Language not detected correctly in meeting transcript and cannot be changed

Open
  • Is something wrong?
#1,033 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@ParamKataria is already working on this.

Since Oct 11, 2026.

  • #1103 by @ParamKataria — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
macos, swift
Domain
desktop

Research direction

Start by reading the meeting recording and transcription flow, then look for where the transcription language is chosen or detected. Reproduce with a German meeting and check whether the transcript can be redone in a selected language. Done means users can choose a language before transcription or redo an existing transcript in that language.

Written by the indexing model from the issue text.

Description

bug keep-open
Describe the bug

The meeting was in German, voice engine "blazing fast" (I guess). Transcription was done based on English language but the meeting was actually in German. There is now way to redo the transcript in another language.
Also downloading the audio is a mess. 140 single files.

Reproduction steps
  1. open fluidvoice
  2. start automatic meeting recording
  3. wait for transcript
  4. its ein english...
Expected behavior

Redo the transcript in a chosen language. Or set the language before transcription.

Actual behavior

Transcript was in English, completey wrong

App Version

1.6.10 beta.7

macOS Version

26.6.2

Architecture

Apple Silicon

Logs or crash report
Screenshots or screen recording

No response

Dominant language
Swift
Stars
11.9k
Forks
863
Avg merge
1d 13h
Merged PRs (30d)
27

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from altic-dev/FluidVoice

All issues in altic-dev/FluidVoice

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.