Hi Dries, in order to enable a conditional layout in a variant, you first have to specify a conditional layout in the Default subject. Afterwards, it is possible to enable and disable conditional layouts for specific variants.
Hi Mark, Thanks for the reply. The IgnoreDiacritics property was already set to Yes, and the reason for the sensitivity to diacritics was that the field was, as you stated, a VARCHAR field. Interestingly, in the Subjects > Data > Filter tab, the box “In combined filter” was checked for this field; however, after changing the datatype to NVARCHAR in the data model, this field became unchecked, which had us puzzled for a while, because we did not expect this to happen. Is this intended behaviour, or would you like me to report this as a bug?
@Arie V Thanks for the reply. We are currently using XML, as such: The result of which should be ภาษาไทย Phasa thai, but is this (notice the ‘&’ sign does get passed to the stored procedure):As Mark stated, the problem is not that special characters such as the & sign are not allowed, but rather that tsf_send_message uses the varchar datatype, which does not support unicode characters such as those from the Thai and Cyrillic character sets.
Hi Mark, thanks for the reply, I will create an idea!
Hi Mark, thanks for your quick response!I am using the far right option. To be honest, I have never used your suggested docking point before, as I have only been using tsf for about two months, but I think that would solve the problem, so thank you for the suggestion. I do still believe it is odd, and unnecessary from a user viewpoint, for the far right slider to be so thin; do you know if there is a good reason for this?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
