
"RandyL"
Usenet Poster
rlink@cableone.net
Posted on:
Nov 12, 2007, 4:35 PM
Post #2 of 4
(34 views)
Shortcut
|
Hi Martin, I am certainly no expert, and this is just a guess, but it may be spelled this way because some 3rd-party ATC utilities (like AI Smooth, EditVoicePack, etc.) take this atc_type definition, reads it, and uses a voice synthisizer to "read back" what it thinks the aircraft type is. By spelling the atc type in certain ways, whatever program is reading it may do a better job of pronouncing the name correctly phonetically than if the name is simply spelled "...Boeing." I know that when I was fooling around with voice synthesis on the the Commodore Amiga and the PC, I would sometimes have to spell a word a certain way or capitalize certain letters in order for the computer to pronounce that word correctly. Or, I could be completely wrong, it has been known to happen. Take care... Randy L. -- Remember: Any landing that you can walk away from, is a landing that you can be fined, sued, or prosecuted for. "Martin S." <ms@ms> wrote in message news:k33hj3dcpd6han92n27u6oaprjgidk81i7@4ax.com... >I seem to have stumped the readers of the AVSIM forums with this. > Sometimes (often ??) you folk here do much better! The question came > up because of 'missing' entries in EditVoicePack. This is the crux of > my post..................... > > Why do many entries for atc_type in the aircraft.cfg file mix bold and > small case letters? I've noticed this, for years in fact, but never > really understood why this is done, or bothered to ask. For instance: > > atc_type=BOeiNg > > I am sure that there must be some good reason for the upper and lower > case combinations. Nearly all my aircraft.cfg files show variations > like this (BoEinG -- BOEinG etc.). Moreover, if you buy and install > FSHotSFX (wouldn't fly without it!), the programme makes entries to > the aircraft.cfg files, like this: > > OldName=BOEING > NewName=BOeINg > > FSHotSFX can't be doing that for nothing... Maybe there needs to be a > unique atc_type entry for each a/c model installed (if so, why?), but > I didn't know entries in what is basically a text file could be case > sensitive. > > Hope someone can explain exactly (or even approximately) what the > issue is here. > > Thanks, > > Martin > > (SORRY IF THIS THREAD COMES UP MORE THAN ONCE - HAVING SOME PROBLEMS > POSTING)
|