... common folder. The Shrinker is called Aspack .. and an additional benefit is that your .exe once shrinked makes it impossible for anyone to use a hex edit to look at your .exe which could revel your source code .. here is the link .. http://www.aspack.com/downloads.html Thanks Rick Lipkin Last ...
... common folder. The Shrinker is called Aspack .. and an additional benefit is that your .exe once shrinked makes it impossible for anyone to use a hex edit to look at your .exe which could revel your source code .. here is the link .. http://www.aspack.com/downloads.html Thanks Rick Lipkin Thank ...
... common folder. The Shrinker is called Aspack .. and an additional benefit is that your .exe once shrinked makes it impossible for anyone to use a hex edit to look at your .exe which could revel your source code .. here is the link .. http://www.aspack.com/downloads.html Thanks Rick Lipkin
... .. the smaller the .exe the quicker the program loads .. another benefit of the "shrinker" is that the .exe can not be read with a hex editor that may reveal some of your code ... Here is the link to review Aspack http://www.aspack.com/aspack.html
... vll_term WHERE WORT LIKE CONCAT('%', _utf8'\u00DF', '%'); doesn't work. ChatGPT has obviously made a mistake here. But when I want to use hex codes for the search string, MariaDB has HEX() and UNHEX(). What is the equivalent in plain SQL? ChatGPT says: Certainly, if you're constrained ...
... number of characters (not bytes) and HB_UTF8SUBSTR( cString, n, 1 ) to get the nth character (not byte) Example: Let us take a sample string in Hex: "41C39CC49EE0B095". This is displayed as : AÜĞక #include "fivewin.ch"function Main() local cString := HEXTOSTR( ...
... und C3B6, not DC C4 D6, see for example https://www.charset.org/utf-8! DC C4 D6 are the ANSI hexcodes +---+--------+-----------------+|STR|ANSI-HEX|UTF8-HEX ||üäö|FC E4 F6|C3 BC C3 A4 C3 B6||ÜÄÖ|DC C4 D6|C3 9C C3 84 C3 96|+---+--------+-----------------+ With the ...
... ), "Ü" ) cText := STRTRAN( cText, CHR( 223 ), "ß" )#endif both "seems" to be same (!) even HEX are same so i don´t understand why UTF16toUTF8( strToWide( UML_OEMTOANSI())) did not work to create "right" Excel Sheet
... cRet If you don't mind, I like to ask you some help purely for my knowledge and educational purpose. Can you please post some OEM strings here in Hex? cTextOEM := FieldGet( n )cTextHex := STRTOHEX( cTextOEM ) and please post the hex string. A few strings like that. I am not sure ...
... If you don't mind, I like to ask you some help purely for my knowledge and educational purpose. Can you please post some OEM strings here in Hex? cTextOEM := FieldGet( n )cTextHex := STRTOHEX( cTextOEM ) and please post the hex string. A few strings like that. I am not ...
... this string is encoded. We can find out its encoding by testing with IsUtf8() or still better, with STRTOHEX( c ) The same character is encoded as hex "FC" in ANSI and encoded as hex "C3BC" in UTF8. When FWH displays, both look exacty alike and in fact both represent the same ...
... : which Type for DBF ? "M" or "V" or ? which Type for SQL ? "BLOB" or ? when store "Image" into DBF using HEX or MEMOREAD ? SQL using HEX with "pre-FIX" ? when XBROWSEr / EDIT how to prevent FIELD from "type into" Image FIELD ... how ...