Re: [sword-devel] Maintaining Module Creation Sources and Scripts

2008-11-29 Thread DM Smith
On Nov 29, 2008, at 10:10 AM, jhphx wrote: > DM Smith wrote: >> >>> >>> Perhaps a .conf file entry for Repository= entry also. >>> >> I'm not sure I understand this. What does this refer and how is it >> needed. >> > > For modules that are only on alternative repositories it could be > used to

Re: [sword-devel] Maintaining Module Creation Sources and Scripts

2008-11-29 Thread jhphx
DM Smith wrote: Perhaps a .conf file entry for Repository= entry also. I'm not sure I understand this. What does this refer and how is it needed. For modules that are only on alternative repositories it could be used to generate an indication that the module for some r

Re: [sword-devel] Maintaining Module Creation Sources and Scripts

2008-11-29 Thread DM Smith
On Nov 29, 2008, at 9:54 AM, jhphx wrote: > Troy wrote: >> ...I guess the general answer to that is that the >> .conf file SHOULD have a valid TextSource= entry pointing to where >> the >> source was obtained. ... > > Perhaps a .conf file entry for Repository= entry also. I'm not sure I under

Re: [sword-devel] Maintaining Module Creation Sources and Scripts

2008-11-29 Thread jhphx
Troy wrote: > ...I guess the general answer to that is that the > .conf file SHOULD have a valid TextSource= entry pointing to where the > source was obtained. ... Perhaps a .conf file entry for Repository= entry also. Jerry ___ sword-devel mailing

Re: [sword-devel] Maintaining Module Creation Sources and Scripts

2008-11-29 Thread Chris Little
DM Smith wrote: > On Nov 29, 2008, at 7:30 AM, Troy A. Griffitts wrote: > >> Dear Greg, >> >> Yes, we haven't had much that we feel the need to maintain yet, save >> the >> token KJV2003 example. This may change in the coming years when our >> community projects rev up. I understand your con

Re: [sword-devel] Maintaining Module Creation Sources and Scripts

2008-11-29 Thread DM Smith
On Nov 29, 2008, at 7:30 AM, Troy A. Griffitts wrote: > Dear Greg, > > Yes, we haven't had much that we feel the need to maintain yet, save > the > token KJV2003 example. This may change in the coming years when our > community projects rev up. I understand your concern to know where > the

Re: [sword-devel] Maintaining Module Creation Sources and Scripts

2008-11-29 Thread Troy A. Griffitts
Dear Greg, Yes, we haven't had much that we feel the need to maintain yet, save the token KJV2003 example. This may change in the coming years when our community projects rev up. I understand your concern to know where the source documents reside. I guess the general answer to that is that t

Re: [sword-devel] Maintaining Module Creation Sources and Scripts

2008-11-29 Thread Greg Hellings
On Sat, Nov 29, 2008 at 2:57 AM, Chris Little <[EMAIL PROTECTED]> wrote: > > > Greg Hellings wrote: >> Just a question... >> >> Are both of these accessible to anyone interested? If a confused >> person can get the source used and the scripts, then run them, they >> can probably figure that much o

Re: [sword-devel] Maintaining Module Creation Sources and Scripts

2008-11-29 Thread Chris Little
Greg Hellings wrote: > Just a question... > > Are both of these accessible to anyone interested? If a confused > person can get the source used and the scripts, then run them, they > can probably figure that much out and have a look at their questions. > But from the looks of it, the sources ar

Re: [sword-devel] Maintaining Module Creation Sources and Scripts

2008-11-29 Thread Greg Hellings
Just a question... Are both of these accessible to anyone interested? If a confused person can get the source used and the scripts, then run them, they can probably figure that much out and have a look at their questions. But from the looks of it, the sources aren't accessible? --Greg On Sat, N

[sword-devel] Maintaining Module Creation Sources and Scripts

2008-11-29 Thread Troy A. Griffitts
CrossWire has an official place to keep content conversion scripts: http://crosswire.org/svn/sword-tools/trunk/ and places to store the sources used to create the modules which are in our repository: crosswire.org:~betamods/source/ crosswire.org:~pubmods/source/ The later has not been kept up