After 2 years, I looked at my JPS article again, and noted the code layout is totally broken, all indenting is gone, also in the "page source" of the web page displayed by my browser. Since I used Python, where blocks are denoted by indenting, this makes the code unreadable.

The text also looks a bit weirdly formatted here and there, so more white-space may be missing. Last but not least, in the horizontal/vertical scan explanation, the reference to the ]B[ picture is missing, in my page source it is now "The <i><span style="font-weight:bold;"></i> picture is the same." in stead of "The <i>]B[</i> picture is the same." (I think it was).

Link to the article:

Note the ]B[ has brackets in the wrong way, but the editor doesn't allow it written as it should be, it modifies it to bold text

Thanks!!

I might still have the code, but it's sad to see this kind of things happening. I don't know when this happened, but likely my article isn't the only one hit.

Apparently the formatting isn't very robust against changes that are being done to the articles. As a suggestion, perhaps find some better format, consider that to be unmodifiable source, and generate web-pages from it?

Even if the formatting gets messed up, you'd still have the source, so you can fix the generator, and re-generate a fixed version.

3 hours ago, khawk said:

Without getting into too much detail, basically the articles and other content have gone through several major revisions over the lifetime of GameDev.net where depending on the time period the formatting may have made certain assumptions different than the previous formatting.

I guessed as much, which I why I was thinking it might be useful to standardize on some well-defined format as 'original source', and always convert from that to whatever format the site needs today.

The downside is that either authors would need to write in that format, or a conversion tool from todays format would be needed. The latter would be necessary as well for all the existing articles.

Perhaps a better solution is to store the generated html page. When converting to a new format, rendering it would need to produce that html page again, so you have a check whether the conversion process is correct.

Finally, thanks for all your work. So much work goes on behind the scenes, we are not even aware of!