mirror of
https://github.com/rhasspy/espeak-ng.git
synced 2026-11-13 01:07:47 +00:00
John Bowler
bfef012068
The six modified files all had spurious characters introduced apparently as a result of files with the UTF8 BOM marker, U-FFFE, which is conventionally used at the start of text files to indicate a UTF-8 file and is invisible under normal circumstances (e.g. the file is opened as a text file). None of these files are recognized by espeak-ng on Linux systems because the 'language variant' line is seen by espeak-ng as starting with a new character. 'gustave' is an uncorrupted file, it correctly starts with the BOM in UTF-8 (three bytes), however even though it is correct espeak-ng does not read it (this may be a separate bug!) 'marcelo' somehow got the BOM character replaced by a literal '?', notice that 'git diff' on these changes will, indeed, show the removed character in 'gustave' as a literal '?'. Notice also that the character in question, the BOM, is actually the Unicode 'zero width no-break space', so it is pretty invisible. The remaining files seem to have suffered major corruption possible as a result of dostounix style convertions. The line endings, normally <lf> on Unix or <cr><lf> on Windows, had been converted to <cr><lf><lf> and the BOM had been replaced by a <tab> character. Signed-off-by: John Bowler <jbowler@acm.org>
21 lines
338 B
Plaintext
21 lines
338 B
Plaintext
language variant
|
|
name Lee
|
|
gender Male
|
|
|
|
#echo 230 30
|
|
pitch 85 110
|
|
|
|
flutter 0
|
|
formant 0 80 80 80 80
|
|
formant 1 80 80 100 100
|
|
formant 2 80 80 80
|
|
formant 3 9 9 9
|
|
formant 4 290 290
|
|
formant 5 130 0 0
|
|
formant 6 90 90 90
|
|
formant 7 90 90 90
|
|
formant 8 90 90 90
|
|
stressAdd 0 0 0 200 0 0 0 100
|
|
stressAmp 30 30 30 30 30 30 30 30 30
|
|
|