On 02/09/2013 Marcus (OOo) wrote:
Right, at the moment only the following has to be done to change the
content of the "other.html":
- change the version number
- change the languages - and if needed its order
- change the platforms - and if needed its order
But this wouldn't change. I managed to express myself very badly.
In practice, what I propose is this:
This is "other_js.html" (a copy of your current "other.html")
http://people.apache.org/~pescetti/tmp/2013-09-otherhtml/other_js.html
This is the new "other.html"
http://people.apache.org/~pescetti/tmp/2013-09-otherhtml/other.html
See the difference? No? Good. "other.html" is obtained by opening in
Firebug other_js.html and copy/pasting the table from there (from the
document's DOM, not the HTML source that would have the write_table()
function there). A few seconds' work.
other_js.html is an internal convenience page, never shown to users or
linked: it is a "generator".
So the workflow is unchanged, with the addition of a step that takes a
few seconds: load "other_js.html" in Firefox and with Firebug copy the
table to "other.html". (you can use dozens of tools and techniques, I
just picked one; if you want to script it you can use phantomjs or
whatever, but everything is overkill for this).
Then other.html will work for everybody and we can avoid dealing with
broken browsers so long as they render HTML tables properly.
I didn't clean up the <noscript> and other parts of other.html that
would then be removed, but would be a simple one-time edit.
All concerns about Google visibility are addressed too: actually, the
new other.html would be more visibile to search engines that in general
have difficulties in parsing JavaScript.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
