rest2web-develop Mailing List for rest2web (Page 6)
Brought to you by:
mjfoord
You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(74) |
Aug
(71) |
Sep
(6) |
Oct
(6) |
Nov
(3) |
Dec
(7) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(8) |
Feb
(17) |
Mar
(16) |
Apr
(48) |
May
(9) |
Jun
|
Jul
(7) |
Aug
(93) |
Sep
(18) |
Oct
(17) |
Nov
(22) |
Dec
(11) |
2007 |
Jan
(11) |
Feb
|
Mar
(61) |
Apr
(14) |
May
(3) |
Jun
|
Jul
(13) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(6) |
2008 |
Jan
|
Feb
|
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(7) |
Oct
(2) |
Nov
(7) |
Dec
(7) |
2009 |
Jan
(2) |
Feb
|
Mar
(4) |
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2010 |
Jan
(1) |
Feb
(1) |
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
|
2011 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(14) |
Sep
(2) |
Oct
(1) |
Nov
(3) |
Dec
|
2012 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
(5) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(2) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
2016 |
Jan
(2) |
Feb
(5) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <ow...@bu...> - 2007-07-10 13:03:13
|
Your message dated Tue, 10 Jul 2007 12:47:05 +0000 with message-id <E1I...@ri...> and subject line Bug#399359: fixed in rest2web 0.5.2~alpha+svn-r248-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) |
From: <ow...@bu...> - 2007-07-10 12:31:04
|
Processing commands for co...@bu...: > # Automatically generated email from bts, devscripts version 2.10.6 > notfixed 399359 0.5.0.svn-r227-1 Bug#399359: rest2web: compile errors with python 2.5 Bug marked as not fixed in version 0.5.0.svn-r227-1. > reopen 399359 Bug#399359: rest2web: compile errors with python 2.5 Bug reopened, originator not changed. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) |
From: martin f k. <ma...@ma...> - 2007-07-10 12:29:00
|
also sprach martin f krafft <ma...@ma...> [2007.07.10.1419 +0200]: > also sprach Mickey Hadick <mdh...@fa...> [2007.07.10.1311 +0200]: > > I'm setting up rest2web on an XUBUNTU laptop, and there seems to be a > > known bug with the version of rest2web available in the aptitude > > repository. The good news is that I think docutils was successful, so I > > might be able to grab the tar and finish it manually, but we may want to > > get the bug corrected. I'm a newbie at the specifics of UBUNTU > > installs, and my googling hasn't turned up a confidence inspiring > > instruction set. Any ideas? >=20 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D399359 >=20 > I'll make a new upload soon. You'll have to file a bug report with > Ubuntu to get them to update their version or install the Debian > package. http://debian.madduck.net/repo/dists/unstable/main/binary-all/web/rest2web_= 0.5.2~alpha+svn-r248-1_all.deb --=20 martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck =20 spamtraps: mad...@ma... =20 "it is the mark of an educated mind to be able to entertain a thought without accepting it." -- aristoteles |
From: <ow...@bu...> - 2007-07-10 12:22:30
|
Your message dated Tue, 10 Jul 2007 14:10:27 +0200 with message-id <200...@pi...> and subject line (no subject) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) |
From: martin f k. <ma...@ma...> - 2007-07-10 12:20:25
|
also sprach Mickey Hadick <mdh...@fa...> [2007.07.10.1311 +0200]: > I'm setting up rest2web on an XUBUNTU laptop, and there seems to be a > known bug with the version of rest2web available in the aptitude > repository. The good news is that I think docutils was successful, so I > might be able to grab the tar and finish it manually, but we may want to > get the bug corrected. I'm a newbie at the specifics of UBUNTU > installs, and my googling hasn't turned up a confidence inspiring > instruction set. Any ideas? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D399359 I'll make a new upload soon. You'll have to file a bug report with Ubuntu to get them to update their version or install the Debian package. --=20 martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck =20 spamtraps: mad...@ma... =20 in seattle, washington, it is illegal to carry a concealed weapon that is over six feet in length. |
From: Mickey H. <mdh...@fa...> - 2007-07-10 11:11:31
|
I'm setting up rest2web on an XUBUNTU laptop, and there seems to be a known bug with the version of rest2web available in the aptitude repository. The good news is that I think docutils was successful, so I might be able to grab the tar and finish it manually, but we may want to get the bug corrected. I'm a newbie at the specifics of UBUNTU installs, and my googling hasn't turned up a confidence inspiring instruction set. Any ideas? Here is what was reported during the "sudo apt-get install rest2web": Setting up rest2web (0.5.0.svn-r227-1) ... Compiling /var/lib/python-support/python2.5/rest2web/pythonutils/pathutils.py ... File "/var/lib/python-support/python2.5/rest2web/pythonutils/pathutils.py", line 23 from __future__ import generators SyntaxError: from __future__ imports must occur at the beginning of the file --Mick (Mi...@Ha...) |
From: kib2 <ki...@fr...> - 2007-05-20 21:25:42
|
Michael Foord a écrit : > Hello Kib2, > > There is (currently...) no support inside rest2web for this. You would > need to add the directives code to 'restutils.py' : > > http://svn.rest2web.python-hosting.com/trunk/rest2web/restutils.py > > HTH > > Fuzzyman > http://www.voidspace.org.uk/python/articles.shtml > > > > Thanks Michael, I will try to add it. I really like your articles on your blog, very nice job. Cheers, ------------------------------------------------ Kib² : ------------------------------------------------ Blog : http://kib2.webfactional.com/ Project : http://kib2.free.fr/geoPyX/geoPyX.html |
From: Michael F. <fuz...@vo...> - 2007-05-20 20:58:20
|
kib2 wrote: > Hi, > > I'm new with rest2web and wanted to know if I could use my own > directives inside it. > In particular, the pygments one given here > http://pygments.org/docs/rstdirective/ > to highlight source code inside my pages. > Hello Kib2, There is (currently...) no support inside rest2web for this. You would need to add the directives code to 'restutils.py' : http://svn.rest2web.python-hosting.com/trunk/rest2web/restutils.py HTH Fuzzyman http://www.voidspace.org.uk/python/articles.shtml > Thanks a lot, > > ------------------------------------------------ > Kib² : > ------------------------------------------------ > Blog : http://kib2.webfactional.com/ > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Rest2web-develop mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/rest2web-develop > > |
From: kib2 <ki...@fr...> - 2007-05-20 20:48:51
|
Hi, I'm new with rest2web and wanted to know if I could use my own directives inside it. In particular, the pygments one given here http://pygments.org/docs/rstdirective/ to highlight source code inside my pages. Thanks a lot, ------------------------------------------------ Kib² : ------------------------------------------------ Blog : http://kib2.webfactional.com/ |
From: Michael F. <fuz...@vo...> - 2007-04-27 17:11:23
|
Chris G wrote: > Using r2w.py is it possible to put some rst2html.py directives > anywhere to change some of the HTML generation? > > In particular I'd like to use the following option:- > > --initial-header-level=<level> > > You can set this per file in the restindex. See the 'initialheaderlevel' keyword: http://www.voidspace.org.uk/python/rest2web/restindex.html#the-keywords Unfortunately I *don't* think this is inherited if you set it in indexpages. You can set global docutils settings in the default config file in your dcoutils package. I have a feeling that if there is a docutils conf file in the current directory when you run rest2web, this will be picked up. If this doesn't work, report back and I will add a 'feature request' for being able to specify a docutils config file to use with a site. Fuzzyman http://www.voidspace.org.uk/python/articles.shtml |
From: Chris G <cl...@is...> - 2007-04-27 15:45:14
|
Using r2w.py is it possible to put some rst2html.py directives anywhere to change some of the HTML generation? In particular I'd like to use the following option:- --initial-header-level=<level> -- Chris Green |
From: Chris G <cl...@is...> - 2007-04-08 09:08:14
|
On Thu, Apr 05, 2007 at 10:42:05PM +0100, Michael Foord wrote: > Chris G wrote: > > Would it be possible to have default values for a couple of the items > > in the sections:pages:page dictionary please? > > > > If you use --force and a page has no header of any sort then there is > > no link-title or crumb value for the page. Setting them to the file > > name by default would be useful. > > > > I suspect that setting the default restindex page-title might be an > > effective cure for this as well (you have a note in the documentation > > that this would be a good idea). > > > > This sounds like a reasonable request. I'll add it to the list of things > to do with rest2web. :-) > > Presumably the crumb should omit the file extension ? What about the > link-title ? > Yes, I guess they should both be without extension. However I very rarely have files with extensions anyway (it's the 'Unix' way). I have actually written a little pre-processor for r2w.py that creates temporary symbolic links of <filename>.txt for all files that return 'text' in the result in response to "file <filename>". A post-processor then removes all symbolic links which end in .txt afterwards. -- Chris Green |
From: Michael F. <ar...@vo...> - 2007-04-05 21:42:43
|
Chris G wrote: > Would it be possible to have default values for a couple of the items > in the sections:pages:page dictionary please? > > If you use --force and a page has no header of any sort then there is > no link-title or crumb value for the page. Setting them to the file > name by default would be useful. > > I suspect that setting the default restindex page-title might be an > effective cure for this as well (you have a note in the documentation > that this would be a good idea). > This sounds like a reasonable request. I'll add it to the list of things to do with rest2web. :-) Presumably the crumb should omit the file extension ? What about the link-title ? Fuzzyman http://www.voidspace.org.uk/index2.shtml |
From: Chris G <cl...@is...> - 2007-04-05 10:58:57
|
Would it be possible to have default values for a couple of the items in the sections:pages:page dictionary please? If you use --force and a page has no header of any sort then there is no link-title or crumb value for the page. Setting them to the file name by default would be useful. I suspect that setting the default restindex page-title might be an effective cure for this as well (you have a note in the documentation that this would be a good idea). -- Chris Green |
From: Gael V. <gae...@no...> - 2007-04-04 18:56:31
|
On Wed, Apr 04, 2007 at 04:46:21PM +0100, Michael Foord wrote: > Hello all, > Sorry for the very late response. I've just checked in the following > change to the sidebar function. :-) Sweet ! I have been overwhelmed with work and had totally forgotten about this. Gaël |
From: Michael F. <fuz...@vo...> - 2007-04-04 15:49:38
|
Hello all, Sorry for the very late response. I've just checked in the following change to the sidebar function. :-) Michael Gael Varoquaux wrote: > On Mon, Jan 01, 2007 at 11:47:28PM +0000, Michael Foord wrote: > >> So your patch just allows the passing in of a comparison function to the >> sidebar function. >> > > >> If a comparison function is passed in, it is used to sort the pages. >> > > Yes, simple, but useful. > > >> It sounds fine. Can you give me an example function I can put in the docs ? >> > > Well, how about this (adapted from the sidebar example): sorting by crumb > value, inverse order. > > .. raw:: html > > {+coloring} > > cmp_page = lambda page1, page2 : 2*(page1['crumb'] < page2['crumb'] ) - 1 > > for page in sidebar(indextree, cmp=cmp_page): > val = page['crumb'] > link = page['target'] > if page['title']: > print '<br /><strong><a href="%s">%s</a></strong>' \ > % (link, val) > else: > print '<br /><a href="%s">%s</a>' % (link, val) > > {-coloring} > > But this allows for much more powerful uses (like having a "date" > uservalue, and sorting by date). > > Cheers, > > Gaël > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Rest2web-develop mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/rest2web-develop > > |
From: Michael F. <ar...@vo...> - 2007-04-02 19:23:18
|
Chris G wrote: > On Mon, Apr 02, 2007 at 12:21:33AM +0100, Michael Foord wrote: > >> Chris G wrote: >> >>> When using the <* .... *> syntax to insert something into a rst page >>> what variables are available? >>> >>> I tried 'title' and was told that wasn't defined and I suppose that's >>> not unreasonable. Then I tried 'pagename' and that was undefined too >>> which doesn't seem right to me, surely the filename should be known. >>> >>> >> Looking at the code (call to 'render_well' in line 934 of >> restprocessor.py), only the uservalues are available at this point. >> >> What is your usecase for knowing the filename at this point ? (I only >> envisaged uservalues being used here - but it *could* be used for >> general templating.) >> >> Anyway - I note your feature request to add more values here - a strong >> use case might speed it up. :-) >> >> (By the way, this is a *slightly* obscure feature of rest2web - it is >> good to see it getting used. :-) >> >> > I want to use it in the default index.txt file so that I can put (for > example) the file name as the default section header. E.g. :- > > <* pagename *> > ====================== > > at the top of the default index.txt would give a reasonable default > heading and would also get into all the rest2web structures for use as > link names etc. Doing it in a raw:: html section would only create > the heading but not set any values. > Ok - that's a reasonable usecase. I'll try and implement it ASAP, but I can't promise when. :-) Michael |
From: Chris G <cl...@is...> - 2007-04-02 08:22:35
|
On Mon, Apr 02, 2007 at 12:21:33AM +0100, Michael Foord wrote: > Chris G wrote: > > When using the <* .... *> syntax to insert something into a rst page > > what variables are available? > > > > I tried 'title' and was told that wasn't defined and I suppose that's > > not unreasonable. Then I tried 'pagename' and that was undefined too > > which doesn't seem right to me, surely the filename should be known. > > > Looking at the code (call to 'render_well' in line 934 of > restprocessor.py), only the uservalues are available at this point. > > What is your usecase for knowing the filename at this point ? (I only > envisaged uservalues being used here - but it *could* be used for > general templating.) > > Anyway - I note your feature request to add more values here - a strong > use case might speed it up. :-) > > (By the way, this is a *slightly* obscure feature of rest2web - it is > good to see it getting used. :-) > I want to use it in the default index.txt file so that I can put (for example) the file name as the default section header. E.g. :- <* pagename *> ====================== at the top of the default index.txt would give a reasonable default heading and would also get into all the rest2web structures for use as link names etc. Doing it in a raw:: html section would only create the heading but not set any values. -- Chris Green |
From: Chris G <cl...@is...> - 2007-04-02 08:12:22
|
On Mon, Apr 02, 2007 at 12:27:27AM +0100, Michael Foord wrote: > > Just some ideas for kicking around, if I'm the only person thinking > > this way then never mind, I'll live with it as it is because it does > > so much in the sort of way I want. > > > > > > But what is to stop you doing this anyway ? Create a directory (wherever > you want) with the config file and template. Then create a shell script > (or batch file) which launches r2w.py with the correct config file (you > can pass the template file location as a command line argument). > Yes, you could be right, it was a bit of a 'think aloud' mail. I think my main problem is that I have a (slightly) old-fashioned programmers view of things (I'm an assembler/C/C++/Java programmer) which expects things to be in compartments. HTML and CSS and things like that don't fit into my ordered view of the world too well. What I have ended up doing is quite like what you suggested. I have now separated 'source' and 'destination' and in the source directory I have the r2w.ini file and the template file. Thus to build one particular hierarchy I go to the top of that hierarchy and run r2w.py. I don't quite know why I didn't see this way of doing things earlier! -- Chris Green |
From: Michael F. <fuz...@vo...> - 2007-04-01 23:27:58
|
Chris G wrote: > Maybe it's just me and wanting a tidy way to do things but I just > can't come up with a 'tidy' way of arranging a rest2web installation > so it appears logical and reasonably easy to maintain. > > How do others handle this? > > As I see it (and this will probably ramble a bit as I explain as I'm > talking to myself to some extent):- > > When you install rest2web you (very reasonably) get a > rest2web-0.5.1 directory where everything you need is installed. > I have copied the rest2web subdirectory to my python site-packages > directory and I have put a copy of r2w.py on my path. So far so > good. > > Now I want to create a new 'source' tree for creating a web site. > In my case it's called 'info'. One of the major advantages of > rest2web is that the source is readable in its own right, this is > why I chose it. So I create a sub-directory 'info' in my home > directory and create text files there which I can (and will) view > directly for local use. > > So where do I put the r2w files associated with my 'info' tree? > By default r2w expects them to be in /home/chris/info but, to my > mind anyway, that clutters the nice clean information resource I'm > creating with things like templates, css files, etc. > > My solution at present is to create an 'info' directory in the > rest2web-0.5.1 directory and put an r2w.ini, template file, css, > etc. there but it's not ideal because that's the r2w software > installation directory and having other (configuration related) > stuff there makes upgrades awkward. It also doesn't really work > with the r2w examples and documentation there which are partly but > not totally done the same way. > > Maybe I'm being too complicated/demanding but ideally how I'd like it > to work is:- > > The rest2web installation itself goes into /usr/local or somewhere > like that and, once installed, you never touch it except to > upgrade it. (Automation of the copying to site-packages would be > nice but I'm quite happy with doing it manually) > > There's a configuration directory, probably somewhere in the > user's home directory, where the .ini file for each 'tree' is kept > and also any custom template and css files. (I'm not sure about > css, since they're used at run time) > > The 'source' and 'destination' directories (i.e. where the .txt > files and .html files are respectively) have *only* the .txt and > .html files in them. > > I think there's probably a 'grey area' around the css files and maybe > template.txt. Having 'images' and 'stylesheets' directories in the > destination directory is not too unreasonable as these don't visibly > clutter places that one sees normally. On the other hand they're not > really in an easy to find place while building a site. > > > Just some ideas for kicking around, if I'm the only person thinking > this way then never mind, I'll live with it as it is because it does > so much in the sort of way I want. > > But what is to stop you doing this anyway ? Create a directory (wherever you want) with the config file and template. Then create a shell script (or batch file) which launches r2w.py with the correct config file (you can pass the template file location as a command line argument). All the best, Fuzzyman http://www.voidspace.org.uk/python/articles.shtml |
From: Michael F. <fuz...@vo...> - 2007-04-01 23:24:27
|
Chris G wrote: > On Fri, Mar 30, 2007 at 07:34:49PM -0300, Marcelo Huerta wrote: > >> Chris G escribió: >> >> >>> I want to be able to use 'r2w.py -f' but specifically ignore a >>> directory called 'config' (or something similar). Then I can put all >>> the customisation for a particular rest2web hierarchy in that config >>> directory. >>> >> *Cough* >> >> http://www.voidspace.org.uk/python/rest2web/special_files.html#prune >> >> *Cough* >> >> > I *almost* asked if I was missing something obvious! :-) > > However it's not documented for the purpose for which I want it which > is probably why I missed it. (That's my excuse anyway) > > Let me know if it doesn't work for you - this is another good use case. The problem with rest2web is that there are now quite a few features and knowing how to document them can be a problem. Patches accepted! Fuzzyman http://www.voidspace.org.uk/python/articles.shtml > Thanks! > > |
From: Michael F. <ar...@vo...> - 2007-04-01 23:22:55
|
Chris G wrote: > On Fri, Mar 30, 2007 at 02:29:21PM +0100, Chris G wrote: > >> This may seem to be a rather basic question! >> >> I've been using r2w for a while but I've only just tried to create a >> new destination hierarchy. Previously I'd been regenerating existing >> hierarchies (e.g. the r2w 'docs_html' one) or I was working with r2w's >> destination set the same as the source so the .html files were put in >> the same directories as the .txt files. >> >> Now I've changed the destination so that it's a new directory in >> /var/www/htdocs and r2w.py fails with a "No such file or directory" >> for the first level of subdirectory under /var/www/htdocs. >> >> Have I really got to create the destination hierarchy manually (or at >> least write a script to do it)? >> >> > A little further checking and I think I see what's happening. > > I'm using "r2w.py -f". If a source directory contains no *.txt files > then I get the "No such file or directory" for the corresponding > destination directory. Presumably it doesn't create the destination > because there are no files to put there, and then it tries to create > the default index.html file and there's no directory. At least that's > what it looks like. > I suspect you are right - in which case it is a bug that needs fixing. Thanks for the report. Fuzzyman http://www.voidspace.org.uk/python/articles.shtml |
From: Michael F. <fuz...@vo...> - 2007-04-01 23:22:16
|
Chris G wrote: > When using the <* .... *> syntax to insert something into a rst page > what variables are available? > > I tried 'title' and was told that wasn't defined and I suppose that's > not unreasonable. Then I tried 'pagename' and that was undefined too > which doesn't seem right to me, surely the filename should be known. > Looking at the code (call to 'render_well' in line 934 of restprocessor.py), only the uservalues are available at this point. What is your usecase for knowing the filename at this point ? (I only envisaged uservalues being used here - but it *could* be used for general templating.) Anyway - I note your feature request to add more values here - a strong use case might speed it up. :-) (By the way, this is a *slightly* obscure feature of rest2web - it is good to see it getting used. :-) Fuzzyman http://www.voidspace.org.uk/python/articles.shtml |
From: Marcelo H. <mar...@gm...> - 2007-03-31 23:57:19
|
Chris G escribi=F3: > Thanks! No problem, I'm happy to help. -- Marcelo Happy User of rest2web on http://www.sindioses.org (in Spanish) |
From: Marcelo H. <mar...@gm...> - 2007-03-31 23:55:18
|
Chris G escribi=F3: > Thanks! No problem, I'm happy to help. -- Marcelo Happy User of rest2web on http://www.sindioses.org (in Spanish) |