[Black Wolf]

Would this be even vaguely conceivable? I'm thinking about the wavy red lines you get in Word and Firefox and such things when you type in an unrecognized word. I know that you can always copy your briefings, debriefings and messages into OpenOffice or something and check them. Then copy them back, but adding the functionality directly to FRED would make it much harder to forget that particular step. It would be far from perfect, of course, but it might help eliminate some of the more easily missed little errors and typoes that can be so immersion breaking when you notice them ingame.

Of course, I want to reiterate that this is purely a thought bubble. I have no idea how it might be implemented, or whether it would be viable or not. Just putting it out there.

[Trivial Psychic]

This would simplify matters. 

[chief1983]

Mention it to z, there are open source spellcheckers out there that could probably do the trick and be integrated into wxFRED.

[Dragon]

That would be nice indeed. It'd need a customizable dictionary (so it can spellcheck words such as "Vasudan" or "jumpdrive"), but I think this would really come in handy for everyone.

[Goober5000]

Pah.  All y'all need to learn to spell.

Alternatively, you can use the Voice Acting Manager to export all your text to a file and then run a spellchecker on that.

[mjn.mixael]

Pah.  All y'all need to learn to spell.

Alternatively, you can use the Voice Acting Manager to export all your text to a file and then run a spellchecker on that.

I'm not convinced you read the first post....

[Kopachris]

Mention it to z, there are open source spellcheckers out there that could probably do the trick and be integrated into wxFRED.

Thinking GNU aspell?  I think the GPL is incompatible with FS2_Open, but what about LGPL?

[Goober5000]

I'm not convinced you read the first post....

I just skimmed it.

[SypheDMar]

Mention it to z, there are open source spellcheckers out there that could probably do the trick and be integrated into wxFRED.

Thinking GNU aspell?  I think the GPL is incompatible with FS2_Open, but what about LGPL?

Does incompatible with FS2_Open mean it's incompatible with wxFRED? If not, all we have to do is release wxFRED under GPL too, right?

I don't oppose the implementation if it speeds up development. If someone decides to try and implement this, there should be tests to ensure that the spell-checker does not act as a bottleneck in any circumstances. As a non-coder, I don't really know if a spell checker can even do that, so it might not even be a concern. If it does nothing to a mission file in, say, BP2, then I'm all for it.

[Admiral Nelson]

I just spell check missions using Notepad++.  I just add all the Freespace "words" to the custom dictionary, and after a few missions are run through it only picks up misspellings in messages, briefings, etc...  There is no need to copy and paste at all.

[MatthTheGeek]

Does incompatible with FS2_Open mean it's incompatible with wxFRED? If not, all we have to do is release wxFRED under GPL too, right?

wxFRED, much like FRED2, has to use FS code.

[karajorma]

Well the question is whether we can stick a different licence on the wxFRED bit from everything else.

A spell checker wouldn't actually have to interact with any of the code at all. It would have already finished it's work before any of the volition data structures were touched.

[z64555]

wxFRED currently does not have anything of 's creation, aside from the general layout of the windows and dialogs, and button graphics for the main editing window.

This will likely change once the drawing canvas gets implemented and hooks into the graphics rendering code, and maybe also once the mission import/export functions get put in.

Other than those bits, I have no clue as to what can/can't be done regarding licensing.