<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace">I'm not going to bore you with all the stuff I've done since<br></div><div class="gmail_default" style="font-family:courier new,monospace">
November here. I put it, and some examples, in the file<br></div><div class="gmail_default" style="font-family:courier new,monospace">update1.txt in the git archive. To read it, <br><br></div><div class="gmail_default" style="font-family:courier new,monospace">
do a git clone of <a href="https://github.com/WyoMurf/SaySentence.git" target="_blank">https://github.com/WyoMurf/SaySentence.git</a><br><br></div><div class="gmail_default" style="font-family:courier new,monospace">I a nutshell, I've upgraded the SayScript grammar to handle<br>
</div><div class="gmail_default" style="font-family:courier new,monospace">expressions in the file names, upgraded the current en, fr,<br></div><div class="gmail_default" style="font-family:courier new,monospace">it, hu, and some others, to use the same approach as say.conf. <br>
Upgraded the test suite. Finished converting Asterisk trunk <br>(mostly) to use SaySentence internally. <br><br></div><div class="gmail_default" style="font-family:courier new,monospace">I'll make the Asterisk Community an offer. Somebody out there,<br>
</div><div class="gmail_default" style="font-family:courier new,monospace">I hope, would like to have Asterisk in his/her language, which<br></div><div class="gmail_default" style="font-family:courier new,monospace">is not yet coded into Asterisk. I offer to help you, whoever you<br>
</div><div class="gmail_default" style="font-family:courier new,monospace">are, to develop a soundpack for your language. Here's the steps:<br><br></div><div class="gmail_default" style="font-family:courier new,monospace">
1. Get the en.template file in my github project. Copy it to the<br></div><div class="gmail_default" style="font-family:courier new,monospace"> translation/<your lang_locale> example: rw_RW<br></div><div class="gmail_default" style="font-family:courier new,monospace">
2. Get the scripts that go with the trunk version for the sound files.<br></div><div class="gmail_default" style="font-family:courier new,monospace"> (That's easy, just download any english core sound file set for<br>
Asterisk. It's in there, with the ending of ".txt".)<br></div><div class="gmail_default" style="font-family:courier new,monospace">3. Translate the scripts for the various files. These are really<br></div>
<div class="gmail_default" style="font-family:courier new,monospace"> a mixture of full sentences, and phrases (parts of a sentence).<br></div><div class="gmail_default" style="font-family:courier new,monospace">4. Now, go to the translation file, with your scripts. Look for<br>
</div><div class="gmail_default" style="font-family:courier new,monospace"> the non-trivial sentences, which usually involve stuff like <br></div><div class="gmail_default" style="font-family:courier new,monospace"> '%' variable references, and more than one sound file. See if<br>
</div><div class="gmail_default" style="font-family:courier new,monospace"> the sentence parts fit together acceptably. If not, rearrange<br></div><div class="gmail_default" style="font-family:courier new,monospace"> under the [format] header for that utterance. Plan new files<br>
</div><div class="gmail_default" style="font-family:courier new,monospace"> with corresponding sentence parts if necessary.<br></div><div class="gmail_default" style="font-family:courier new,monospace">5. Now, Plan out the way your numbers, ordinal and cardinal, are<br>
</div><div class="gmail_default" style="font-family:courier new,monospace"> spoken, and how the money for your locale is spoken. I will help<br></div><div class="gmail_default" style="font-family:courier new,monospace">
you (for free) to generate a set of SayScripts for your language.<br></div><div class="gmail_default" style="font-family:courier new,monospace"> We'll have to deal with issues like gender, or who-knows-what-else!<br>
</div><div class="gmail_default" style="font-family:courier new,monospace">6. Run a bunch of tests to make sure the numbers, etc are generated<br></div><div class="gmail_default" style="font-family:courier new,monospace">
properly.<br></div><div class="gmail_default" style="font-family:courier new,monospace">7. Find a friend with a nice voice, and hand them the 400+ file<br></div><div class="gmail_default" style="font-family:courier new,monospace">
scripts. If you can't find one, or can't afford one, find a quiet<br></div><div class="gmail_default" style="font-family:courier new,monospace"> room, and record them yourself, as best you can. Edit the recording<br>
</div><div class="gmail_default" style="font-family:courier new,monospace"> into separate files. Clean them the best you can. Get them in the<br></div><div class="gmail_default" style="font-family:courier new,monospace">
best, highest quality format you can. 44+ kiloherz wav pcm files<br></div><div class="gmail_default" style="font-family:courier new,monospace"> if possible. I'll get them into a good format; Asterisk trunk<br></div>
<div class="gmail_default" style="font-family:courier new,monospace"> can handle sln32 or higher file formats. My intention is that<br></div><div class="gmail_default" style="font-family:courier new,monospace"> the sound files in soundpacks will be a single best choice format.<br>
</div><div class="gmail_default" style="font-family:courier new,monospace"> When installing sound packs, the files can be converted into any<br></div><div class="gmail_default" style="font-family:courier new,monospace">
combination of formats you wish. We can use Asterisk itself to <br></div><div class="gmail_default" style="font-family:courier new,monospace"> convert the files, or sox. All I know is that the higher quality<br></div>
<div class="gmail_default" style="font-family:courier new,monospace"> the source sounds are, the better off you'll be converting them.<br></div><div class="gmail_default" style="font-family:courier new,monospace">8. We'll form your sound files, scripts, and SayScripts into a single<br>
</div><div class="gmail_default" style="font-family:courier new,monospace"> Sound Pack. Possibly the first one ever. I'll have to get busy<br></div><div class="gmail_default" style="font-family:courier new,monospace">
and write some scripts to build sound-packs, and some scripts to<br></div><div class="gmail_default" style="font-family:courier new,monospace"> install them.<br><br></div><div class="gmail_default" style="font-family:courier new,monospace">
I'd like to help with at least one new language, if possible, to see<br></div><div class="gmail_default" style="font-family:courier new,monospace">what can be done to smooth the process.<br></div><div class="gmail_default" style="font-family:courier new,monospace">
<br></div><div class="gmail_default" style="font-family:courier new,monospace">Interested? Write me!<br>
</div><div class="gmail_default" style="font-family:courier new,monospace"><br>
</div><div class="gmail_default" style="font-family:courier new,monospace">murf<br><br></div>-- <br><div dir="ltr"><br>Steve Murphy<br>ParseTree Corporation<br>57 Lane 17<br>Cody, WY 82414<br>✉ murf at parsetree dot com<br>
☎ <a href="tel:307-899-5535" value="+13078995535" target="_blank">307-899-5535</a><br>
<br><br></div>
</div>