StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5828257
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
29
CommunityOwnedDate
CreationDate
2011-04-29T05:29:34.287
FavoriteCount
0
LastActivityDate
2011-04-29T12:07:46.447
LastEditDate
2011-04-29T12:07:46.447
LastEditorUserId
506879
OwnerUserId
506879
ParentId
5828091
PostTypeId
2
Score
20
ViewCount
0
LastEditorDisplayName
text
Body
You could use the String constructor with the charset parameter: <pre><code>try { final String s = new String(nodevalue.getBytes(), "UTF-8"); } catch (UnsupportedEncodingException e) { Log.e("utf8", "conversion", e); } </code></pre> Also, since you get the data from an xml document, and I assume it is encoded UTF-8, probably the problem is in parsing it. You should use <code>InputStream</code>/<code>InputSource</code> instead of a <code>XMLReader</code> implementation, because it comes with the encoding. So if you're getting this data from a http response, you could either use both <code>InputStream</code> and <code>InputSource</code> <pre><code>try { HttpEntity entity = response.getEntity(); final InputStream in = entity.getContent(); final SAXParser parser = SAXParserFactory.newInstance().newSAXParser(); final XmlHandler handler = new XmlHandler(); Reader reader = new InputStreamReader(in, "UTF-8"); InputSource is = new InputSource(reader); is.setEncoding("UTF-8"); parser.parse(is, handler); //TODO: get the data from your handler } catch (final Exception e) { Log.e("ParseError", "Error parsing xml", e); } </code></pre> or just the <code>InputStream</code>: <pre><code>try { HttpEntity entity = response.getEntity(); final InputStream in = entity.getContent(); final SAXParser parser = SAXParserFactory.newInstance().newSAXParser(); final XmlHandler handler = new XmlHandler(); parser.parse(in, handler); //TODO: get the data from your handler } catch (final Exception e) { Log.e("ParseError", "Error parsing xml", e); } </code></pre> Update 1 Here is a sample of a complete request and response handling: <pre><code>try { final DefaultHttpClient client = new DefaultHttpClient(); final HttpPost httppost = new HttpPost("http://example.location.com/myxml"); final HttpResponse response = client.execute(httppost); final HttpEntity entity = response.getEntity(); final InputStream in = entity.getContent(); final SAXParser parser = SAXParserFactory.newInstance().newSAXParser(); final XmlHandler handler = new XmlHandler(); parser.parse(in, handler); //TODO: get the data from your handler } catch (final Exception e) { Log.e("ParseError", "Error parsing xml", e); } </code></pre> Update 2 As the problem is not the encoding but the source xml being escaped to html entities, the best solution is (besides correcting the php to do not escape the response), to use the <a href="http://commons.apache.org/lang/download_lang.cgi" rel="noreferrer">apache.commons.lang library</a>'s very handy <code>static StringEscapeUtils class</code>. After importing the library, in your xml handler's <code>characters</code> method you put the following: <pre><code>@Override public void characters(final char[] ch, final int start, final int length) throws SAXException { // This variable will hold the correct unescaped value final String elementValue = StringEscapeUtils. unescapeHtml(new String(ch, start, length).trim()); [...] } </code></pre> Update 3 In your last code the problem is with the initialization of the <code>nodevalue</code> variable. It should be: <pre><code>String nodevalue = StringEscapeUtils.unescapeHtml( new String(ch, start, length).trim()); </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POdecode string encoded in utf-8 format in android
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USrekaszeru
UserOwnerUserId
1. USrekaszeru
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POdecode string encoded in utf-8 format in android
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId

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.