Be that as it may, it would be helpful if someone could go the extra mile
beyond the call of duty.
As it is, I have no means to test a new GenBook module until itβs been put in
CrossWire Beta by Dom.
Kind regards,
David
Sent from ProtonMail Mobile
On Wed, Jun 3, 2020 at 15:44, Greg Hellings <greg.helli...@gmail.com> wrote:
> I will remind you
>
> 1) Windows builds of the utilities are not officially supported at all
> 2) Builds of the utilities from any source other than SVN trunk are not
> supported at all
>
> This problem falls into both categories and is, therefore, not a supported
> situation that is likely to garner any attention.
>
> --Greg
>
> On Wed, Jun 3, 2020, 09:36 David Haslam <dfh...@protonmail.com> wrote:
>
>> http://tracker.crosswire.org/browse/MODTOOLS-104
>>
>> Sent from ProtonMail Mobile
>>
>> On Wed, Jun 3, 2020 at 14:33, David Haslam <dfh...@protonmail.com> wrote:
>>
>>> My Sword path is not in the part of the system that Windows guards like
>>> that!
>>>
>>> It's where any normal Windows user with the same name would have it.
>>>
>>> C:\Users\David\AppData\Roaming\Sword
>>>
>>> For my own convenience, I have subst s: <sword_path> as one of the several
>>> substitute drives made during startup.
>>>
>>> I never had such a weird problem with other module creation tools.
>>>
>>> Best regards,
>>>
>>> David
>>>
>>> Aside (especially for Tom): Eggshellβ’ is Sean Connery's favourite
>>> spreadsheet program. π
>>>
>>> Sent with ProtonMail Secure Email.
>>>
>>> βββββββ Original Message βββββββ
>>> On Wednesday, 3 June 2020 14:22, Tom Sullivan <i...@beforgiven.info> wrote:
>>>
>>>> David:
>>>>
>>>> I gave up on Microslop and Windoze years ago. So I am way out of date,
>>>> but even several years ago, Windoze would, for security reasons, restore
>>>> changed system files and delete foreign files unless certain settings
>>>> were made. C:\, was protected then, and maybe now.
>>>>
>>>> I think you got hit by Windoze is smarter than you behavior. Try cd to
>>>> your "my documents" directory and repeat. If you see a 3 files, then
>>>> you have a Windoze problem. You should be able to break your script into
>>>> simpler steps and fix things.
>>>>
>>>> Hope this helps.
>>>>
>>>> Tom
>>>>
>>>> Tom Sullivan
>>>> i...@beforgiven.info
>>>> FAX: 815-301-2835
>>>>
>>>> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>>
>>>> On 6/3/20 9:10 AM, David Haslam wrote:
>>>>
>>>> > I followed Timmy's sensible suggestion, which was something I'd pondered
>>>> > myself already.
>>>> > Now here's what I observed.
>>>> > Files lbc1646.dat and lbc1646.idx appeared /momentarily/ in the
>>>> > Make folder, but simply vanished when lbc1646.bdt finished being
>>>> > created.
>>>> > Does anyone have a plausible explanation for such bizarre behaviour?
>>>> > Were they moved to some unknown destination or simply deleted?
>>>> > Best regards,
>>>> > David
>>>> > Sent with ProtonMail https://protonmail.com Secure Email.
>>>> > βββββββ Original Message βββββββ
>>>> > On Wednesday, 3 June 2020 13:34, Timmy tim....@gmail.com wrote:
>>>> >
>>>> > > Hi David,
>>>> > > As Tom also mentioned, I run the command on linux, in your case, like
>>>> > > this:
>>>> > > ..\utils64\xml2gbs -fO ..\Import\OSIS\OSIS-lbc1646.fix.xml lbc1646
>>>> > > Windows also can have issues if there are spaces in the path. I don't
>>>> > > know if your full path has any spaces, but you might want to try
>>>> > > running from c:\ directly, or some path that has no spaces.
>>>> > >
>>>> > > After command runs, the 3 files are in current directory. If it does
>>>> > > not work on Windows then there might be wins problem, not sure.
>>>> > > *
>>>> > >
>>>> > > ---------------------------------------------------------------------------------------------------------------------------------------
>>>> > >
>>>> > > Timmy Braun*
>>>> > > On Wed, Jun 3, 2020 at 6:23 AM David Haslam <dfh...@protonmail.com
>>>> > > mailto:dfh...@protonmail.com> wrote:
>>>> > >
>>>> > > Thanks Tom,
>>>> > >
>>>> > > The module name is [LBC1646] (as specified in my .conf file), and
>>>> > > that points to the right module path.
>>>> > >
>>>> > > This was the command in my CMD file, all of which are stored in a
>>>> > > folder called Make under my Sword path.
>>>> > >
>>>> > > ..\\utils64\\xml2gbs -fO ..\\Import\\OSIS\\OSIS-lbc1646.fix.xml
>>>> > > ..\\modules\\genbook\\rawgenbook\\lbc1646\\lbc1646 2>..\\Log\\error.log
>>>> > >
>>>> > > NB. utils64 is a symbolic link to where I installed the Windows
>>>> > > edition of Sword utilities (x64 version).
>>>> > > Likewise, the Import folder is one I created some years ago. The
>>>> > > Log folder is similar.
>>>> > >
>>>> > > This command created the file called lbc1646.bdt in the right
>>>> > > place, but did not create the other two files.
>>>> > > And, yes, I've looked for them elsewhere too!
>>>> > >
>>>> > > So am I doing something wrong or is there a deficiency in the
>>>> > > Windows edition of xml2gbs ?
>>>> > >
>>>> > >
>>>> > > Best regards,
>>>> > >
>>>> > > David
>>>> > >
>>>> > > Sent with ProtonMail Secure Email.
>>>> > >
>>>> > > βββββββ Original Message βββββββ
>>>> > > On Wednesday, 3 June 2020 12:57, Tom Sullivan
>>>> > > <i...@beforgiven.info <mailto:i...@beforgiven.info>> wrote:
>>>> > >
>>>> > > > David:
>>>> > > >
>>>> > > > You will have cd to a temporary directory xml2gbs as xml2gbs
>>>> > > just puts
>>>> > > > its output in the current directory, then copy files from that
>>>> > > temporary
>>>> > > > directory to your .sword library as below, along with your .conf
>>>> > > file.
>>>> > > >
>>>> > > > All three of those files are created simultaneously.
>>>> > > >
>>>> > > > After you copy from the temporary directory, you should have a .conf
>>>> > > > file in .sword/mods.d, (done manually), and then from your temporary
>>>> > > > directory: in .sword/modules/genbook/rawgenbook/somemodulename
>>>> > > the three
>>>> > > > files *.bdt, *.dat, *.idx.
>>>> > > > An images directory should be there also if there are images.
>>>> > > >
>>>> > > > This is Linux. I do not know what Windoze will do.
>>>> > > >
>>>> > > > Hope this helps.
>>>> > > >
>>>> > > > Tom
>>>> > > >
>>>> > > > Tom Sullivan
>>>> > > > i...@beforgiven.info
>>>> > > > FAX: 815-301-2835
>>>> > > > ---------------------> It's apparent that the .dat and .idx
>>>> > > files are
>>>> > > > needed for the module to function aright.
>>>> > > >
>>>> > > > > When I tried to open the new module in Xiphos, nothing was
>>>> > > displayed.
>>>> > > > > So please would someone explain how I can make these two files
>>>> > > so that my new module will work correctly.
>>>> > > > > Best regards,
>>>> > > > > David
>>>> > > > > Sent with ProtonMail Secure Email.
>>>> > > > > βββββββ Original Message βββββββ
>>>> > > > > On Wednesday, 3 June 2020 11:18, David Haslam
>>>> > > dfh...@protonmail.com <mailto:dfh...@protonmail.com> wrote:
>>>> > > > >
>>>> > > > > > I have just used xml2gbs to create a Generic book module for
>>>> > > the first time.
>>>> > > > > > It created a module file with extension .bdt in the right
>>>> > > location.
>>>> > > > > > All Generic book modules I've installed from CrossWire also
>>>> > > have two more files in the module folder.
>>>> > > > > > One with extension .dat and one with .idx
>>>> > > > > > I have not found anything on our wiki that describes what
>>>> > > software tool is used to create these two files, nor an
>>>> > > explanation of what they are for.
>>>> > > > > > Please would someone enlighten me.
>>>> > > > > > Best regards,
>>>> > > > > > David
>>>> > > > > > Sent with ProtonMail Secure Email.
>>>> > > > >
>>>> > > > > sword-devel mailing list: sword-devel@crosswire.org
>>>> > > <mailto:sword-devel@crosswire.org>
>>>> > > > > http://www.crosswire.org/mailman/listinfo/sword-devel
>>>> > > > > Instructions to unsubscribe/change your settings at above page
>>>> > > > >
>>>> > > > > This email has been scanned by the Symantec Email
>>>> > > Security.cloud service.
>>>> > > > > For more information please visit http://www.symanteccloud.com
>>>> > > >
>>>> > > > sword-devel mailing list: sword-devel@crosswire.org
>>>> > > <mailto: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
>>>> > > <mailto:sword-devel@crosswire.org>
>>>> > > http://www.crosswire.org/mailman/listinfo/sword-devel
>>>> > > Instructions to unsubscribe/change your settings at above page
>>>> > >
>>>> >
>>>> > This email has been scanned by the Symantec Email Security.cloud service.
>>>> > For more information please visit http://www.symanteccloud.com
>>>> >
>>>> > 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 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
