It always was one of the aims of OpenGuides for the
software to be
everywhere on the globe. We havent gotten round to most of this yet,
as the main protagonists have full time jobs. Patches are welcome
Hehehe, I *knew* that would be said :) Well, I'm starting to get bettar at
perl programming, but by no means I'm a great programmer.. I could try,
I don't see why you couldn't install a Spanish
OpenGuides site. You will
to translate the templates. If you do this, please consider submitting
translated templates to CPAN (suggested name space OpenGuides::ES).
There might be some other issues with character sets,
Search::InvertedIndex, but I think that these would only be minor.
What overwhelms me a little is the amount of libraries I have to deal with,
and none of them are apt-gettable!!! :)
Having a multilingual site is a different ball game. I
don't know if
I don't know how you would maintain the translated wiki text in parallel
well, it is done in wikipedia. In fact I've been trying mediawiki this days
in parallel with openguides (in fact, travelwiki uses it), and I have to
say it is impressive, but it is too big for a wiki and it is not easily
customizable, nor good documented. Features i liked the most of it:
interkwiki linking, talk, watching pages, user can logon with password (but
not forced to do so).
In many ways, the categories and locales are the whole
Granted, they can be done as a "hack" on other wikis - this is the
of the London OpenGuide, which started out as "Grubstreet" using the
I see... but, the point is, I can put Location_BuenosAires or Category_Bars
at the end of the page (like c2 does) and then use search referring pages,
and it is almos the same. Since locales in openguides doesn't show all
pages in the locale by default.
The rest of
metadata doesn't seem to be used except to be shown in the
page (the coordinates system can't be used,
since i'm outside the uk).
We're working on that - coordinates. (/me needs to pull finger out).
uh.. I don't know what to pull a finger out is... my crappy english :)
Have you looked at the RDF syndication (format=RDF)
option for each
This enables other websites to get hold of the metadata. See
for an example of this.
well, I'd never given any look at rdf and syndication :)
I'm looking at it right now... But i don't see any metadata used at all,
just a changelog.. Sorry, but I don't know anything about rdf :)
You say it is too slow. We have not had any recent
on the existing sites. If you can give an example of this slowness,
please let us know.
Click on my draft site :) The computer is a k6-500 and it is very slow
there, i think compilation times are killing it...
Granted high volume sites benefit hugely from
mod_perl. But, how many
second do you imagine getting?
no, it is not what worries me, just waiting 7 seconds for each page (at
localhost) seems a bit too much for me :)
In terms of running on mod_perl, possibly the
be ported to run on Apache::Session - I'm not an expert on this, perhaps
on the list can answer this one.
Well, I have a experience porting a small application to mod_perl in my day
job and it hasn't been easy :(
But I think the task should not be to port the engine but the front end. If
you already have all the logic in a .pm well done, the porting is easy, you
just change the way the underlying modules are called...
Good questions all round. Welcome to OpenGuides.
I want to say that if I'm saying all these things is because I like
openguides, and maybe my worries are because I'm just missing :)