I followed this
First, embedding is seriously discouraged unless you’re willing to keep up with updates to Redux. Otherwise, your users won’t benefit from updates or security fixes.
Second: When you’re writing your options panel, you have to add them in your sections and fields, like this:
Redux::set_field(
'OPT_NAME',
'SECTION_ID',array(
'id'=>'my-sample-textarea',
'type'=>'editor',
'title'=>esc_html__('Sample Text Area','my-text-domain'),
'subtitle'=>esc_html__('Write here your copyright text!','my-text-domain'),
'default'=>'Powered by Redux Framework.',
)
);
If you use translators in your options arrays, the translations will compile in your POT file. I don’t specifically know how you are implementing your translations or compiling them. That’s not something we support, actual theme/plugin development. There are numerous resources on the internet on how to compile and implement WordPress translations properly. See: https://www.hostinger.com/tutorials/wordpress/how-to-translate-wordpress-theme-using-poedit
As far as translatable strings inside Redux, they have translators on them. The problem is the translations PO/MO files are not complete. They’re hosted here. We encourage Redux devs and users to contribute. It may be why you’re not seeing a complete translation, depending on the language and the required percentage completion for that file. See here:
Good luck.