On Fri, 7 Feb 2003, Axel Boldt wrote: Several thoughts: * Rather than a static HTML tree (which will grow too big for a CD without compression sooner or later), store compressed and indexed wikitext, and distribute it with a dedicated reader, which will have a search mechanism built in to it. (Related to or the same as a dedicated writer... see discussions on meta) * A Java hack * Write a helper program to do searching, include compiled versions for major platforms. (But how to integrate with browser?) -- brion vibber (brion @ pobox.com)

On Fri, 7 Feb 2003, Pieter Suurmond wrote: ... This is planned; see http://meta.wikipedia.org/wiki/Machine-friendly_wiki_interface ;) Another reason in favor of a 'smart' program that can download updates and seamlessly jump between the versions on disc and the new updated versions. -- brion vibber (brion @ pobox.com)

Magnus Manske wrote: Sorry but I cannot find any 'database dump' on http://www.wikipedia.org/ or on meta. Pieter

Pieter Suurmond wrote: Try "Database download" on www.wikipedia.org, which leads to http://www.wikipedia.org/wiki/Wikipedia%3ADatabase_download The direct link to the "cur" table dump is http://www.wikipedia.org/tarballs/cur_table.sql.bz2 Magnus

On Fri, Feb 07, 2003 at 11:14:03AM -0800, Brion Vibber wrote: Distributing any code to be run on client machine is really bad idea. A bit of Javascript to do searching in some index is about as much as can be reasonably done. Distributing renderer is really really bad idea.

On Fri, Feb 07, 2003 at 01:22:01PM -0800, Jason Richey wrote: Because: * it's not safe for user * there's no chance it will run on every machine people would want to see wikipedia on. Is this good enough ?

Tomasz Wegrzanowski wrote: Sorry, I'm afraid not. If wiki-syntax and -semantics are clear, it must be possible to render it on ANY machine. Why not?? (this is what OPEN SOURCE is about) The only thing that matters is the wikisource (which I can now download, which is really great!!), I 'll find my own alternative way(s) to render it :-). Am I not free? One could use JavaScript, Java, C++ in combination with wxWindows, or whatever... Let us develop as may different viewers and renderers for all different machines, operating-systems, etc... But first (I'm afraid) Wikisyntax needs to be finished/completed (a matter of specification, not of implementation). Sorry, in my opinion "Distributing renderer" is a really really very good idea (it enables me to read articles at times that the wikipedia-server is very slow or down). Pieter

On 7 Feb 2003 at 14:49, Axel Boldt wrote: What about starting with Amaya? http://www.w3.org/Amaya/ Disclaimer: I'm not a member of W3C community neither of Amaya Development team, and this is not an ad. I've downloaded yesterday fresh (Feb 03) version 7.2 and the stupid smile on my face is getting bigger and bigger with every minute :) Of course using Amaya won't be a solution for searching problem but Amaya: * supports MathML rendering (so one only needs to transform our TeX <math> syntax into MathML and Amaya will do the rest) * supports SVG (anybody still thinking about future support of SVG in WP?) * is a browser/editor - you have to click only one icon to change the mode (so if one smartly design the rest, ie. handling "source code" of articles, like transforming it to XHTML and back, then every person could edit the page even without knowing wikisyntax or Wikipedia software, Amaya is WYSIWYG) * support for annotations which can be held in local file on posted to a server (just imagine Wikipedia as a server for such annotations! If one browse off-line and see an error then he/she adds an annotation and saves it locally and when he/she has the access to the Net posts to the Wikipedia and Wikipedians correct) Disadvantages, that I've found out after one day of playing with Amaya: no elaborated HTML, no scripts and a bit harsh interface but Amaya is free and open source project. User:Youandme

On Sat, Feb 08, 2003 at 12:26:28AM +0100, Youandme wrote: I checked that, but what it renders look horrible. It completely fails to do proper vertical alignment. For example \int \int_p x looks like: / / | | | | x | / / p With second integral sign smaller than first, and their centers at different heights. Another example: it doesn't place operators on the same height as fraction line.

Erik Moeller wrote: Ah nice (I did see a lot of tiny httpd's lately but this one is new to me). Indeed, must be possible to do it all via normal CGI-queries. Write upon 'fnord' or grab source and add wiki-features to it... (?) Just writing CGI seems best because that is standardised and would enable migration to apache or some other server... there are probably many servers out there that can do the job... I think on most Operating Systems nowadays some kind of 'personal webserver' is already installed... ? (I also object to Java, it's in the hands of Sun and Microsoft, it seems) Greetings / thanks for the link, Pieter