In article <[EMAIL PROTECTED]>, Simon Voortman <[EMAIL PROTECTED]> wrote:
> Michael Drake suggested I asked here which parts of the new site are > stable and can be translated. I've taken a look at the site now and I think that the following pages are unlikely to change: Homepage - http://test.netsurf-browser.org/ I think all of that is safe for translation, except for the "Latest news" section, which is currently made up. I'm not sure how we'll handle news. Maybe it will be added to the page dynamically in the future and therefore not so straightforward to translate. Maybe if a section is in English we should say "Latest news (English)" (translated into the other language), if it can't be translated. Documentation - http://test.netsurf-browser.org/documentation/ I think all of this section is ready to be translated, except for the User Guide. Contact - http://test.netsurf-browser.org/contact/ Can be translated. The "About NetSurf" and "Downloads" sections are likely to change, so I wouldn't work on them yet. The other parts of the site are still being written. As for actual translations, it would be good to have a central place where we can check how up-to-date each version is. Perhaps we could have a page in the contributor/developer area of the new site that contains a table of the latest updates to the transactions. Something like: Page | .en (reference) | .de | .nl --------------------+-----------------+-------------+------------ / | 04 Oct 2007 | 20 Sep 2007 | 04 Oct 2007 /about/ | 15 Mar 2006 | 15 Mar 2006 | 15 Mar 2006 /about/news | 30 Nov 2007 | * | * /about/screenshots | 11 Jun 2007 | 11 Jun 2007 | 18 May 2007 * English only The entries for .de, .fr, .nl and any others can be coloured red if they are not as new as the .en one. That should make it easier to see what the status of the translations is. We could have similar for the Messages and Templates files. Do you think that would help? On the translated pages, I think we should keep the same markup on all versions. So the tags should be identical between .en and .fr pages, for example. The only difference should be the content, alt text and things like that. I've seen that there are some differences, such as the red and green text on some .nl pages, like: http://www.netsurf-browser.org/info.nl I'm not sure what the red / green means but I think it would be best if we could avoid it and put the information elsewhere.. > Also, it would be handy to have a way to view the (old) > web-documentation while translating it. At the moment the */css file > isn't loading, so it's not displaying like the website. I can setup a > local webserver for that. Are there any special settings to be made? > (For example, to make the switch between the various languages work?) The files we used to do this with Apache are still in SVN. I'm not sure if it will work with WebJames. It used .htaccess files and a 406.php error page. I'm not really sure how that worked. http://source.netsurf-browser.org/trunk/netsurfweb/406.php?view=markup http://source.netsurf-browser.org/trunk/netsurfweb/.htaccess?&view=markup Normally, when I am working on the web site locally, I change the CSS file URL. So I change the "/netsurf.css" in <link rel="stylesheet" type="text/css" href="/netsurf.css"> to "netsurf.css" or "../netsurf.css" or whatever is required to load it. Once I've finished editing the page I change it back to "/netsurf.css". Best regards, Michael -- Michael Drake (tlsa) http://www.netsurf-browser.org/
