Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>'?' characters occur when data is going through a Unicode-to-Ansi conversion to an Ansi charset that does not support the Unicode characters being converted.</p> <p>What version of C++Builder are you using? In versions prior to CB2009, you should tell Indy the encoding of the AnsiString data that you are passing in. Indy defaults to ASCII (ie: <code>TIdTextEncoding::ASCII</code>) for most String-based operation. That can be overridden when needed, either with optional <code>AAnsiEncoding</code> parameters, the <code>TIdIOHandler::DefAnsiEncoding</code> property, or the global <code>Idglobal::GIdDefaultAnsiEncoding</code> setting. If you do not specify the correct encoding, the AnsiString data may not be converted to Unicode correctly before then being converted to UTF-8. For example:</p> <pre><code>AContext-&gt;Connection-&gt;IOHandler-&gt;WriteLn(cxMemo1-&gt;Text, TIdTextEncoding_UTF8, TTIdTextEncoding_Default); </code></pre> <p>Or:</p> <pre><code>AContext-&gt;Connection-&gt;IOHandler-&gt;DefAnsiEncoding = TIdTextEncoding_Default; AContext-&gt;Connection-&gt;IOHandler-&gt;WriteLn(cxMemo1-&gt;Text, TIdTextEncoding_UTF8); </code></pre> <p>You can optionally also use the <code>TIdIOHandler::DefStringEncoding</code> property if you do not want to specify the UTF-8 encoding on every call:</p> <pre><code>AContext-&gt;Connection-&gt;IOHandler-&gt;DefStringEncoding = TIdTextEncoding_UTF8; AContext-&gt;Connection-&gt;IOHandler-&gt;WriteLn(cxMemo1-&gt;Text); </code></pre> <p>Now, with that said, the fact that <code>WriteFile()</code> is also sending data that J2ME is not handling correctly tells me that Indy is not the root of the issue. WriteFile() simply dups the raw file data as-is to the connection without any interpretation at all. If you send a UTF-8 encoded file, then UTF-8 encoded octets will be sent to J2ME.</p> <p>I suggest you use a packet sniffer, such as Wireshark, to verify the data that Indy is sending. That will tell you for sure whether Indy is really at fault or not.</p> <p>*PS: notice in the examples above that I use Indy's <code>TIdTextEncoding</code> macros instead of <code>TEncoding</code> directly. This is because Indy's TIdTextEncoding logic works around some bugs in Embarcadero's <code>TEncoding</code> classes. Also, we're going to phase out direct support for <code>TEncoding</code> in Indy 11 and expand on <code>TIdTextEncoding</code> so Indy has more control than Embarcadero offers.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to send text in UTF-8 using Indy TIdTCPServer in c++ builder
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRemy Lebeau
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COHi @Remy I'm using C++ Builder 2010 !
      singulars
      1. PO
      1. USSuhrob Samiev
    2. COAlso this way doesn't helping too `try { int b=AContext->Connection->IOHandler->ReadByte(); result->Items->Add(b); //AContext->Connection->IOHandler->WriteFile("c:\\fids.xml"); AContext->Connection->IOHandler->DefStringEncoding = TIdTextEncoding::UTF8; AContext->Connection->IOHandler->Write(cxMemo1->Text); AContext->Connection->Disconnect(); } catch(Exception & e) { //ShowMessage(e.ToString()); AContext->Connection->Disconnect(); }`
      singulars
      1. PO
      1. USSuhrob Samiev
    3. COAll you have done is add a call to `IOHandler->ReadByte()`, you have not changed anything else regarding how you send data back to J2ME. You still need to isolate the root cause of the problem. Did you do what I suggested and verify the raw transmitted data yet? In any case, I know for a fact that `Write(UnicodeString, TIdTextEncoding::UTF8)` works fine in CB2010, because that is the version I use myself. BTW, reading the `cxMemo1->Text` property directly in a `TIdTCPServer` event handler like you are is not thread-safe, so that may be a factor by itself.
      singulars
      1. PO
      1. USRemy Lebeau
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload