nit-pick-bicker: Translated strings don't print well to console/log

[SwissalpS]

unifieddyes/init.lua

Line 45 in 521b73d

print(S("[UnifiedDyes] Loaded!"))

Translating debug mesages doesn't make debugging easier either.

The common syntax using '[...]' seems to be symbolizing a mod, so print('[unifieddyes] loaded') would be the way most filters expect the message.

It's not important though, it just grabbed my attention when looking at the translation file.

[wsor4035]

trival to leave it or remove it. the rest of the logs are going to most likely be in english, so at this time i dont see a reason for it to be translated. however it probably should be updated to use minetest.log to follow minetest log levels

[SwissalpS]

The output isn't translated. Output is the original string wrapped in translator markers.
Terminals try to deal with the escape sequence and depending on the mod, it finds something valid or not.

Yes, cleanest would probably be to use minetest.log('info', '[unifieddyes] loaded') but I'm not sure that's the intention of this line.
log lines are not output to stdout.
It seems to me, that generally this 'mod has loaded' line is output to stdout and not logs. It gives a nice quick overview of which mods loaded without having to scour the log file.

[wsor4035]

...print goes to logs

EDIT: disregard this

[OgelGames]

...print goes to logs

No, it doesn't, even with the log level set to verbose.

[wsor4035]

it appears that you are correct. for some reason i thought it went to logs