Last Updated on December 31, 2017 by Neil Murray
RESOLVED:
[1] Update .pot file to reflect the new translation phrases included in the Indonesian .po file.
[2] The term "Display Log" is not translated in the "Advanced" tab of CF7Skins.

[3] The term "skins" in the meta box is more of a marketing decision, since this is what the CF7 Skins would be displayed as in the search engines and elsewhere. Direct translation to the target language would not be ideal. Code here: admin.php#188 and admin.php#215
The following terms are part of a sentence with the subject missing. This makes translation to other languages harder as conjugation rules vary across languages. For example, in Nepali (or Hindi), translation of a sentence like "CF7 Skins makes your job easier" would have other characters morphed into the subject "CF7Skins" without spaces (like how "'s" morphs into a subject in English). So, just translating the rest of the sentence while putting the subject "CF7Skins" as placeholder wouldn't work. The whole sentence will have to be translated.
[x] getting-started.php[x] pro-version.php
[4] Term: "makes it easier for regular WordPress users to create forms using built in" in getting-started.php#12.
[5] Term: "covers from how to get started up to how to customize your forms and everything else in between." in getting-started.php#50
[6] Term: "browse over some commonly asked questions." in pro-version.php#151
[7] Term: a great place to find detailed answers."" in pro-version.php#154
[8] Term: "maintained by the CF7 Skins Support Team to help you solve most questions. You can search it either by Categories & Tags or Keywords." in pro-version.php#157
[9] Term: "to help you get started using CF7 Skins quickly & easily." in getting-started.php#56 and pro-version.php#160
[10] Term: "you can search by Categories & Tags or Keywords." in getting-started.php#53
[11] Term: "leave a plugin review on WordPress.org" in getting-started.php#70 and pro-version.php#136
[12] Term: "add your Testimonial to those listed" in getting-started.php#73 and pro-version.php#139
[13] Term: "log in & vote "works" on your current versions" in getting-started.php#76 and pro-version.php#142
[14] Term: "help us to improve CF7 Skins by offering feedback" getting-started.php#79 and pro-version.php#145
[15] Term: "browse over some commonly asked questions." in getting-started.php#87
[16] Term: "covers from how to get started up to how to customize your forms and everything else in between." in getting-started.php#50
[17] Term: "to help you get started quickly with CF7 Skins." in getting-started.php#96
… and several other with similar problems. Basically, sentences that have subject or other noun missing in them have this problem. All of these need to be fixed. Solution might not be generic to all and might need some case-by-case inspection.
CONTINGENT ON OTHER FACTORS:
The problems 1, 4 and 5 arise in CF7Skins Logic, Multi, Pro and Ready:
[1] The post-installation prompts are in English, not in the selected language of WP.

The problems 2 and 3 arise because name of the plugin is just in English and does not provide translations.
[2] Menu titles in the dashboard are in English, not in the selected language of WP.
[3] Page titles (of HTML – shown in the browser) are still in English, not in the selected language.
[4] The terms "Active Licenses" and "License Key" in the CF7Skins license page are not translated.
[5] The prompts to enter licenses are not translated.

UPDATE: Sastra contacted the GTE and PTE and so translation will be done again at 26 December, with Sastra helping them translate the untranslated string.
[ ] The feedback from Indonesian PTE/GTE is that there are several issues with the Indonesian translation. See the conversation below:

You can find the BitBucket issue of this here.
Notes:
- Make sure someone else can understand each problem easily
- Add image showing problem – where necessary
- Add links to code in Bitbucket showing where code is incorrect – if possible
- Also list problems on the Bitbucket issue
- On Bitbucket you can also edit your existing comments rather create a new comment.
I like your idea of keeping Notes at bottom of the post – works well.