Avoid usage of localized strings before initialization during import in many modules

This happens if import is done before i18n setup
(InstallLocalRessources()).
This affects PLCOpenEditor mostly. Beremiz IDE is free from this issue, but moving
initialization from import should make modules more robust.
Otherwise execution result depends on where and when import was done
and this is not a good thing.

Some modules (ConfigTreeNode, features, CodeFileEditor related
classes) still have this, but they are used only in Beremiz.
Most problems result in non-working internatialization.
In some cases (VariablePanel) there is backtrace, because localized
key is not found in non-localized dictionary.

     1

all:

     2

	@echo "Please specify target 'source_list', 'template' or 'locales'"

     3

     4

template:

     5

	@echo To generate translation template message.pot file:

     6

	python mki18n.py -p --domain=Beremiz

     7

     8

locales:

     9

	@echo "Generate .mo files for all languages:"

    10

	python mki18n.py -m --moTarget=../locale --domain=Beremiz

    11

    12

    13

source_list:

    14

	echo @To "Generate list with source files: app.fil:"

    15

	find .. -name "*.py" -exec grep -q '_(' {} ';' -print -o -name "*XSD*" -print -o -name "*.csv" -print | grep -v '/build/' | grep -v '/pyjs/' > app.fil

    16

	echo "../plcopen/Additional_Function_Blocks.xml" >> app.fil

    17

	echo "../plcopen/Standard_Function_Blocks.xml"   >> app.fil

    18

    19

.PHONY: all, template, locales, source_list