error parsing genre.xml

[dulsin]

I have had genres working on my library for months but now I would like to customize my genres. After editing the default genre file the YAMJ will not parse the file any longer.

All I did was delete the lines for War and western and add a Film-Noir under Thriller. here it the text.

If it is not the code then it is a bad character but I can not see it.

Code:

<!--                                                                                   -->
<!-- Genre elements contains the relation between some sub-genres and a master genre   -->
<!--                                                                                   -->
<!-- Example of usage for internationalization (Comédie is French for Comedy)          -->
<!--  <genre name="Comédie">                                                           -->
<!--    <subgenre>Comedy</subgenre>                                                    -->
<!--  </genre>                                                                         -->

<genres>
  <genre name="Action">
    <subgenre>Adventure</subgenre>
    <subgenre>Sport</subgenre>
    <subgenre>Guerre</subgenre>
    <subgenre>Aventure</subgenre>
    <subgenre>Action and Adventure</subgenre>
  </genre>
  <genre name="Drama">
    <subgenre>Biography</subgenre>
    <subgenre>Romance</subgenre>
    <subgenre>History</subgenre>
    <subgenre>Crime</subgenre>
  </genre>
  <genre name="Thriller">
    <subgenre>Horror</subgenre>
    <subgenre>Mystery</subgenre>
    <subgenre>Film-Noir</subgenre>
  </genre>
  <genre name="Other">
    <subgenre>Short</subgenre>
    <subgenre>Music</subgenre>
    <subgenre>Musical</subgenre>
  </genre>
  <genre name="Sci-Fi">
    <subgenre>Science Fiction</subgenre>
    <subgenre>Science-Fiction</subgenre>
  </genre>
</genres>

[accident]

delete the lines that start with <!--

There is a unicode character in the text and if your texteditor can't handle utf-8 it's breaking the file.

A trick with xml files, is open them in your browser. they will tell you exactly where it's broken or use a text editor that can test them. In this case nothing appeared in the browser indicating a problem before the xml started in the comments.

[dulsin]

I will know tomorrow when the script finishes but it looks like it was the double quotes. After doing a search and replace switching all double quotes for single quotes it seems to be working.

[dulsin]

That was it.

Swapping out double quotes for single quotes and everything is fine.