FiveTech Software tech support forums

... pues resulta que el que lo lleva en el interior me lee la cadena completa, mientras que la que tiene el adaptador externo, me lee primero un byte, y en la siguiente lectura el resto. Pongo el código: En el díálogo en el que se hace la lectura: oDlg:bCommNotify = { | nComm, nStatus | ...

You can try it using chatgpt: recover the original PRG code from this pcode: HB_FUNC( APRIDBCONPASSWORD ) { static const BYTE pcode[] = { HB_P_FRAME, 0, 2, /* locals, params */ /* 00003 */ HB_P_BASELINE, 138, 0, /* 138 */ HB_P_PUSHLOCALNEAR, 2, /* PASSWORD */ HB_P_PUSHNIL, HB_P_EXACTLYEQUAL, ...

... characteristics: It should have a header that identifies the file as a GIF file and specifies the version of the format. The header should be six bytes long and contain the ASCII characters “GIF89a” It should have a logical screen descriptor that defines the dimensions and properties of the logical ...

This is a UTF8 encoded string. You can use HB_UTF8LEN( cString ) to find the 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 ...

Hi,

There is a string in unicode. The length of Latin characters is 1 byte, the length of characters of other code pages is 2 bytes.
How to get an array of characters of this string ?

Encoding fails when inserting a character string contains 2-Byte ANSI character, e. g. '"üäö". Encoding is OK if the character string contains at least one 2-Byte NON ANSI character, e. g. "П" #include "fivewin.ch"STATIC aStr ...

I noticed that all hexcodes in your example are ANSI and that there are NO UTF8 2-byte hexcodes!

Probably the encoding is already changed to ANSI before the TGet() was activated!?

Maybe it is the text object to display the hexcode directly?

I'll test it tomorrow

... more details in your other posting. All English characters and also all non-accented characters of other languages are encoded as same single byte both in ANSI and UTF8, so there is no problem there. I noticed that this library requires utf8 encoding. If our string containing Umlauts is encoded ...

... mind. While all English characters and all characters of other West European languages other than accented characters are represented by a single byte in both ANSI and UTF8 notiation, the accented characters (which include German Umlauts) are represented by a single byte in ANSI and two bytes ...

... using your Sample i got https://i.postimg.cc/d0607GTW/XLSX-notexist.jpg --- than i create "some.xlsx" but with 0-Byte and i got "wrong Structure" https://i.postimg.cc/C5k5xXC8/fail-open-empty.jpg --- so i try to create Structure of Table, ...

... languages? If you are confined to English and West European languages, all characters other than accented characters are represented by a single byte (and the same byte) both in ANSI and UTF8. So, normal RegEx expressions should work with UTF8 text also, if you are not programming for Asian languages

These issues with Umlauts is fixed in FWH2307 soon to be released.

... = CType(myReq.Proxy, IWebProxy) Dim proxyaddress As String Dim myProxy As New WebProxy() Dim encoding As New ASCIIEncoding Dim buffer() As Byte = encoding.GetBytes(sXmlIda) myReq.AllowWriteStreamBuffering = False myReq.Method = "POST" myReq.ContentType = "text/xml; charset=UTF-8" ...

yes, this issue (bug) is very confusing. To better understand what is happening, I have adjusted the sample again: function Main()   local oDlg   local oGet   local oEdit   local oMulti   local oMemo   local cVar1 := "üäö"   local cVar2 := "üäö"   local cVar3 := "üä...