-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is the -k option completely gone? I can't get it to work. I usually use -k1, but nothing special happens now. I am also noticing a very rare bug that I can't reproduce on my own, but I have experienced it twice while reading text. It is another cut-off bug, and it seems to occur when a word is followed by a comma and the next word starts with a. However, I have tried a number of tests to reproduce the bug and I can't. Basically, eSpeak cuts off up to the end of the sentence or the line, whichever comes first, but it has only happened twice. To clarify, I can't make it do it, but wherever it does happen, reading the same line more than once produces the same result every time, so it's not intermitant in that regard. Wow! I just produced it in this mail. It seems that the a isn't the only problem. It cuts off after the word time 2 lines above this one. and resumes at the beginning of the next sentence beginning with "Wow". I just caught it proofreading this message before sending it. eSpeak is still great. I use it almost exclusively now, with my accent as a backup when I am upgrading eSpeak or speech-dispatcher. And the upgrade, with the exception of the minor issues I mentioned, is very good. Thanks much, Lorenzo - -- You will reach the highest possible point in your business or profession. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE2fnBG9IpekrhBfIRAg3TAKCvVc5hJqZJlmW7buZVZOcY6/ExwQCghzDs +RVSWgNHKASNJMXlZ+LnkXs= =n9ee -----END PGP SIGNATURE-----
