User forums > Using Code::Blocks
9 errors but still build an executable
thomas:
--- Quote from: oBFusCATed on January 29, 2013, 07:26:50 pm ---
--- Quote from: jens on January 29, 2013, 06:30:40 pm ---The easiest way to fix this is to go to "Settings -> Environment -> Environment variables" and add "LC_ALL" as variable and set it to either an english flavour or (more easy) to "C".
--- End quote ---
Is it possible to just force it in the compiler plugin?
--- End quote ---
This is what I'd really do, too. But unluckily, this tremendously stupid thing called "internationalization" is something that a lot of people actually want at every price, even if it kills them. I fear we'd be getting an equal amount of complaints if we forced compiler output to English.
The only solution that would probably work without complaints would be to force to English, and compile files that contain errors again (secretly, in a second pass) to display error messages in a local language, if that is desired. Bah.
I'm certainly OK with having menus and dialogs in German (assuming translations are not of the "typical" quality), but in regards of anything that I might have to type (shell commands, formulas, ...) or find on the internet, it's a nightmare. The same goes for anything a parser might have to decipher.
Try and find out what a Windows service (pick one with a particularly gay sounding name) does. The translated decription consists of only makeup-words that you can't understand as a native speaker. If you type the name into Google, you get directed to some machine-translated fuckshit at MSDN that no sane person can decipher.
Now, if the entire thing was just English (including the service's name) it wouldn't be any kind of problem.
I'm still waiting for the day when you open a command prompt and have to type wv to change a directory and ld to delete a file... It's already like that in MS Excel (and all of its puny clones like OO) where you have to type MITTELWERT or WENN when you mean AVG or IF (which every half-savy person should be able to type, even if they don't have English as native language).
oBFusCATed:
--- Quote from: thomas on January 30, 2013, 12:37:44 pm ---This is what I'd really do, too. But unluckily, this tremendously stupid thing called "internationalization" is something that a lot of people actually want at every price, even if it kills them. I fear we'd be getting an equal amount of complaints if we forced compiler output to English.
--- End quote ---
Then we can redirect them to this issue (I've posted the last comment, btw): http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19165 it is quite old and as it seems no one of gcc's devs really cares.
But reading this bug report I'm not really sure we can force it, always.
--- Quote from: thomas on January 30, 2013, 12:37:44 pm ---The only solution that would probably work without complaints would be to force to English, and compile files that contain errors again (secretly, in a second pass) to display error messages in a local language, if that is desired. Bah.
--- End quote ---
This is too complex for me, we should try to keep it simple. Anyway error messages in some obscure for the internet language are useless, because most of the info is in English out there.
Navigation
[0] Message Index
[*] Previous page
Go to full version