Bug 428863

Summary: The letter sounds should be the phonemes, not the letter names
Product: [Applications] gcompris Reporter: Robert Pollak <robert.pollak>
Component: generalAssignee: Bruno Coudoin <bruno.coudoin>
Status: REPORTED ---    
Severity: wishlist CC: animtim, fios, fuxfwgc4a2i1gr
Priority: VLO    
Version First Reported In: 0.80   
Target Milestone: ---   
Platform: Mint (Ubuntu based)   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Robert Pollak 2020-11-08 21:51:11 UTC
SUMMARY
I am using GCompris 0.81 on Linux Mint 19.3, with German localization.

In the activities about clicking on letters, the used sounds unfortunately contain the "letter names".
For learning to read, the *phonemes* of the letters should be played instead,
e.g. [m] instead of [em], [k] instead of [ka], ...

ADDITIONAL INFORMATION
I already filed this in 2009 as https://bugzilla.gnome.org/show_bug.cgi?id=576781 .
A similar issue is https://bugs.kde.org/show_bug.cgi?id=262015 .
Comment 1 animtim 2020-11-09 18:27:20 UTC
Hi,

This is technically not a bug, this activity (as currently all our activities to learn letters) are meant by design to learn letters name, not their pronunciation.

For learning phonemes, we would need to create a specific different activity.
Though this is quite tricky for several reasons:
-in most languages, the same letter can have different pronunciation, so it would need some kind of combination of letters to give context.
-even with combination of letters, some languages (even in English) have lots of exceptions so it may not work.
-recording sets of all possible combinations for all possible cases for all supported languages is a lot of work, and would make the voices sets as much heavier.
-making such activity to work good in an international way is surely not an easy task (it is actually already hard with just letters for some languages, I can't imagine how messy it could be if we try to cover phonemes too).
Comment 2 Alexey 2023-05-03 19:13:00 UTC
*** Bug 446848 has been marked as a duplicate of this bug. ***