GNOME Bugzilla – Bug 576781
The letter sounds should be the phonemes, not the letter names
Last modified: 2020-11-08 21:53:26 UTC
Please describe the problem: I am using GCompris V8.4.4 on Ubuntu 8.04, with german localization. In the activity "click_on_letter", the wav files from /usr/share/gcompris/boards/voices/de/alphabet/ are used to let the child hear a letter. Unfortunately, these sound files 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], ... I could provide the necessary replacement wav files, if you are interested. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
I agree. It may be handled differently in some countries but in my experience at a basic level of reading/writing, many schools use the phonetic values of letters, not the names, with the names getting introduced much later. Perhaps it could be made an option that is set in the settings, whether to use [em] or [m] type sound files?
Multigraph support (see: https://bugzilla.gnome.org/show_bug.cgi?id=696869) is pretty much done. So, we could even teach 'ch' and 'sch' etc. as single units. I don't know how things are taught in German schools these days though.
I think Robert's bone is more with the recordings than the choice of letters dropping.
Yes, but if he wants to record a new set, this is something to keep in mind. Otherwise, sounds might be missing later.
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. Furthermore, GCompris development has moved to a different platform (from GTK+ to Qt). The last legacy release based on GTK+ was version 15.10 in October 2015. If you can still reproduce this problem in a recent and supported of GCompris, then please feel free to report it at https://bugs.kde.org/buglist.cgi?product=gcompris See https://gcompris.net/ for more information. Thank you for reporting this issue and we are sorry it could not be fixed.
I have now reported this as https://bugs.kde.org/show_bug.cgi?id=428863 .