Image quality is poor on _every_ blog pre-Verint

Hi shabaz,

Thanks for creating a thread on this as it makes it easier to track the issue. I have not forgotten when you reported it previously ( RE: Unusable images when downloaded ) and we have an internal ticket with the development and ops team regarding this. I raised it on the 5th of December, and the initial feedback has been that it's a time-intensive problem to solve, and the pushback has been "Well no-one's noticed for 2 years, is it a problem?" which is not something that you want to hear.

I went through and identified a pattern with the blog and how it's affected, particularly the xilinx blog you cite here. My concern is that this has likely affected more content on the site, but I have no way of knowing how much content is affected by this.

The problem appears to have been caused by the wrong path used when transferring content from Jive to Verint, on Jive the path /JiveServlet/downloadImage/ was used to transfer the files to Verint, and this was the 'preview' URL which is an optimised and lower quality image, rather than the 'JiveServlet/showImage/' path which contained the original, higher resolution image. Updating potentially so much content has implications if we're editing the content directly, and it has other resource implications behind the scenes, but the decision is not in my hands.

It would probably help if we could identify how much content is affected by this and I have asked the team to see if they can at least do that initial diagnosis if there are any links you can identify and provide where you're seeing this beyond the Xilinx blog you've provided that would be helpful. I can likely update/fix at least a small number of blogs which show this problem by manually updating them.

I'll also push for a re-review from the team.

Hi Christopher,

The site was broken for a year, and I'm sure people certainly did notice the image problems but, frankly, gave up trying to read articles rather than reporting them, because they couldn't use the site very well at all back then.

Secondly, there's only going to be a small percentage of people who will register, then find where to report a problem, and then supply the information.

Here's an example from Jan Cumps  blog  Learning Xilinx Zynq: use AXI with a VHDL example in Pynq  

An example from another blog:  Learning Xilinx Zynq: Interrupt ARM from FPGA fabric  

That one is so bad, if you click on the image, it actually reduces the quality further, and zooms out:

Yet another one still using Jan Cumps  blogs as an example:  Programmable Electronic Load - Analog Controller and Driver Board 

Here's a RoadTest review from Fred27  , same issue: /products/roadtest/rv/roadtest_reviews/513/eclypse_z7_zynq-7000 

The problem is most painful on screenshots from application software, because they tend to require the detail so that people can see where to click and what output to expect. But it's negatively impacted circuit diagrams too, and these are all fundamental. The times you need help will be with complex software or circuits, and that's when the impact of the problem will be most experienced.

This has happened with other websites (e.g. Electronics Design is a famous example) where on various upgrades, they have lost detail, to the point that some articles such as this one by Bob Pease refer to non-existant diagrams.

It's not making best use of the assets if the low-res versions are being supplied, and high-res are only available on a case-by-case basis. For what it's worth, I think it's time to push this to a high priority, over other features. The tutorial blogs feature I think could have been postponed if this one had been prioritised. Anyway, it's just an opinion but someone has to say it.

It is frustrating. Thanks for the additional links.