Skip to content

Hiragana and Katakana readings treated as same answer in practice game #26989

Description

@tentoumushii

Summary

In a practice game, the user clicked the hiragana 'しゅ' (shu) and it was marked as correct even though the displayed correct answer was the katakana 'シュ' (shu). This happened twice. The user expects these to be distinct answers since they are different scripts.

Steps To Reproduce

  1. Open the practice game where katakana is the target.
  2. Wait for a prompt where the correct answer is 'シュ'.
  3. Click the hiragana 'しゅ' as the answer.
  4. Observe that it is accepted as correct instead of being marked wrong.

Expected Behavior

Only the katakana 'シュ' should be accepted as the correct answer for a katakana prompt, and the hiragana 'しゅ' should be considered incorrect.

Actual Behavior

The hiragana 'しゅ' was accepted as correct for a katakana prompt, which happened twice.

Environment

  • Page: Unknown
  • Feature: Unknown
  • Device: Unknown
  • Browser: Unknown
  • Locale: Unknown

Attachments

None.

Triage Notes

Likely cause: answer matching is comparing romaji or pronunciation only, not considering script. Need to ensure exact script match for kana-based questions.

Missing Info

  • Which specific practice game or mode was being used (e.g., Hiragana quiz, Katakana quiz, matching game)?
  • What was the exact prompt showing before the answer was selected?

Source

  • Source: Tally
  • Report ID: b6eb0ac9-fbb6-4eee-9169-480410cd210f
  • Tally submission ID: 6DAWqJ5
  • Submitted at: 2026-08-02T21:44:22.000Z

Original User-Entered Fields

How would you rate KanaDojo? (optional)

4

How did you find out about KanaDojo? (optional)

Google

In detail, please describe the bug you encountered (alternatively, provide any other additional feedback here)

I clicked しゅ which is the same as the "correct" anwser of シュ they both mean Sho this happened twice why?

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions