Answers.Body: <p>There doesn't appear to be an issue with the code after I tested it in a dummy ePub with ePubcheck 3.0.  Since you haven't mentioned how the ePub was created I would trouble shoot by:</p>
  
  <ul>
  <li>Creating a new XHTML file and re-doing the contents of the old XHTML file in it to make sure there isn't any issues with the file or if the file is corrupted.  </li>
  <li>Check to make sure your closing tag is proper or the document ends with <code>&lt;/html&gt;</code>.  This can be tested by opening the XHTML file in a browser such as Chrome and you might get a code error in red at the top.</li>
  <li>Sometimes empty lines after <code>&lt;/html&gt;</code> can cause a validation issue with ePubcheck so make sure to remove them.</li>
  <li>If this was created in an application like Sublime or BBEdit you can always validate the XHTML.</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-04-21T16:19:45.177Z
Answers.LastActivityDate: 2015-04-21T16:19:45.177Z
Answers.UserDisplayName: DᴀʀᴛʜVᴀᴅᴇʀ
Body: <p>The xml string is the same on all the pages (.xhtml files)
  Here is an example: </p>
  
  <pre><code>&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
  &lt;!DOCTYPE html&gt;
  &lt;html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops"&gt;   
  </code></pre>
  
  <p>I appreciate the help!</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-16T17:30:43.357Z
Comments.Text: Does the error tell you exactly which file? The package.opf file is also an xml file, which may be missing the required quotation marks.
Comments.UserDisplayName: Jason Down
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-16T18:03:40.047Z
Comments.Text: I don't understand. Do you have a question, or is this a piece of advice?
Comments.UserDisplayName: Tom
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-16T19:46:23.200Z
Comments.Text: It is a question.  It does tell me the file.  /OEBPS/j83643-Flower-Fairy_-epubBody-26.xhtml(1,15): The value following "version" in the XML declaration must be a quoted string.
Comments.UserDisplayName: Janis Friesler
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-16T19:47:23.880Z
Comments.Text: Sorry I didn't put the whole message here.
Comments.UserDisplayName: Janis Friesler
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-04-23T17:19:09.813Z
Comments.Text: @JanisFriesler if the below doesn't answer your question do you mind making an [edit] to your question so I make a better answer.
Comments.UserDisplayName: DᴀʀᴛʜVᴀᴅᴇʀ
Tags: <epub><validation>
Title: The value following "version" in the XML declaration must be a quoted string
UserDisplayName: Janis Friesler
ThreadText: # The value following "version" in the XML declaration must be a quoted string
  
  (Asked by: username_0 on 2015-04-16)
  
  The xml string is the same on all the pages (.xhtml files)
  Here is an example:
  
  ```
  <?xml version="1.0" encoding="UTF-8" standalone="no"?>
  <!DOCTYPE html>
  <html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops">   
  
  ```
  
  I appreciate the help!
  
  **Tags:** epub, validation
  
  > **Comments:**
  > **username_1**: Does the error tell you exactly which file? The package.opf file is also an xml file, which may be missing the required quotation marks.  
  > **username_2**: I don't understand. Do you have a question, or is this a piece of advice?  
  > **username_0**: It is a question.  It does tell me the file.  /OEBPS/j83643-Flower-Fairy_-epubBody-26.xhtml(1,15): The value following "version" in the XML declaration must be a quoted string.  
  > **username_0**: Sorry I didn't put the whole message here.  
  > **username_3**: @username_0 if the below doesn't answer your question do you mind making an [edit] to your question so I make a better answer.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2015-04-21. Score: 1
  
  There doesn't appear to be an issue with the code after I tested it in a dummy ePub with ePubcheck 3.0. Since you haven't mentioned how the ePub was created I would trouble shoot by:
  
  * Creating a new XHTML file and re-doing the contents of the old XHTML file in it to make sure there isn't any issues with the file or if the file is corrupted.
  * Check to make sure your closing tag is proper or the document ends with `</html>`. This can be tested by opening the XHTML file in a browser such as Chrome and you might get a code error in red at the top.
  * Sometimes empty lines after `</html>` can cause a validation issue with ePubcheck so make sure to remove them.
  * If this was created in an application like Sublime or BBEdit you can always validate the XHTML.
  
  
  ---
  
  