Hi Khoryolis,
I’ve never used that plugin specifically, but the strings are generated with i18n in mind, and nothing in SuperCPT would preclude the strings from being translated. Specifically, I used WordPress’ _x i18n function, which defines a string to have a context, and I set the context to be the custom post type name.
For instance, say you setup a post type employee. By default, your singular and plural strings are “Employee” and “Employees”. The translatable context is “employee”, and the individual strings are:
Employees
Employee
New Employee
Add New Employee
Edit Employee
New Employee
View Employee
Search Employees
No Employees found
No Employees found in Trash
Parent Employee:
If for some reason qTranslate won’t allow you to translate these, you should alert that plugin’s author to the issue.
Best of luck!
Okay, thank you,I’ll find a way to reach my needs and keep you in touch.
Bye.