Thanks Waruddar for keeping up with the bugs. Hopefully Pacific will have some time this week to look at them too

(because I know I won't)
On Tes4Edit/View/Trans - The issue is a matter of versions (at least, hopefully it's that easy). Old versions were distributed as "Tes4View.exe" and could use a flag to switch to Edit or Trans. The most recent version (2.5.3) changed this - it was distributed as Tes4Edit and you had to make a separate file for each of Tes4View/Trans to get those running (and I'm 99% sure I tested "Tes4View -Trans" and got View). I tried to handle for both cases, but never made a full check for the files because it would also require testing the version. Making copies would be much easier, though, and would only take up a small amount of room (if anyone is complaining about 14 MBs to manage a 4 gig game with mods that easily surpass 500 MBs...) so that seems the best method.
Err... no, they shouldn't. The ini wasn't the source of the error, and people can leave it as is.
"Tes4View.exe -translate" works, as does "Tes4View.exe -edit". Made sure of that before my last post

Perhaps Bash shouldn't bother at all with the command line switches, and treat Tes4View / Edit / Trans as completely separate applications (just like the rest of the launchers). If the user wants Tes4Trans, they make the copy themselves and (if needed) change a path variable in bash.ini. This would simplify the code, and require adding "sTes4ViewPath" and "sTes4TransPath" to bash.ini. This is probably the best way to go...
Speaking of the ini, I'm going to go through and double-check all of the variable names. Most of the launcher bugs that I fixed were variable mismatches between the code and ini file (code looked for sTES4EditPath, variable was sTes4EditPath, or the code looked for sSomething, and the variable was sSomethingPath, etc). Case sensitivity can be painful at times. I've been choosing to change the code rather than the ini so that people don't have to go make new ini files if they already have a custom one. Unfortunately, this means that the variable names aren't all consistent. Some end with Path, others don't, etc.
Just to be clear, there won't be any reason to recreate the ini file with the next release. People that used the work-around I posted that deleted/commented part of the ini might want to add that section back though.