It is something you have to troubleshoot on your end. The issue is somewhere in your code or in the way of how you try verifying/viewing the serialization result. I can tell that the original arabic text is تجربة 6 (المجموعة الأولى), and what you saw in your observation is simply the UTF-8 code points of this arabic text incorrectly read/interpreted using some ANSI encoding. But i can tell with certainty that the result of تجربة 6 (المجموعة الأولى) clearly shows one of these three problems apply to your issue. I can't tell which of the three problems are happening in your situation, because the perceived (reported) outcome of those problems can be indistinguishable from each other. This would also include some unusual faulty custom JsonConverter mangling data. This can happen if there are some faulty text processing/conversion steps before serialization happening (Like for example, if the text is being passed between different tools/libraries each doing their own text encoding handling. The original text values got already mangled before being fed into the json serializer. (That includes code/libraries that transmit strings using UTF-8, but using a protocol not supporting UTF-8 or failing to signal the correct encoding to the receiver.) After downloading Unzip or unzip the RAR file and open the format (use WinRAR to download the. Uninstall first using I Obit Uninstaller Pro. The string produced by JsonConvert.SerializeObject is transmitted by some code/library which does not enforce UTF-8 encoding on the receiver/reader side. Download the full version of AnyTrans Crack first. The serialized json text itself is intact and accurate (using UTF-8 encoding), but a wrong text encoding is used when reading/inspecting the json text back. Problems like these are not caused by JsonConvert.SerializeObject, and are normally caused by one of three things:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |