Not commenting on the merits, but only on the necessities and history:
Module names can (often should be for readability) upper and lower case
DataPath needs to match exactly the data path on the file system. The
case needs to match because some operating systems are case sensitive.
Historicall
It seems to me that squashing to lower
case for file system references is what caused problems in the
first place, because I didn't also squash the module name to lower
case. Wouldn't it be better to keep the module name the same as
the file & directory names? Of
Yes. Traditionally paths are lowercase. So is the conf file name. The zip
doesn't follow that convention.
In Him, DM
> On Aug 13, 2015, at 2:20 PM, Karl Kleinpaste wrote:
>
>> On 08/13/2015 02:15 PM, Kahunapule Michael Johnson wrote:
>> Is there anything else that needs to be fixed?
> I've ju
On 08/13/2015 02:15 PM, Kahunapule Michael Johnson wrote:
> Is there anything else that needs to be fixed?
I've just been periodically trying to load up the entire content and
reporting what I find doesn't work.
As for fixing this sort of thing, generally speaking I believe we have
always recommen
THANK YOU, Karl, for catching that and
pointing it out. I'm really embarrassed that I missed that, but
glad you caught it.
I'll let you know when the corrections are uploaded.
Is there anything else that needs to be fixed?
On 08/13/2015 02:03 AM, Karl
On Thu, Aug 13, 2015 at 12:32:04PM -0400, Karl Kleinpaste wrote:
>On 08/13/2015 11:18 AM, Fred Smith wrote:
>
> Would you like me to upload them to you (as I did with the 4.0.2 RPMs)?
>
>Thanx, but shouldn't be necessary. As Greg just explained to me, once
>his builds get into EPEL,
On 08/13/2015 11:18 AM, Fred Smith wrote:
> Would you like me to upload them to you (as I did with the 4.0.2 RPMs)?
Thanx, but shouldn't be necessary. As Greg just explained to me, once
his builds get into EPEL, then both RHEL and Centos can get them after
doing "yum install epel-release".
___
Thanks for the information. I just downloaded and installed it over the
top of 1.7.2 on Windows 10. Everything seems to be working fine, except
indexed searching. I tried it on a couple of modules, one of my own and
the ESV. Without an index, I get search results. With an index for the
same
Drat, I forgot to build the epel RPMs for this build. I'm kicking off
the build right now. Looks like biblesync never made it into EPEL-7
either, so I'll push both of them into circulation here in short
order, if possible.
--Greg
On Thu, Aug 13, 2015 at 10:18 AM, Fred Smith
wrote:
> On Thu, Aug
On Thu, Aug 06, 2015 at 11:04:40PM -0400, Karl Kleinpaste wrote:
>For those unaware: Peter von Kaehne bumped sideways into a nasty,
>crash-inducing Xiphos limitation related to the maximum count of
>language groups that can be handled at one time. This was caused by a
>new reposito
Thanks Troy. I must have missed any announcement almost 12 months ago.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/BibleCS-1-7-2-tp4653527p4654957.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
__
That's a particular module issue. Please report such issues direct to Michael
Johnson.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/New-repository-Implications-for-frontends-tp4654941p4654958.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
There are now many modules with directory upper/lowercase errors causing
installation failures. Example:
$ grep DataPath .sword/InstallMgr/20150811152606/mods.d/thaKJV2003.conf
DataPath=./modules/texts/ztext/tha*kjv*2003/
ftp> cd modules/texts/ztext/
250 CWD command successful
ftp> dir tha*
227
The SWORD Project for Windows v1.7.3
was release on Sun Aug 24 18:27:04 MST 2014
On 08/13/2015 10:53 AM, David Haslam wrote:
> Is BibleCS-1.7.2 still "in the long grass", or will there be a proper release
> with an installer?
>
> David
>
>
>
> --
> View this message in context:
> http://swor
Is BibleCS-1.7.2 still "in the long grass", or will there be a proper release
with an installer?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/BibleCS-1-7-2-tp4653527p4654953.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
__
In Haiola, I convert something as simple as:
\x + Deuteronomy 8:3\x*
to:
Deuteronomy
6:16
where the origin reference (Matthew 4:7 in this case) comes from
the location of the note if not explicitly given with an \xo tag.
That was based on
16 matches
Mail list logo
