Hi Thomas,
On Fri, Mar 7, 2014 at 6:46 PM, Thomas Hackert <thackert@nexgo.de> wrote:
Hello Christian, *,
On Freitag, 7. März 2014 18:25 Christian Lohmaier wrote:
On Fri, Mar 7, 2014 at 5:58 PM, Thomas Hackert <thackert@nexgo.de>
That is because the feed created by wordpress contains invalid
characters:
If you get http://blog.documentfoundation.org/feed/ you see that
on one occurence of the Support The Document Foundation has
control characters before the "S" (between "<strong>" and S)
errrr ... Do you mean in the HTML text of the feed?
yes - although it is not HTML, but xml ;-)
I only found a
couple of
<quote>
<p><strong>Support The Document Foundation</strong></p>
</quote>
but none with additional "control characters" ... :(
That means whatever program you're using to view it just ignores
them/doesn't display them. As they have no visible representation,
this is somewhat expected...
http://validator.w3.org/check?uri=http%3A%2F%2Fblog.documentfoundation.org%2Ffeed%2F
should make it more clear.
I cc Florian, he should be able to edit the blog to fix this.
ciao
Christian
--
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.