On Tue, Mar 30, 2010 at 1:39 PM, Gijs de Rooy wrote:
> There is an even simpler solution. At the wiki, we can redirect
> articles. Eg. "737-300" and "733"
> redirect to "Boeing 737-300". So for an automated script, you could easily
> create links like
> wiki.flightgear.org/inxed.php/737-300, where the page title is the
> aircraft's root (data/Aircraft/...)
> folder or perhaps the <areo/> value.. Those links will then be redirected
> to the corresponding (full
> title) article about the aircraft.
>
> If you do the script part, I'm willing to arrange the redirects ;)
>
Ok, so if we come up with a standardized naming scheme, can we blindly
create links for every aircraft on the download page? What do we do with
aircraft that don't have a specific wiki link? Would we route those to some
"generic" aircraft information page? Will we have problems with name
contention or clashes if we start generating links to 100's of
yet-to-be-created wiki pages automatically?
I can do it, I just don't want to create a bigger mess than we anticipated
...
Regards,
Curt.
--
Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
