Don't run pronounReplacer on undefined or 0.

This MR just puts the logic back to how it was before it was moved to JS. prestigeDesc is checked on the very next line anyway. I'm not sure that this fix is correct, since you added a new comment on this line too that I don't understand.

As it is now, it'll throw errors. If this fix isn't correct, and the logic change on this line was intentional, we'll need a different fix for it. pronounReplacer can't handle 0 as input and pornPrestigeDesc can definitely be 0, so we have to check it.