> I just want to make sure that if someone fixes this it doesn't cause any
> further problems or bugs. If nobody will do it we can leave this here.
> I can't fix this in UI because the install manager is in the Sword
> library. That is why I was worried about problems which could appear if
> this w
On Thu, 17 Jan 2008, Karl Kleinpaste wrote:
> Martin Gruner <[EMAIL PROTECTED]> writes:
> > And no more than 8+3 characters. Hehe.
>
> Oh, for pity's sake... Working far too hard at a non-problem.
>
> Fine, take the caption name, in any character combination the user
> wants, and shovel it throu
Martin Gruner <[EMAIL PROTECTED]> writes:
> And no more than 8+3 characters. Hehe.
Oh, for pity's sake... Working far too hard at a non-problem.
Fine, take the caption name, in any character combination the user
wants, and shovel it through an MD5 hash, stripping off the upper 8
characters as t
And no more than 8+3 characters. Hehe.
;)
am Donnerstag, 17. Januar 2008 um 14:53 schrieben Sie:
> Eeli Kaikkonen <[EMAIL PROTECTED]> writes:
>> Right, and therefore the file name can't be the same as caption name
>> because files names have different limitations in different platforms.
> Sur
Eeli Kaikkonen <[EMAIL PROTECTED]> writes:
> Right, and therefore the file name can't be the same as caption name
> because files names have different limitations in different platforms.
Surely isalnum()-plus-dash is a lowest common denominator of filenames
on any platform.
If /really/ necessary,
On Thu, 17 Jan 2008, Karl Kleinpaste wrote:
> Eeli Kaikkonen <[EMAIL PROTECTED]> writes:
> > That would trigger bugs later because the names are user defineable
> > and can contain any characters.
>
> There is no reason not to limit caption names to isalnum() plus dash.
Right, and therefore the f
Eeli Kaikkonen <[EMAIL PROTECTED]> writes:
> That would trigger bugs later because the names are user defineable
> and can contain any characters.
There is no reason not to limit caption names to isalnum() plus dash.
___
sword-devel mailing list: sword-
On Thu, 17 Jan 2008, Karl Kleinpaste wrote:
> The right solution would be simply to name the local directory after the
> repository's caption name, e.g. Crosswire and Crosswire-beta.
That would trigger bugs later because the names are user defineable and
can contain any characters.
Yours,
On Thu, 17 Jan 2008, DM Smith wrote:
> The solution that JSword uses for the cache name is to use the server
> name and the path, with / replace by _ .
Special characters in the remote path may be problematic if the
path is copied as-is. Maybe it should be standardized so that only ascii
alphanum
Eeli Kaikkonen <[EMAIL PROTECTED]> writes:
> Installmgr seems to write the modules conf cache in a directory which is
> named after the server name only. This is a problem if there are two
> repos in the same server, like Crosswire main and Crosswire beta. After
> refreshing one the cache is overwr
On Jan 17, 2008, at 7:11 AM, Eeli Kaikkonen wrote:
> Installmgr seems to write the modules conf cache in a directory
> which is
> named after the server name only. This is a problem if there are two
> repos in the same server, like Crosswire main and Crosswire beta.
> After
> refreshing one t
Installmgr seems to write the modules conf cache in a directory which is
named after the server name only. This is a problem if there are two
repos in the same server, like Crosswire main and Crosswire beta. After
refreshing one the cache is overwritten and querying the other entry
(with "installmg
12 matches
Mail list logo
