Timmy Braun has tried xml2gbs in Windows 10.
The .idx & .dat files were created, but only every other SECTION of the
resulting test module LBC1646 were displayed.
i.e. SECTION I, III, V, VII, IX,...
Very weird behaviour!
To compare the results with the module built properly under Linux might be
I just tried with MSE stopped. It made no difference at all.
David
Sent from ProtonMail Mobile
On Wed, Jun 3, 2020 at 22:23, Greg Hellings wrote:
> On Wed, Jun 3, 2020, 15:41 David Haslam wrote:
>
>> The only AV that I use is Windows Security Essentials.
>> This has never caused me any issue
The only AV that I use is Windows Security Essentials.
This has never caused me any issues with other Sword utilities, so I doubt it
could be the culprit for xml2gbs. There's nothing in its quarantine storage.
I noticed during a further test earlier this evening that during the fleeting
existenc
Well I guess there's at least one Windows 10 user on this mailing list, so it
would be useful to know whether the same issue occurs on that supported
operating system, even if one accepts that Windows 7 is past its official end
of support for non-enterprise customers.
Aside: There's still a ver
On Wed, Jun 3, 2020, 15:41 David Haslam wrote:
> The only AV that I use is Windows Security Essentials.
> This has never caused me any issues with other Sword utilities, so I doubt
> it could be the culprit for xml2gbs. There's nothing in its quarantine
> storage.
>
Can you try running the impor
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
On Wed, Jun 3, 2020 at 12:41 PM David Haslam wrote:
> Well I guess there's at least one *Windows 10* user on this mailing list,
> so it would be useful to know whether the *same issue* occurs on that
> supported operating system, even if one accepts that *Windows 7* is past
> its official end of
http://tracker.crosswire.org/browse/MODTOOLS-104
Sent from ProtonMail Mobile
On Wed, Jun 3, 2020 at 14:33, David Haslam 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\Da
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: as one of the several
substitute drives made during startup.
I never
Well, yes, a sensible last resort - but the result was no match found!
Best regards,
David
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Wednesday, 3 June 2020 14:16, Tom Sullivan wrote:
> David:
>
> One last suggestion: Windoze (used to at least) has pretty good fil
If I watch the folder for the full datapath while I'm running the original
command, the same thing happens!
They appear and vanish
Best regards,
David
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐ Original Message ‐‐‐
On Wednesday, 3 June 2020 14:10, David Hasl
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
On Wed, Jun 3, 2020 at 9:50 AM David Haslam wrote:
> Be that as it may, it would be helpful if someone could go the extra mile
> beyond the call of duty.
>
Don't hold your breath. None of the developers of the utilities are Windows
users, nor do they support running an unsupported version of the
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\g
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 w
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 atten
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
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
David:
One last suggestion: Windoze (used to at least) has pretty good file
search capabilities. Search your whole machine for the missing files.
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
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 f
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
As such the Wiki does not describe any of our file formats and that is
intentionally so. So please do not start an article there.
Peter
> Gesendet: Mittwoch, 03. Juni 2020 um 11:18 Uhr
> Von: "David Haslam"
> An: "sword-devel mailing list"
> Betreff: [sword
22 matches
Mail list logo
