So the easy way (Add Reference in Visual Studio) did not work. Along some exported functions, it provides some COM classes but does not contain a typelibrary. The MLang.dll is in the Windows\system32 directory. DetectOutboundCodePageInIStream (for streams).Wow! This sounded more than promising! The interface has only two methods: This interface extends IMultiLanguage2 by adding outbound text detection functionality to it. This is what MSDN says about this interface: Internet Explorer 5.5 introduced a new interface exported from the MLang DLL: IMultiLang3. A wrapper function to the DetectInputCodepage is provided in the EncodingTools class. Even this was not suitable for my problem, and I wondered if there had been development since version 5.0. This method detects the encoding used in a text (used by Internet Explorer to do automatic codepage detection if the header is missing from a page). Then I remembered the IMultiLang2.DetectInputCodepage method that was introduced along with Internet Explorer 5.0. So this method can only distinguish between ASCII (7bit), single byte (8bit) and the different Unicode flavors (UTF-7, UTF8, Unicode, etc.). The codepage is only used to map single bytes to the correct character for display. All single byte encodings are binary equal in their encoding result. This is not only ugly, it does not even work properly. If no errors remember the encoding that produced the fewest bytes.Built a list of suitable encodings (only iso-codepages and unicode).My first attempt was a simple brute-force attack: I wondered if it is possible to detect the best encoding from the given text. But it is definitely not a good solution if you have an end-user GUI application (most users do not even know what an "encoding" is). This is fine as long as you know the target character set or always assume Unicode. The user had to provide the charset to use for the Transfer-Encoding by hand. The body of the email is passed as String. I started this along with another component that constructs MIME conformant emails. The EncodingTools class offers some easy-to-use functions to determine the best encoding for different scenarios. This is very handy for codepage detection of text stored in files or for text that needs to be sent over the internet. Similarly, the IMultiLang2 interface has a function to detect the encoding of an incoming byte array. But luckily, Microsoft provides the MLang API, in which the IMultiLang3 interface is used for outbound encoding detection.
#Texpad change encoding code#
One could argue that Unicode always does the trick but I needed the most efficient (byte saving) way to transfer data.ĭetecting a code page from text is a very tricky task. In some cases, you need to know what the best codepage (encoding) is to either transfer text over the internet or store it in a text file.
0 kommentar(er)
