Finden 
Community 
Hilfe 
Produzieren 
MyPodster
Dieser Artikel wurde automatisch erzeugt und wird auch automatisch wieder ausgelesen. Es ist deshalb wichtig, dass nur der Inhalt der gelben Code-Boxen verändert wird.
Es handelt sich dabei um eine Fehlermeldung des Feed-Validators, die eventuell noch ins Deutsche übersetzt werden muss. Wenn du kannst, hilf mit!
Es handelt sich dabei um eine Fehlermeldung des Feed-Validators, die eventuell noch ins Deutsche übersetzt werden muss. Wenn du kannst, hilf mit!
Status dieser Fehlermeldung: Noch nicht übersetzt
Meldung
<p>UnicodeError: decoding error, invalid data</p>
Erklärung
<p>Your feed contains an invalid character.</p>
Lösung
<p>A common cause of this error is having a high-bit character (such as a curly quote or curly apostrophe) in your RSS feed. This can happen if you copy-and-paste a quote from another page that contains curly quotes. For maximum compatibility with readers, you should remove the invalid character or use a numeric entity equivalent.</p>
<p>You can also try changing your character encoding to a more liberal encoding. For example, if you have this at the top of your feed:</p>
<p><samp><?xml version="1.0" encoding="utf-8"?></samp></p>
<p>Try changing it to this:</p>
<p><samp><?xml version="1.0" encoding="iso-8859-1"?></samp></p>
<p>This can be a difficult error to diagnose, because the validator can not give you the exact location of the error. (This is due to a limitation of our parsing library; sorry, we tried very hard to work around it!) For example, if the validator says the error occurred at the end of a <code>description</code> element, the actual invalid character could be anywhere within the description.</p>
<p>You can also try changing your character encoding to a more liberal encoding. For example, if you have this at the top of your feed:</p>
<p><samp><?xml version="1.0" encoding="utf-8"?></samp></p>
<p>Try changing it to this:</p>
<p><samp><?xml version="1.0" encoding="iso-8859-1"?></samp></p>
<p>This can be a difficult error to diagnose, because the validator can not give you the exact location of the error. (This is due to a limitation of our parsing library; sorry, we tried very hard to work around it!) For example, if the validator says the error occurred at the end of a <code>description</code> element, the actual invalid character could be anywhere within the description.</p>