revision 13170

additional untranslated string discovered. see attached additional_untranslated.png

Be careful - tip of trigger statuses stored into DB in 'triggers' table row 'error'
p.s. I still will add here pictures with not translated places. Do not hasten to resolve this issue. I will try to inform you in addition when I can already find nothing.

no more suggestion. Now you can resolve this is issue.

picture '5.untranslated_tip_statuses_of_trigger.png' is planed to resolve in the separate ZBXNEXT-567

I checked dev/ZBX-2647 branch. I know that it can be not finished yet, but i want to report something.
info(S_ITEM_UNLINKED, $db_item["key_"]);
info(sprintf(S_TRIGGER_UNLINKED, $trigger['description']));
this is difference (sprintf using-not using) are normal ?

'S_CIRCULAR_LINK_CANNOT_BE_CREATED'=> 'Circular link can not be created'
is exist early.
need to remove new duplicate
'S_CIRCULAR_LINK_CANNOT' => 'Circular link can not be created',

At picture 12.two_different_palaces.png stay untranslated "Incorrect resource" text.
Stay untranslated 8. and 9. pictures.
Picture 9. is the duplicate of ZBX-2586 - don't forget to close it when fulfil this issue.

I must say that I have concentrated on the trunk version, and new strings for branche I will not have to translate. I will do so only in the trunk.
If you have done this a bit earlier, before gettextization - it would be great.
oh, i see an dev/ZBX-2647-trunk - don't worry

Unlike Oleksiy, I have not checked dev/ZBX-2647 branch yet, but in dev/dev-491 branch the message "Circular link cannot be created" also appears when I try to link template C to B, B to A, and C to A, which is wrong. Just FYI.

Thank you, Oleksiy!

>info(S_ITEM_UNLINKED, $db_item["key_"]);
>info(sprintf(S_TRIGGER_UNLINKED, $trigger['description']));
You are right, I've corrected this place.

>S_CIRCULAR_LINK_CANNOT_BE_CREATED'=> 'Circular link can not be created' is exist early.
I've corrected this one too.

>At picture 12.two_different_palaces.png stay untranslated "Incorrect resource" text.
Seems, that in latest revision this string is changed to "Incorrect resource provided for screen item". It is translatable now.

All provided cases and many more found on the way are marked for translations in trunk as well. It is possible, that there are more untranslated string in API exceptions, but I think they should be dealt with step by step.

Tip "Zabbix was restarted" (5.untranslated_tip_statuses_of_trigger.png) comes from Zabbix server and cannot be translated through frontend.

Thank you for fulfilling this request. In return I promise that I will make Ukrainian and help with Russian translation for the 1.8 branch. This is a token of my gratitude to you.

About picture (5.untranslated_tip_statuses_of_trigger.png) as we discussed with Richlv - it can be translated and for this i registered separate ZBXNEXT-567. The same partially for picture (8.untranslated_in_web_sc2.png) - "page didn't match"

Some details of this issue I will add to the others.
Let's close this issue, and if i find the remarks - we will deal with them separately.

For trunk version it seems you forgot to include modified files to POTFILES.in

thanks for the note. now all php files will be scanned for translatable strings

Merged to branches/1.8: 16294
Merged to trunk: 16298