Log translation

[Miguel Gimenez]

Translation of Log() messages is not coherent, many use _() but others do not.

Is there a reason to not translate them? Of course, keeping them untranslated makes searching in the web easier, but some users do not understand the english messages.

[stahta01]

Translation of Log() messages is not coherent, many use _() but others do not.

Is there a reason to not translate them? Of course, keeping them untranslated makes searching in the web easier, but some users do not understand the english messages.

This has very little to do with Code::Block! It has almost everything to do with the Compiler/Toolchain!

Edit: If you are not talking about the "Build Log" please state which!

Tim S.

[Miguel Gimenez]

I am talking about log messages like these:

Code Select Expand


Manager::Get()->GetLogManager()->DebugLog(_T("Could not find File->New menu!"));
CCLogger::Get()->DebugLog("SetParser: No parser available.");
Manager::Get()->GetLogManager()->Log(_T("cbEditor::AutoComplete() is obsolete.\nUse AutoComplete(cbEditor &ed) from the Abbreviations plugin instead."));
Manager::Get()->GetLogManager()->Log(_("Error: file 'options_") + name + _(".xml' not found"));
Manager::Get()->GetLogManager()->DebugLog(_T("Compiler circular dependency detected?!?!?"));


[BlueHazzard]

I think debug logs should not really be translated... They would make error checking of localized cb more difficult for us...
But "Log" and "Error" should probably be translated? But this makes things inconsistent...

[Miguel Gimenez]

But this makes things inconsistent...

Now it is almost random, so inconsistency (entropy?) is maximum. I agree with you, "normal" messages should be translated while "debug" ones should not, so a casual user would see everything in his language.