When a pattern for a text question contains a star (*) character it is interpreted differently in CAPI and CAWI modes.
CAPI
NB: 1 = special characters are accepted and 2 = Cyrillic (non-English) letters are accepted in the CAPI input field.
CAWI
Non-English letters and special characters are not accepted in the entry field anywhere when the mask is active.
Wanted:
Consistent behavior of the CAPI and CAWI modes
Possibility to permit ANY character
Possibility to permit ANY LETTER (of any alphabet, but NOT a special character)
Possibility to permit ANY ENGLISH LETTER (of specifically English alphabet)
Possibility to permit ANY character from a specific set
Items 2-5 are to extend the capabilities of the masked edit. The bug itself is in the inconsistent behavior of the CAPI vs CAWI (item nr. 1).
Untested:
It appears that the preloading procedure will follow the CAPI convention if data for masked edit fields is specified in the data file, but creating assignments interactively from the web interface will follow the CAWI convention, and will not allow to enter the same values.
When a pattern for a text question contains a star (*) character it is interpreted differently in CAPI and CAWI modes.
CAPI
NB: 1 = special characters are accepted and 2 = Cyrillic (non-English) letters are accepted in the CAPI input field.
CAWI
Non-English letters and special characters are not accepted in the entry field anywhere when the mask is active.
Wanted:
Items 2-5 are to extend the capabilities of the masked edit. The bug itself is in the inconsistent behavior of the CAPI vs CAWI (item nr. 1).
Untested:
It appears that the preloading procedure will follow the CAPI convention if data for masked edit fields is specified in the data file, but creating assignments interactively from the web interface will follow the CAWI convention, and will not allow to enter the same values.