StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
547149
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-02-13T18:38:43.197
FavoriteCount
0
LastActivityDate
2010-11-17T20:02:35.313
LastEditDate
2010-11-17T20:02:35.313
LastEditorUserId
12597
OwnerUserId
12597
ParentId
546994
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
text
Body
i found it. The answer is no: The XmlDocument will not honor the ContentEncoding of the response stream it's writing to. <hr> Update: the proper way to do it <ol> <li>Use <code>Response.Output</code>, and NOT <code>Response.OutputStream</code>. Both are streams, but <code>Output</code> is a <code>TextWriter</code>. When an <code>XmlDocument</code> saves itself to a <code>TextWriter</code>, it will use the encoding specified by the <code>TextWriter</code>. The <code>XmlDocument</code> will automatically change any xml declaration node, i.e.: <?xml version="1.0" encoding="ISO-8859-1"?> to match the encoding used by the <code>Response.Output</code>'s encoding setting.</li> <li>The <code>Response.Output</code> <code>TextWriter</code>'s encoding settings comes from the <code>Response.ContentEncoding</code> value.</li> <li>Use <code>doc.Save</code>, not <code>Response.Write(doc.ToString())</code> or <code>Response.Write(doc.InnerXml)</code> You DON'T want to Save the xml to a string, or stuff the xml into a string, and <code>response.Write</code> that, because that: <ul> <li>doesn't follow the encoding specified</li> <li>wastes memory</li> </ul></li> </ol> To sum up: by Saving to a <code>TextWriter</code>: the XML Declaration node, the XML contents, and the HTML Response content-encoding will all match. Sample code: <pre><code>public class Handler : IHttpHandler, System.Web.SessionState.IRequiresSessionState { //Note: We add IRequiesSessionState so that we'll have access to context.Session object //Otherwise it will be null public void ProcessRequest(HttpContext context) { XmlDocument doc = GetXmlToShow(context); //GetXmlToShow will look for parameters from the context if (doc != null) { context.Response.ContentType = "text/xml"; //must be 'text/xml' context.Response.ContentEncoding = System.Text.Encoding.UTF8; //we'd like utf-8 doc.Save(context.Response.Output); //doc save itself to the textwriter, using the encoding of the text-writer (which comes from response.contentEncoding) } #region Notes /* * 1. Use Response.Output, and NOT Response.OutputStream. * Both are streams, but Output is a TextWriter. * When an XmlDocument saves itself to a TextWriter, it will use the encoding * specified by the TextWriter. The XmlDocument will automatically change any * xml declaration node, i.e.: * <?xml version="1.0" encoding="ISO-8859-1"?> * to match the encoding used by the Response.Output's encoding setting * 2. The Response.Output TextWriter's encoding settings comes from the * Response.ContentEncoding value. * 3. Use doc.Save, not Response.Write(doc.ToString()) or Response.Write(doc.InnerXml) * 3. You DON'T want to Save the xml to a string, or stuff the xml into a string * and response.Write that, because that * - doesn't follow the encoding specified * - wastes memory * * To sum up: by Saving to a TextWriter: the XML Declaration node, the XML contents, * and the HTML Response content-encoding will all match. */ #endregion Notes } public bool IsReusable { get { return false; } } } </code></pre> <hr> The encoding that the XmlDocument will use when saving to a stream depends on the encoding specified in the xml declaration node. e.g.: <pre><code> <?xml version="1.0" encoding="UTF-8"?> </code></pre> If "UTF-8" encoding is specified in the xml declaration, then Save(stream) will use UTF-8 encoding. If no encoding is specified, e.g.: <pre><code><?xml version="1.0"?> </code></pre> or the xml declaration node is omitted entirely, then the XmlDocument will default to UTF-8 unicode encoding. (<a href="http://msdn.microsoft.com/en-us/library/system.xml.xmldeclaration.encoding.aspx" rel="noreferrer">Reference</a>) <blockquote> If an encoding attribute is not included, UTF-8 encoding is assumed when the document is written or saved out. </blockquote> <a href="http://msdn.microsoft.com/en-us/library/system.xml.xmldeclaration.encoding.aspx" rel="noreferrer">Some common encodings strings</a>, that you could also use in the xml declaration, are: <ul> <li>UTF-8</li> <li>UTF-16</li> <li>ISO-10646-UCS-2</li> <li>ISO-10646-UCS-4 </li> <li>ISO-8859-1</li> <li>ISO-8859-2</li> <li>ISO-8859-3</li> <li>ISO-8859-4</li> <li>ISO-8859-5</li> <li>ISO-8859-6</li> <li>ISO-8859-7</li> <li>ISO-8859-8</li> <li>ISO-8859-9</li> <li>ISO-2022-JP</li> <li>Shift_JIS</li> <li>EUC-JP</li> </ul> Note: The encoding attribute is not case sensitive: <blockquote> Unlike most XML attributes, encoding attribute values are not case-sensitive. This is because encoding character names follow ISO and Internet Assigned Numbers Authority (IANA) standards. </blockquote> If you loaded your XML from a string or a file, and it did not contain an xml declaration node, you can <a href="http://msdn.microsoft.com/en-us/library/system.xml.xmldeclaration.encoding.aspx" rel="noreferrer">manually add one to the XmlDocument</a> using: <pre><code>// Create an XML declaration. XmlDeclaration xmldecl; xmldecl = doc.CreateXmlDeclaration("1.0", null, null); xmldecl.Encoding="UTF-8"; // Add the new node to the document. XmlElement root = doc.DocumentElement; doc.InsertBefore(xmldecl, root); </code></pre> If the XmlDocument does not have an xml declaration, or if the xml declaration does not have an encoding attribute, the saved document will not have one either. Note: If the XmlDocument is saving to a TextWriter, then the encoding that will be used is taken from the TextWriter object. Additionally, the xml declaration node encoding attribute (if present) will be replaced with the encoding of the TextWriter as the contents are written to the TextWriter. (<a href="http://msdn.microsoft.com/en-us/library/sa5wd18z.aspx" rel="noreferrer">Reference</a>) <blockquote> The encoding on the TextWriter determines the encoding that is written out (The encoding of the XmlDeclaration node is replaced by the encoding of the TextWriter). If there was no encoding specified on the TextWriter, the XmlDocument is saved without an encoding attribute. </blockquote> If saving to a string, the encoding used is determined by the xml declaration node's encoding attribute, if present. <hr> In my specific example, i am writing back to an Http client through ASP.NET. i want to set the Response.Encoding type to an appropriate value - and i need to to match what the XML itself will contain. The appropriate way to do this is to save the xml to the Response.Output, rather than the Response.OutputStream. The Response.Output is a TextWriter, who's Encoding value follows what you set for the Response.Encoding. In other words: <pre><code>context.Response.ContentEncoding = System.Text.Encoding.ASCII; doc.Save(context.Response.Output); </code></pre> results in xml: <pre><code><?xml version="1.0" encoding="us-ascii" ?> <foo>Hello, world!</foo> </code></pre> while: <pre><code>context.Response.ContentEncoding = System.Text.Encoding.UTF8; doc.Save(context.Response.Output); </code></pre> results in xml: <pre><code><?xml version="1.0" encoding="utf-8" ?> <foo>Hello, world!</foo> </code></pre> and <pre><code>context.Response.ContentEncoding = System.Text.Encoding.Unicode; doc.Save(context.Response.Output); </code></pre> results in xml: <pre><code><?xml version="1.0" encoding="utf-16" ?> <foo>Hello, world!</foo> </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POASP.NET: Will Saving an XmlDocument to the Response.OutputStream honor the encoding?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USIan Boyd
UserOwnerUserId
1. USIan Boyd
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POASP.NET: Will Saving an XmlDocument to the Response.OutputStream honor the encoding?
 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
 VTAcceptedByOriginator
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
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.