On 05.02.2012 15:04, Richard Stallman wrote:
> Please insert a list like this: > > <ul> > <li> On MS Windows, install<a ...>Evince</a>. > <li> On MacOS, install<a ...>Vindaloo</a>. > <li> On GNU/Linux and other free operating systems, > you probably have a free PDF player installed already. > Try displaying a PDF file and see! If that doesn't > work, you can install one; see<a ...>advice</a>. > </ul> Something similar was planned, but I think right now, it is really best to do all the changes in one go, so that we don't duplicate efforts, trigger useless translations et cetera.
The changes I've suggested are easy to do; if I were maintaining this page I would have done it in the time I spent writing to you about it.
You don't need to update the translations before you release a modified English page. After all, the existing page is not false. The changes we're talking about are improvements.
There is no pressing need to simultaneously improve the page in all languages. It is fine to improve each language when and as someone can do the work. Some improvement is better than no improvement, after all.
Well, we would rather do it with other changes, since I am mostly doing the planning right now, but I don't do the actual hacking on the site, and we also have people more skilled in layout and design etc. then myself.
I have done a mockup and attached it. Basically it boils down to having 5 sub-site: 1. Recommended: Showing one recommended reader and the short paragraph proposed by you. I would also like to recommend a browser plugin in addition to the desktop reader (if these are not included in the same package). 2. Overview: An overview over all Free readers on all platforms and browsers. It might be best, to make different paragraphs for all platforms and put a table in each, depending on how many we got. 3. Graphics: the same as the current one. 4. About PDF: like the current "Open Standards" Page but with more information on how well each is supported by Free Software 5. About this Site: the current "About" page.
Should pdf.js become useable we can add a site for that under "For Webmasters", so that webmasters may offer Free Software rendering in the browser. If we do we should also inform about the SaaS issue there and ask those webmasters to explicity inform their users, that the PDF-rendering is achieved by Free Software Javascript running in their browser.