Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here is a function I wrote to convert all non-ASCII characters to their corresponding entity. Might help you sanitizing some PCDATA content before output.</p> <pre><code>/** * Creates xml entities for non ascii characters in the given String. */ public static String xmlEntitify(String in){ StringBuffer b = new StringBuffer(); for (int i=0;i&lt;in.length();i++){ Character c = in.charAt(i); if (c&lt;128){ b.append(c); } else if (c=='\ufeff'){ // BOM character, just remove it } else { String cstr = Integer.toHexString(c).toUpperCase(); while(cstr.length()&lt;4){ cstr="0"+cstr; } b.append("&amp;#x"); b.append(cstr); b.append(";"); } } return b.toString(); } </code></pre> <p>Read your input stream into a <code>String content</code>, and write into the output stream <code>xmlEntitify(content)</code>.</p> <p>Your output is guaranteed to contain only ASCII characters, no more encoding problem.</p> <p><strong>UPDATE</strong></p> <p>Given the comments, I'll be even bolder : if you are not sanitizing your data, you are calling for trouble. I guess you are at least already replacing the <code>&lt;</code> and <code>&amp;</code> characters in your PCDATA. If not, you definitely should. I have another version of the above method which, instead of the first <code>if</code>, has :</p> <pre><code>if (c&lt;128 &amp;&amp; c!='&amp;' &amp;&amp; c!='&lt;' &amp;&amp; c!='&gt;' &amp;&amp; c!='"'){ b.append(c); } </code></pre> <p>so that these characters are also converted to their corresponding Unicode entity. This converts all of my PCDATA to unicode-friendly ASCII-only strings. I had no more encoding problem since I'm using this technique. I don't ever output XML PCDATA which has not been passed through this method : this is not sweeping the elephant under the carpet. It is just getting rid of the problem by being as generic as can be.</p>
    singulars
    1. This table or related slice is empty.
    1. POConvert XML document from Latin1 to UTF8 using Java
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USglmxndr
    1. USglmxndr
    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. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis solves the wrong problem. He needs to UTF-8 encode the output stream, which is VERY different from substituting character entities for non-ascii data. Those character entities will still point to the Latin1 code points, not the requisite UTF-8 code points.
      singulars
      1. PO
      1. USJim Garrison
    2. COAs Jim wrote (and my colleague pointed out to me) this is simply covering up the problem. This became my temporary solution just because I needed a quick fix but when I have time I will go back and rewrite my code because it is simply wrong.
      singulars
      1. PO
      1. USUmYeah
    3. COHaha, so great. I'm downvoted for the only answer that brings something so far. I love you pals. @Jim : I know I did not answer the question in the desired way. If someone comes up with a better fix, I'll be glad to upvote it and use it in my own code. So far, sanitizing the PCDATA has always been the best way for me, which works in all the cases. @UmYeah : when you have only ASCII characters, you text is UTF-8 encoded. You just have changed the way the extended characters are referred to. You let to the client the responsability to format them.
      singulars
      1. PO
      1. USglmxndr
 

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