Re: [sword-devel] Diatheke Patch (was Re: Next version)
Hi, Actually, I had another reason to suggest adding these to Diatheke. Specifically, I'd like to have get to a full LaTeX exporter at some point, i.e. supporting the options (Word of Christ in Red, etc.). I don't really see how that could be done without using the API. Any idea? God bless Raphaël On Sun, Mar 31, 2013 at 8:56 PM, Peter von Kaehne wrote: > On Sun, 2013-03-31 at 09:21 -0500, Greg Hellings wrote: > > > I don't know the limits of LaTeX and whether a custom exporter > > program is feasible, but is there any particular reason to not want > > changes to Diatheke? > > Only starting now to get to grips with latex, but FWIW, Latex allows > embedding of various languages into new macros, so a use of e.g. the > Perl bindings within Latex is entirely feasible and would be a great > addition. > > I think that is the way to go and not via some circuitous shell > construct. > > Peter > > > ___ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Diatheke formatting options
Hello, For some time, I've been struggling with Diatheke's output, piping it into sed and other string editors when I need to grab simple verses. To make things easier, I'm attaching a patch to this email which adds 3 flags to Diatheke: * --no-refs suppresses reference printing in output * --no-mod-name suppresses the module name in output * --no-newlines replaces new lines with a space in output When combining the 3 flags, Diatheke outputs the all the verses as a single paragraph without references or module name. Here are a few examples: $ diatheke -b KJV -k Jn 3:16-17 John 3:16: For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life. John 3:17: For God sent not his Son into the world to condemn the world; but that the world through him might be saved. (KJV) $ diatheke -b KJV --no-mod-name -k Jn 3:16 John 3:16: For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life. John 3:17: For God sent not his Son into the world to condemn the world; but that the world through him might be saved. $ diatheke -b KJV --no-refs -k Jn 3:16-17 For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life. For God sent not his Son into the world to condemn the world; but that the world through him might be saved. (KJV) $ diatheke -b KJV --no-refs --no-mod-name --no-newlines -k Jn 3:16-17 For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life. For God sent not his Son into the world to condemn the world; but that the world through him might be saved. Blessings, Raphaël diatheke_opts.patch Description: Binary data ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Fwd: [bt-devel] Systemwide clucene indexes
-- Forwarded message -- From: Raphaël Pinson Date: 2009/8/15 Subject: Re: [bt-devel] Systemwide clucene indexes To: BibleTime development On Thu, Jul 30, 2009 at 9:59 AM, Eeli Kaikkonen wrote: > On Thu, 16 Jul 2009, Raphaël Pinson wrote: > >> Hello, >> >> I have a proposal to improve the usability of BibleTime for end users. >> Currently, when you install modules, whether locally or systemwide, >> you need to build the indexes before peforming searches. In >> Debian/Ubuntu, quite a few modules are packaged and shipped as .deb, >> making them available to all users. I think it would be great if the >> indexes could be compiled and installed systemwide aswell. From what I >> see, this would require 2 things : >> * that BibleTime search for clucene indexes in /usr/share/foo in >> addition to ~ ; >> * that there exists a CLI tool to generate the indexes from the modules. >> >> >> With these two conditions, packagers could generate the indexes from >> the modules as they package them, and ship them together for >> systemwide installation, which would allow all users on the system to >> benefit from the indexes without building them. >> >> >> Feedback on the idea is welcome :-) >> >> >> Raphaël Pinson Hi Eeli, > > Hello, it's been long time again since I last wrote to this list... > > The idea is basically good. It would be easier to implement like this: > > In the config dialog there would be a checkbox for "Preferred > directory for indexes" and a textbox/opener button for directory > selector. This directory would be used instead of the home directory if > the checkbox is selected. New indexes would be created there and when > using indexes the program would search them there first and then in the > home directory. > > But that would complicate things for users. If the packagers want to > package indexes they should modify the software so that the program uses > the preferred directory by default. And there's a problem with file > permissions. If the Preferred directory is selected and the user doesn't > have write permissions, creating an index fails. At least the user > should be given a notice: "You don't have permission to write to x/x/x. > You can create a new index to you home directory by temporarily > disabling the preferred index directory from the configuration dialog." That is why I proposed to have a cascading system instead. This is very common in Unix programs (and in KDE in particular). For example, KDE has paths for the configuration, set in /etc/kderc. This is how Kubuntu overrides KDE defaults without impacting user configurations. Such a system could just look for indexes in several paths, and stop if it finds one. If no index is found, then the user could create one in his home directory. Is there a need to re-create an index for a work ? If that is the case, the cascading system would just have to override the system index with the user one (just like it's done with configs). Regards, Raphaël Pinson ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Systemwide clucene indexes
On Thu, Jul 16, 2009 at 5:59 PM, Dmitrijs Ledkovs wrote: > 2009/7/16 Raphaël Pinson : >> Hello, >> >> I have a proposal to improve the usability of BibleTime for end users. >> Currently, when you install modules, whether locally or systemwide, >> you need to build the indexes before peforming searches. In >> Debian/Ubuntu, quite a few modules are packaged and shipped as .deb, >> making them available to all users. I think it would be great if the >> indexes could be compiled and installed systemwide aswell. From what I >> see, this would require 2 things : >> * that BibleTime search for clucene indexes in /usr/share/foo in >> addition to ~ ; >> * that there exists a CLI tool to generate the indexes from the modules. >> >> >> With these two conditions, packagers could generate the indexes from >> the modules as they package them, and ship them together for >> systemwide installation, which would allow all users on the system to >> benefit from the indexes without building them. >> >> >> Feedback on the idea is welcome :-) >> >> >> Raphaël Pinson >> > Hi Dmitrijs, Thank you for your feedback. > Sure. On the debian/ubuntu side we were getting around to look into > packaging modules (it is possible they are out-of date) > > One request (which was heatedly discussed before) is to show users > 1) which modules are system-wide and hence need to use Kpackagekit to > remove/add > 2) for user to be able to show / hide those modules I think this is outiside of the scope of system-wide indexes. While I agree that it could be nice to allow users to find modules to install systemwide using a systemwide package manager, I'd have a question about that: is this the way it is done currently in Ubuntu/Kubuntu (e.g. for modules in Firefox). BibleTime is now pure Qt (unless I'm wrong) so it's not KDE-specific anymore, and people who use it might not have KpackageKit or any other KDE app installed, so I don't think it would be good to rely on KDE-specific programs. I'd be interested to know how it's currently done in Ubuntu. > Eg. If for example one user wants to study / view all of the modules > while another user just wants to work with smaller amount of modules. > > From me additional request would be if Bibletime can hook into > Kpackagekit to show which modules are available for system-wide > install and optionally install them. Kpackagekit is distro-agnostic > and will work in Debian, Ubuntu and Fedora if they will have modules > packaged. > > more info at http://packagekit.org/ > > -- > With best regards > > > Dmitrijs Ledkovs (for short Dima), > Ледков Дмитрий Юрьевич > > ___ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Systemwide clucene indexes
Hello, I have a proposal to improve the usability of BibleTime for end users. Currently, when you install modules, whether locally or systemwide, you need to build the indexes before peforming searches. In Debian/Ubuntu, quite a few modules are packaged and shipped as .deb, making them available to all users. I think it would be great if the indexes could be compiled and installed systemwide aswell. From what I see, this would require 2 things : * that BibleTime search for clucene indexes in /usr/share/foo in addition to ~ ; * that there exists a CLI tool to generate the indexes from the modules. With these two conditions, packagers could generate the indexes from the modules as they package them, and ship them together for systemwide installation, which would allow all users on the system to benefit from the indexes without building them. Feedback on the idea is welcome :-) Raphaël Pinson ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Ubuntu
Le Vendredi 21 Avril 2006 23:40, Roberto C. Sanchez a écrit : > David J. Ring, Jr. wrote: > > Unfortunately with the distributions I've tried, I find they run much > > slower on older machines - much slower than Windows XP - which surprises > > me. I have one machine that is a Pentium 3 at about 550 MHz with 64 MB > > RAM and it is slower than a slothful man at work time. Ringht now I'm > > running on Mandriva Linux 2006 and it just creeps when doing anything. > > > > Anyone have a recommendation for a linux distro that runs quickly on old > > machines? > I'd also recommend Xubuntu if you want to keep an Ubuntu background with a light WM. Xubuntu now has an install CD with Dapper (which is now beta). Raphaël -- Raphaël Pinson <[EMAIL PROTECTED]> Ubuntu - Linux for Human Beings http://www.ubuntulinux.org pgpRiF4xVIskH.pgp Description: PGP signature ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] SwordModuleCreator
I personally use Quanta to edit the OSIS files since it's an XML format, and I think developping a module to support OSIS in Quanta would be great :) If anyone is willing to do that... <>< Raphaël Le Vendredi 24 Mars 2006 15:26, canfield a écrit : > Hello, > To those interested, a new version of SwordModuleCreator can be found at > sourceforge: https://sourceforge.net/projects/modulecreator/ > There are two flavours to choose from: > The executable is a setup file which will install the executable, help and > test project files (Windows only) The second is the source code for > SwordModuleCreator for those who wish to try compiling themselves. > > The program has been debugged and further developed. It is now possible to > have a project which contains multiple files. The files will be compiled > into a single module. The tags catalog now includes Osis, VPL and IMP > formats, so bibles, daily devotions and lexicons may be created with it. > All compilers are built-in and written using wxWidgets. The windows setup > includes a help file which descibes the functions. It also includes a > little test project showing how multiple files can be used to create a > genbook module. > > There is no doubt more that could be added, but at the moment I will leave > this version as the final one except for any corrections found necessary. > Hopefully this application will prove to be a usefull tool for those using > windows. I would like to try and port it to Linux, but my attempts so far > have failed due to not being able to set up the system properly for > wxWidgets. Perhaps some one might like to have a go? Anyway have fun using > it. -- Raphaël Pinson <[EMAIL PROTECTED]> Ubuntu - Linux for Human Beings http://www.ubuntulinux.org pgpr8DL33NLDA.pgp Description: PGP signature ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Re: Jonah 1.17 / 2.1
Just adding to my own post: if some of you wonder why i'm insisting on this verse issue, have a look at the WLC Sword module : it lacks verse 2.11, since it couldn't be added using the KJV layout, that only goes up to 2.10. This means we lost this verse in WLC, which is a reference text... Raphaël -- Raphaël Pinson <[EMAIL PROTECTED]> Ubuntu - Linux for Human Beings http://www.ubuntulinux.org pgp4aiRXL5JKy.pgp Description: PGP signature ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Jonah 1.17 / 2.1
Hello, I have begun to convert David Martin and Ostervald French versions of the Bible to OSIS, so as to create Sword modules with them. Doing that, I came across some issues. One of them is with Jonah 1.17 / 2.1. When building the Sword module for Jonah (from the Ostervald 1996 version), I got a warning from osis2mod, saying it was moving Jonah 2.11 back to 2.10. So I checked these verses, and indeed there is no such verse as Jonah 2.11 in KJV. It is numbered 2.10 instead. This is due to the fact that in KJV, there is a 1.17 verse, that is numbered 2.1 in Ostervald. In both the printed French Bibles I have here (NBS - Revision of the LSG, a trustable translation based directly on the Hebrew and Greek texts - and TOB - a modern ecumenical translation also based on original texts), I have a 2.11 verse and thus no 1.17. Now I was wondering about that, cause of course if I try to make a parallel between several versions in BibleTime, they don't match on these verses... so I began to search deeper... going back to the source... Both WLC and my personal Hebrew TNK (a German version from the beginning of the century) have 2.11, and no 1.17. Could the KJV be wrong on this? How is it possible to keep the numbering scheme with 2.11 verse and no 1.17 in Sword modules, given that osis2mod automatically removes 2.11? <>< Raphaël -- Raphaël Pinson <[EMAIL PROTECTED]> Ubuntu - Linux for Human Beings http://www.ubuntulinux.org pgpaInNyocC0j.pgp Description: PGP signature ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] new project proposal
Hello Fabrizio! This sounds like a nice idea. Some months ago, we had talked with a few other christian linux fellows about creating a wiki Bible, that would be translated from the Hebrew/Aramaic/Greek into lots of languages, as a collaborative work. Maybe it can become a complement to your work :) Raphaël On 12/28/05, Fabrizio Lanza <[EMAIL PROTECTED]> wrote: > Hello, > I'm starting a new project at sourceforge.net, titled "Biblic Translation > Platform". We will be 4 developers. I would like to know if we could make it > part of the crosswire project. > > Some details about the Biblic Translation Platform (codename "biblic"). > Platform: OS indipendent > Programming langs: Perl, C++, Java, JavaScript, PHP > User interface: wxWidgets, web > Database, MySQL, ODBC > Description: > Biblic Translation Platform (BTP) is a translation software with many > utilities, which aid translating from Hebrew and Aramaic. It is specifically > targeted to biblic and jewish mystical sources. > > Tools will include: conversion utilities for Hebrew and Aramaic (addressing > charset issues, etc.), database backup tools for right-to-left languages, > web Hebrew-English-Hebrew dictionary (later Hebrew-Italian-Hebrew also), web > Aramaic-English-Aramaic dictionary (later Aramaic-English-Aramaic also), > realtime Hebrew translator (standalone and web), realtime Aramaic translator > (standalone and web), Hebrew bible translation memory for CAT tools, misc > tools for developers, etc. > > We believe that after the Brown-Driver-Briggs Lexicon, this project will be > the next great innovation in the biblic field. It will provide invaluable > tools both to scholars and translators. > Putting online our dictionary (which currently is for modern Hebrew), users > will be able to enhance it, and slowly train it with biblic Hebrew. More > people will use it, and more the realtime translator will become effective. > > Kindest regards, > > Fabrizio Lanza - ULC-ITALIA > > > ___ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > -- Raphaël Pinson - [EMAIL PROTECTED] http://raphink.multiply.org Ichthux - http://www.ichthux.org - Christian Linux Distribution ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Re: Christian Debian distro talk / Report
On Apr 5, 2005 2:16 PM, Nigel Chapman <[EMAIL PROTECTED]> wrote: Pastor Ed B. wrote: Can we *please* get rid of the development packages, the unnecessary editors (5 editors? how about just down to Kedit, Kate, and a text editor (I prefer nano over zile, easier for a newbie to use, but it doesn't matter THAT much - most newbies don't do console editing anyway). Console editing matters for developers, however, which we definitely want to attract. So a good choice of editors (Kate, Vim, Emacs) is essential. It means the disk can be used to extend future versions of itself. Text editors don't take up much space, anyway, and needn't be linked in menu's. Totally agreed Nigel, and that's what I've been doing so far. I use the last version of Ichthux to build the next one, as Knoppix contains all the tools to build Knoppix-remastered Live CDs. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Re: Christian Debian distro talk / Report
Hi all! We're now having some logos done... I gathered them on the wiki : http://ichthiux.free.fr/wikini/wakka.php?wiki=IchthuxLogo I modified (although not entirely yet) the main page of the wiki ( http://ichthiux.free.fr/wikini/wakka.php?wiki=Main ) so as to take in account the merging of the projects as a new one. God bless Raphaël On Mar 31, 2005 5:15 PM, Nigel Chapman <[EMAIL PROTECTED]> wrote: > Hi all, > > We're obviously going to need a logo for this ICHTHUX thing (which I > humbly suggest is the best title of those thus far mooted, in regard to > fishiness, for instant recognition amongst Christians, and > web-uniqueness, for domain name availability and search engine results). > > Here are my suggestions for what the logo needs to achieve: > > 1. It has to focus on the 'fish'; that's what signals to Christians the > nature of the project. > > 2. But it has to avoid the 'standard', horizontal, 2 dimensional, rather > static, Christian fish of bumper-sticker fame -- rather it needs to > communicate something living and vibrant. > > 3. In spite of the nice "HTH" in the centre of the word, it's more > important to reinforce the fish meme than to try and capitalize on the > possible 'cross' associations. They look rigidly geometric rather than > organic, in any case, which is bad. > > I've attached a photo of a sketch of one possible idea. I'm not going to > explain it at this point, since if logos need to be explained, then > they've already failed. > > Comments are welcome. If it gains mindshare I'll turn it into vector > art, colorize it, make GIFs and JPEGs, etc. > > I'm very excited about this project; my own work in the area (web based > Bible search tools) would not have been possible without the Sword > library and its Diatheke interface. I wasn't awake at 4am Sydney time > for the start of our talk, but I expect to be catching up with more of > you next time around. > > Blessings, > Nigel Chapman > > -- > > Nigel Chapman | Email,MSN: [EMAIL PROTECTED] > p a n t a + s u n e r g e i + e i s + a g a t h o n > > > ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Re: Christian Debian distro talk / Report
I like your drawing very much so far :) My original idea was to use the X as a cross put aside. That was much easier to do with the word iXthus, since the X was in the middle of the word. At the same time, it might indeed be better to not use the cross on the logo and stick ton the fish, which also means a lot to Christians :) On Mar 31, 2005 5:15 PM, Nigel Chapman <[EMAIL PROTECTED]> wrote: > Hi all, > > We're obviously going to need a logo for this ICHTHUX thing (which I > humbly suggest is the best title of those thus far mooted, in regard to > fishiness, for instant recognition amongst Christians, and > web-uniqueness, for domain name availability and search engine results). > > Here are my suggestions for what the logo needs to achieve: > > 1. It has to focus on the 'fish'; that's what signals to Christians the > nature of the project. > > 2. But it has to avoid the 'standard', horizontal, 2 dimensional, rather > static, Christian fish of bumper-sticker fame -- rather it needs to > communicate something living and vibrant. > > 3. In spite of the nice "HTH" in the centre of the word, it's more > important to reinforce the fish meme than to try and capitalize on the > possible 'cross' associations. They look rigidly geometric rather than > organic, in any case, which is bad. > > I've attached a photo of a sketch of one possible idea. I'm not going to > explain it at this point, since if logos need to be explained, then > they've already failed. > > Comments are welcome. If it gains mindshare I'll turn it into vector > art, colorize it, make GIFs and JPEGs, etc. > > I'm very excited about this project; my own work in the area (web based > Bible search tools) would not have been possible without the Sword > library and its Diatheke interface. I wasn't awake at 4am Sydney time > for the start of our talk, but I expect to be catching up with more of > you next time around. > > Blessings, > Nigel Chapman > > -- > > Nigel Chapman | Email,MSN: [EMAIL PROTECTED] > p a n t a + s u n e r g e i + e i s + a g a t h o n > > > ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Re: Christian Debian distro talk / Report
Hello guys, The talk held today as planned (and even before the time it was planned). There were unplanned guests to it too. Took part in the chat : - biblix : head of the biblix project - daga : bug finder for the sword project (joined later) - glasseyes : administrator of the crosswire mailing lists - jansorg : head of the BibleTime project - pastorEd : head of the iXthus project - raphink : head of the ichthux project - scribe : head of the sword project - tee : head of the GnomeSword project - _mg_ : programmer of the BibleTime and Sword projects Were here as observers : - AnglX - n1637 Presentation of the various linux distribution projects : * Biblix : Biblix is aimed to be a linux live CD easy to use and running on slow computers, so people with few money can run it. biblix : "Biblix started with sysresccd so that it was small and could be used by people who do not have big pc so poor people could study the bible by themselves. Then onto kaella because it saves me time to frenchize the distro [raphink : kaella being a french localization of knoppix, thus a Debian based distro]". * iXthus : The goal of the iXthus project is to create a whole Christian Debian-based distribution. pastorEd : "The iXthus Project is a Linux distribution intended to be an OS replacement for MS Windows. It is designed to be immediately usable by non-Linux users. Based on Debian, NOT a LiveCD (yet). We are working on a Kanotix - LiveCD version, but nothing released so far. iXthus Project has Sword Project files (Bibletime, Gnomesword), as well as regular Linux tools [...] The iXthus Project iso is really just SystemRescue CD with the iXthus system as a .tbz2 file on the CD". * LateDecember : Davy, the head of the LateDecember project, could not be part of the talk unfortunately, but he let me know that he was interested in the project, and I presented his project myself. raphink : "[LateDecember] is a DamnSmallLinux (Debian knoppix again) with quite the same goals [as the other projects] running christian apps under fluxbox". * Ichthux : Ichthus is a very recent project I started last week. It is a live CD. raphink : "Ichthux (almost as Pastor Ed's iXthus, although I didn't know about it at all) [is] based on knoppix 3.8 (CeBit version, as the official version is not out yet). It has many goals : 1) providing a nice live CD with christian apps for christian geeks used to knoppix 2) providing a nice way to christians to get to linux 3) providing a way of installing a full Debian system on churches' computers 4) hopefully, converting some non christian geeks that would download ichthux for a try and discover the Bible at the same time". The immediate conclusions are obvious : - all these projects are based on Debian - all these projects plan to include Christians apps (including obviously the sword project and GUI such as BibleTime and/or GnomeSword) - all these projects have too few developers and lack means of hosting their work It seems everyone agrees that merging the projects would make it a stronger one without modifying the goals of each one. The first question that comes is whether this project should be a whole independent distribution, or rather a distribution derived from an existing one (such as Ubuntu for Debian). Everyone agrees that this is not the goal to improve the technical aspects of the distribution, that the project should use an existing technical basis to build a Christian project with Christian apps. Debian is chosen as the core basis. Because of the different needs that various end users (young believers, old people, ministers, missionaries, etc...) might have of such a distribution, there comes the question of the existence of various subprojects aimed to different people. There is no answer to it yet. [Personal opinion : a live CD should be able to be used by any user, and a whole distro should leave the choice to install a system for various needs, during installation]. Everyone agrees that the distribution should contain also non-Christian apps for a general use (although they might be ``christian-tuned''). Once this is set, there is a need for : 1) a website to manage the project 2) a staff with tasks for everyone 3) a place to host the products (ISOs and packages) Scribe says crosswire is willing to host such a project and provide an official webpage, a ftp for the hosting, plus mail, servlist and ssh. For the organization of the project, the ichthux wiki (http://ichthux.free.fr) can be used as it is already set for this use. The last point is the name of the project. In the less than 10 gathered so far, at least two have a named derived from the greek word Ichthus. Linc Fessenden from the L4C project seems to have thought about Icthux aswell (http://www.thelinuxlink.net/pipermail/linux4christians/2002-January/08.htmlhttp://www.thelinuxlink.net/pipermail/linux4christians/2002-January/08.htmlhttp://www.thelinuxlink.net/pipermail/linux4christians/2002-January/
