| 1 |
<wpml-config> |
| 2 |
<!-- |
| 3 |
SureForms WPML Configuration. |
| 4 |
|
| 5 |
Tells WPML which SureForms structures are translatable. |
| 6 |
|
| 7 |
Design principles: |
| 8 |
1. The `sureforms_form` CPT is NOT translatable — we ship ONE form per |
| 9 |
`post_id` and translate its strings via WPML String Translation. |
| 10 |
This keeps entries unified on a single form regardless of language. |
| 11 |
2. Block-attribute strings (labels, placeholders, help, errorMsg, option |
| 12 |
labels, etc.) are NOT declared here. They are registered |
| 13 |
programmatically at form-save time by String_Collector using a |
| 14 |
per-form naming scheme (`form_{form_id}_block_{block_id}_{attribute}`) |
| 15 |
so each form's strings stay grouped together in WPML's String |
| 16 |
Translation UI rather than appearing as flat per-block-type entries. |
| 17 |
3. ALL form-level meta — submit button text, notifications, confirmation |
| 18 |
messages and the restriction message — is registered programmatically by |
| 19 |
String_Collector under a per-form naming scheme (e.g. `form_{form_id}_submit_button`) |
| 20 |
rather than via `<custom-fields>`. This keeps every form's strings grouped |
| 21 |
together in WPML's String Translation UI, avoids WPML's nested-array |
| 22 |
<custom-fields-texts> quirks, and prevents a duplicate/dead declaration |
| 23 |
competing with the programmatic registration at render time. |
| 24 |
|
| 25 |
@since x.x.x |
| 26 |
--> |
| 27 |
|
| 28 |
<!-- Do NOT duplicate the SureForms form CPT per language. --> |
| 29 |
<custom-types> |
| 30 |
<custom-type translate="0">sureforms_form</custom-type> |
| 31 |
</custom-types> |
| 32 |
</wpml-config> |
| 33 |
|
