FreeGameDev

I've decided to do away with some of my pet peeves in the Options GUI such as "resolution" (younger users may not understand this word), "Graphical Effects Level" (a term which should be replaced with "Graphical Effects Settings" as you can now customize the settings as well) and the config-will-be-taken-from-fire (which should be replaced with "Menu Enter"). Here is the resulting .zip.:



If you can call these bugs I've just reported them here and most except for resolution and Graphical Effects I have not known of before now.

Here are some edits to the help menus fixing things such as grammar (periods, commas, colons and semicolons), speeling, etc..



I think someone mentioned these bugs on the blog at one time.

IMO "graphical effects level" and "resolution" are just good enough and I see no use in breaking all translations but such a minor change.

Regarding the input menu incorrectly to the fire key, thanks, I create a bug report for this. We'll need to see what we do since officially we are in string freeze

Regarding the changes to the help menu, they are so minor, I see no use in breaking all translations just for that...

I can see your point (though in the case of "resolution" I outlined a reason).

In the help menus this wouldn't break up translations. Remember all the grammar that I did is ENGLISH grammar and in the translations any missing periods may have been corrected. There's really no difference from me correcting it with launchpad. However I realise that you are in a string freeze. Does that freeze end once 0.8.0 is out or does it break earlier.

Hero {l Wrote}:Here are some edits to the help menus fixing things such as grammar (periods, commas, colons and semicolons), speeling, etc..

ah yes, we really have to watch out for speeling

You're quick on that.

"ah yes, we really have to watch out for speeling" >> "Ah yes, we really have to watch out for spelling."

Thanks,
Hero

No, translations don't work this way. When the original english string is modified, it becomes a totally new string (the computer is not smart enough to see you only changed punctuation), so all translations that currently exist for that string are lost

Ah. So it's reliant on the English version in the stkgui files?

Exactly. Think of the English strings as the "variables" the software puts into a function to fetch the translations. If the variable name changes, it's a new variable and the old one is gone.