The LO homepage (https://www.libreoffice.org/) has a section near the bottom of the page entitled "News at TDF Blog". This section appears to include excerpts from TDF Blog entries.
The entries are showing up on the libreoffice.org page with escaped HTML tags and character entities. For example:
The following is an open letter The Document Foundation has sent to the City of Freiburg, Germany, as a statement regarding the current discussion about Freiburg’s IT strategy. The letter in its original format is available at <a href="http://wiki.documentfoundation.org/File" target="_blank">wiki.documentfoundation.org/File</a>:OffenerBriefFreiburg.pdf At the same time, The Document
Berlin & Barcelona, November 7, 2012 – The Document Foundation announces the first group
I assume that something in the blog-to-feed import chain is applying some kind of html-escaping filter (perhaps for security reasons).
Either the HTML should be stripped entirely, or the HTML should be preserved in its original state so that it can be rendered as it appears on the TDF Blog.
Thank you for your bug report!
REPRODUCIBLE easily by browsing the TDF site; I will attach a screenshot showing the current state, including the escaped HTML tags cited by Qubit.
This bug is more important than one may think first; some people (including me ;-) may regard such escaped (visible) HTML on a website as a sign that the company or organization which ows that website is unprofessional ...
Created attachment 70411 [details]
Screenshot of www.libreoffice.org, section "News at TDF blog", 2012-11-22
Hi, could I please get a status update on this bug?
I really like LO, and I really want to promote LO, but it's hard for me to bill LO as a serious piece of software and promote it to business professionals when the front page doesn't reflect the high quality of the software product.
We're coming up on 2 weeks that the front page has been looking sub-par.
For comparison, here's the front page for MS-Office:
do you know (I don’t, sorry) who exactly is responsible for the technical side of the LibO website and can fix this bug? Please CC him/her about this bug. Qubit is right that this little bug should be fixed fast, because it makes the LibO website look unprofessional, or even embarrassing ...
Thank you very much!
Hello to all,
I am actually new here. But I took a glance at it and I downloaded the page to correct it. The <a> tags were somehow corrupted. I think you need something like the following html code...Isn't it right? I do not know how to commit etc...
<p>The following is an open letter The Document Foundation has sent to the City of Freiburg, Germany, as a statement regarding the current discussion about Freiburg&#8217;s IT strategy. The letter in its original format is available at <a href="http://wiki.documentfoundation.org/File" target="_blank">wiki.documentfoundation.org/File<>OffenerBriefFreiburg.pdf</a> At the same time, The Document Foundation has signed the open letter of the Open Source Business [...]</p>
Welcome and thank you for your attempt to help!
> I am actually new here. But I took a glance at it and I downloaded the page
> to correct it. The <a> tags were somehow corrupted. I think you need
> something like the following html code...
You are completely right that this would fix the problem for now. But I fear that the issue is more difficult.
This part of the LO hompage, “News at TDF Blog”, is generated automatically by some script (or however this may be called ;-) from the contents of
IMHO the script, while abbreviating the articles from the blog to short summaries, “damages” some HTML tags and character entities by converting the HTML markup into literal text ...
So what is necessary is to fix that script, and I fear this is a bit more difficult.
@ Florian Effenberger:
this little bug about the front/home page of www.libreoffice.org/ is embarrassing, because it makes the whole page look unprofessional.
And that is bad ...
Do you know who is responsible for the website, especially for the script which generates the contents of the “News at TDF Blog” section, and therefore should be told about this bug? I did not succeed in finding any information about that on the website (which is, BTW, probably yet another bug ;-).
Thank you very much for your help!
Cloph, can you have a look at this one?
Twitter has changed/closed its API, Cloph just told me, which is why it is not working. We need to see if there is a workaround, otherwise removing the Twitter column is an option until someone can provide code that works.
For the blog posts, all the errors so far were result of badly-formatted blog posts, I hear.
Migrating Whiteboard tags to Keywords: (ProposedEasyHack -> needsDevEval, TopicWeb)