Of course that's logical.
My questions are not because they can not solve; but because in some cases it works, and not in others.
Examples:
CASE 1
I think an extra field: /etc/form/com_componentname.view (view = article, product, category, item, etc.).
And translation in: /language/en-GB/en-GB.tpl_template_name.ini. The translation works perfect.
CASE 2
I think an extra field: /etc/extrafields/extrafieldgroup.xml
And translation in: /language/en-GB/en-GB.tpl_template_name.ini. The translation is not working.
For case 2, the solutions would be:
a) the translation in template_name.sys.ini. Which is incorrect and translation would not work in Front-End. And create the same translation in template_name.ini to work in front-end makes no sense.
b) create the file: /etc/form/com_componentname.view.xml. with the following code:
<?xml version="1.0" encoding="utf-8"?>
<form></form>
Note: I've seen those Joomlart make the translation to extra fields in template_name.ini; but always use the /etc/form/com_componentname.view.xml(com_content.article.xml file). I would like to do only with /etc/extrafields/extrafieldgroup.xml tests; And see if there is a solution to that little problem.