Huge encyclopaedia: The Dictionary of Christianity and the Bible

My conversion is stuck at 25%. I deleted it and started over. Still no luck.

Logs?

4544.cef.zip

3107.PBB Logs.zip

Super Tramp:

I realized that for me it took about 2-3 hours (or more I just left my computer and then came back later in the day) to get past the converting part of the process (and the entire time the progress bar didn't move (stayed at about 25%) and then another 30 min or so at the "Compiling phase" (bar moved to about 50% but then stayed there) and then the rest took maybe 10 min to finish. So I just needed to be patient. I thought I remembered last time I did it that the bar moved consistently, but maybe not.

So I just needed to be patient.

Thanks. I will give it all night.

It is now compiling and is at 50%.   I guess time and patience is all I needed.

Re-compiling an existing book takes longer than compiling a book for the first time. But other than that I don't know why it should take so long.

Re-compiling an existing book takes longer than compiling a book for the first time.

That is odd. Why should that be? Other than a tiny extra amount of time to delete the old compiled file first, what would require more time compiling it afresh?

I don't know if this is allowed because I've never seen anyone do it before, but I've also never seen anything that says it's not allowed - so please, report this post if this is a violation of the rules.

I am attaching a link to the fully compiled file, which can then be scanned into Logos.  You can download it here.

I'll leave this up for a few days, unless it is violating rules and gets reported.

the fully compiled file, which can then be scanned into Logos.

Unless Logos did change something in the way PBs work (they want to but haven't announced anything yet), the scan should not be able to give access to the file, since as far as we know, currently only the maker of the PB holds a licence to it.

I refrained from downloading 380 MB to proof this - but would be interested if someone gets it to work.

SUCCESS at last.

Thank you very much Mark Barnes for another great contribution to Logos.

One problem I encountered was the inability to start over from scratch. The book would resume at 25% every time I tried to start over even though I had deleted it from my PB panel.

My laptop is an older (slower) one. I figure that is the main reason it took so long.

To anyone else who has yet to compile this resource; give it time. It is a BIG resource.

Re-compiling an existing book takes longer than compiling a book for the first time.

That is odd. Why should that be? Other than a tiny extra amount of time to delete the old compiled file first, what would require more time compiling it afresh?

It tries to match up articles in the existing resource with articles in the new one, so that if necessary highlighting, notes, etc. can be moved to the correct position in the updated resource.

Mark:

Are there any plans to update this entry over time as new entries are added to Wikipedia or old entries are updated?  How many changes would there be in a five year period?  Enough to warrant an update?  Or does the new connection to Wikipedia built into LOGOS somehow make this book redundant?  

I know that older dictionaries are still valued - maybe no changes are planned.  But given the fluid nature of Wikipedia, the question does make sense.  

Thanks for any details you can provide on your plans.

Are there any plans to update this entry over time as new entries are added to Wikipedia or old entries are updated?  How many changes would there be in a five year period?  Enough to warrant an update?  Or does the new connection to Wikipedia built into LOGOS somehow make this book redundant?  

The wikipedia tools certainly makes the resource less necessary, but I think it's still useful to have a fully searchable Wikipedia in this format.

I will update it from time to time. It really doesn't seem like 9 months since it was first built. I'll try and do an update before it's anniversary! It's not a huge hassle to rebuild it, but it does take several days to download and format all the articles. 

I will update it from time to time. It really doesn't seem like 9 months since it was first built. I'll try and do an update before it's anniversary! It's not a huge hassle to rebuild it, but it does take several days to download and format all the articles. 

Thanks for the details.

Floyd

Good to know.  I'll leave it up in case someone wants to try it.

Thank you for your efforts, Mark! Any chance that you could share the process so that it may be replicated for Wikipedia in other languages?

Thank you for your efforts, Mark! Any chance that you could share the process so that it may be replicated for Wikipedia in other languages?

There's a series of quite complex scripts written in PHP, with the data stored in a MySQL table. If that makes sense to you, I could perhaps share the scripts with you to adapt for another language. If not, I could see if it's possible to use another language. Did you have one in mind?

I was thinking about the German Wikipedia.

I know roughly what PHP and MySQL are, but use them, I cannot. If it is straight-forward to adapt the links and categories in the script, I may be able to do that, though.

If you'd be willing to help, that would be great. No expectations, though. [:)]

Thanks so much. I really appreciate your work and sharing with the rest of us.

Thank you for your efforts, Mark! Any chance that you could share the process so that it may be replicated for Wikipedia in other languages?

Mark,

Thanks for the great effort put out to compile the articles into a PBB.  Along the lines of the request above I was wondering if we could add another wiki source to the list. 

I am thinking of the OrthodoxWiki that is a collection of Orthodox articles.  It isn't real huge, about 4800 articles.  Might be of interest to some folks.

http://orthodoxwiki.org/Main_Page

Kudos. Fine job!

It tries to match up articles in the existing resource with articles in the new one, so that if necessary highlighting, notes, etc. can be moved to the correct position in the updated resource.

I never thought about that obvious wrinkle to re-compiling. It's quite considerate of the developers to do that.

I downloaded and built this on my MacBook and it worked great. Excellent resource.

However, I just tried to open it on my Mac mini and it says "You don't have a license to open this resource".

However, I just tried to open it on my Mac mini and it says "You don't have a license to open this resource".

I can still open it on my PC.

Were you able to successfully upload it on your MacBook after you built it?  If not then that might be the reason.

Were you able to successfully upload it on your MacBook after you built it?  If not then that might be the reason.

I assume so. I didn't get any kind of error saying it didn't.

However, I just tried to open it on my Mac mini and it says "You don't have a license to open this resource".

This resource won't sync, as it's too large for Logos' servers to accept it. You'll have to copy the .docx files onto your Mac mini and recompile it there.

Oh Mark Barnes, thank you for your tremendous work, everything worked out.
When you have more work out there, some resources for research pass me a copy, this is my Email jdetranreis@gmail.com, thank you for everything.

Thank you, Mark.

Thanks Mark!

Todah rabbah!

Hi Mark

took 90 min with 6.7.

Dit it look right? with all these Errors?
Sascha

I will update it from time to time. It really doesn't seem like 9 months since it was first built. I'll try and do an update before it's anniversary! It's not a huge hassle to rebuild it, but it does take several days to download and format all the articles. 

In going through my PB's, I found this classic. Has there been an update from the March 2014 files I compiled way back when?

Thanks for this masterpiece!

Still a great resource. Thanks Mark.

This is a real find, thanks! One question - I built it with the files going in dcb-01 showing at the top and progressing down, yet it looks like the table of contents is backwards. Is there a way to fix this, or is this just how the resource was built?

This is a real find, thanks! One question - I built it with the files going in dcb-01 showing at the top and progressing down, yet it looks like the table of contents is backwards. Is there a way to fix this, or is this just how the resource was built?

For me it was dcb-00 at the top - down through dcb-36 (you seem to be missing something towards the end, too) and the ToC is sorted right. Note I built it last 2014 with the files someplace else, so I can't check if the current PB tool has a bug.

Yeah I have the order messed up. I can fix that, thanks...

Trying to delete!

Time to Compile: 5 hours 35 minutes  [And I thought that my machine was fast but no ssd drive] Left it running over night.

File size: 383,071 KB

Log file size: 1,045 KB

Warnings: Head Words may not contain colons    [things like John 3:16]

What is the file type ending '.mstidx'  ??

So who is going to capture all the items added since that set of files were made?  

I've tried 4 times now to build the book and each time I've waited overnight, but nothing happens.  The PB just says "Converting", and the horizontal bar never moves.  It always starts out at about 1/5 complete, but then the bar never changes.  

Any ideas?

Bob

Same with me. 

I've tried 4 times now to build the book and each time I've waited overnight, but nothing happens.  The PB just says "Converting", and the horizontal bar never moves.  It always starts out at about 1/5 complete, but then the bar never changes.  

Any ideas?

If on a PC check Power Settings.  When pugged in PC goes to sleep?  select NEVER.  Not sure that is the fix but worth a try to check.

Mine took 5 and a half hours.   

That worked! Thanks.

If on a PC check Power Settings.  When pugged in PC goes to sleep?  select NEVER.

Mac OS equivalent is found in System Preferences under Energy Saver (the light bulb). I have used the settings in this screenshot for more than a dozen years and have not worn out a Mac yet. Since Hard Drives do wear out, I allow them to take a nap, The "Wake for network access" is likely unnecessary since the computer has insomnia.

Since Hard Drives do wear out, I allow them to take a nap

Spinning Hard Drives have mechanical parts (and some very strong magnets inside the drive case). Caveat: start/stop of spinning hard drive also has wear factor.

Solid State Disks (SSD) are completely electronic (so personally have "Put hard disks to sleep when possible" unchecked).

Keep Smiling [:)]

I've tried 4 times now to build the book and each time I've waited overnight, but nothing happens.  The PB just says "Converting", and the horizontal bar never moves.  It always starts out at about 1/5 complete, but then the bar never changes.  

Any ideas?

   And to John W

If on a PC check Power Settings.  When pugged in PC goes to sleep?  select NEVER.  Not sure that is the fix but worth a try to check.

Mine took 5 and a half hours.   

Well I have made the setting switch.  I am now at over 7 hours for compiling.  I do have an SSD, so didn't expect this much time.  The horizontal bar shows over 50% done now.  So we will see what happens.  The original email said something like 30 -90 minutes.  I am way longer than that, even with SSD and a fast Windows laptop.

Bob

Caveat: start/stop of spinning hard drive also has wear factor.

This is not entirely wrong but is misleading. Only with some HDDs in some condition will something similar to this statement be true. (e.g. WD green head parking. Also, start/stop means a completely different thing, and there's 2 different states too. In that case yes, start/stop is wearing, but it won't be triggered when you are actively compiling things for hours.

HDDs write/read has "no wear" (physically everything has wear, just that the wear tolerance here is negligible), and all SSDs writes has wears and can only be done a finite amount of times.

Compiling this for hours or even for days for low power machine is normal. It is a very big PBB, practically the biggest available. And Logos' compiler is very inefficient.

I've tried 4 times now to build the book and each time I've waited overnight, but nothing happens.  The PB just says "Converting", and the horizontal bar never moves.  It always starts out at about 1/5 complete, but then the bar never changes.  

Any ideas?

   And to John W

If on a PC check Power Settings.  When pugged in PC goes to sleep?  select NEVER.  Not sure that is the fix but worth a try to check.

Mine took 5 and a half hours.   

Well I have made the setting switch.  I am now at over 7 hours for compiling.  I do have an SSD, so didn't expect this much time.  The horizontal bar shows over 50% done now.  So we will see what happens.  The original email said something like 30 -90 minutes.  I am way longer than that, even with SSD and a fast Windows laptop.

Bob

Well it finally completed in around 9-10 hours, with an SSD.  And there are 63 errors and 10,258 warnings.

Here are a few of the warnings:

[Warning] Document contains Hebrew characters (“א”) that have not been tagged with a language code; they may not display in the proper order.
[Warning] Document contains Hebrew characters (“סב”) that have not been tagged with a language code; they may not display in the proper order.
[Warning] Document contains Hebrew characters (“למה”) that have not been tagged with a language code; they may not display in the proper order.
[Warning] Document contains Hebrew characters (“שש”) that have not been tagged with a language code; they may not display in the proper order.
[Warning] Document contains Hebrew characters (“אחוזי”) that have not been tagged with a language code; they may not display in the proper order.
[Warning] Document contains Hebrew characters (“שירי משכיל”) that have not been tagged with a language code; they may not display in the proper order.

And some of the errors:

[Error] Document contains an unsupported VML image which will not appear in the final document. To use this embedded image, open the document in Word, select “Save As...”, and deselect the “Maintain compatibility with previous versions of Word” option. Then rebuild the book.
[Error] Document contains an unsupported VML image which will not appear in the final document. To use this embedded image, open the document in Word, select “Save As...”, and deselect the “Maintain compatibility with previous versions of Word” option. Then rebuild the book.

[Error] Font 'Courier New' is not a valid font for use in resources.
[Error] Font 'Serto Urhoy' is not a valid font for use in resources.
[Error] Font 'Symbol' is not a valid font for use in resources.
[Error] Font 'Nyala' is not a valid font for use in resources.
[Error] Font 'Myanmar Text' is not a valid font for use in resources.
[Error] Font 'Wingdings' is not a valid font for use in resources.
[Error] Font 'Consolas' is not a valid font for use in resources.
[Error] Font 'Tahoma' is not a valid font for use in resources.
[Error] Font 'Mangal' is specified but not installed or embedded. Is this a valid font name?

Bob

7-9 hours later on a very fast gaming laptop with an ultra fast SSD, it worked.  I had given up after letting it run for 1 hr and then 2 hrs since my laptop is so fast.  What doesn't seem to work is the ability to "Upload" the file now that it's been built.  That is sad since rebuilding it takes so long.  No (easy) way to move it to my other computers running Logos ... a shame.  Looks really good though.

Hi Mark:

Yes, there is a size limit for uploaded PBs. I'm not sure what it is, but this one bursts it wide open.

This is what you do for your other computers:  Navigate to the Resource folder in your Logos data folder. In Windows, it's something like:  C:\Users\Robert\AppData\Local\Logos\Data\n2cbq2pd.jvv\ResourceManager\Resources.  Sort by size and find the largest '.lbspbb' file. It's likely the resource in question, but verify by date, also. (You could also find the full lbspbb file name in the Information window for the compiled resource, at the bottom.) Convey this file to each of your other computers via Dropbox, network copy, or something. If I were you, I would place in a folder with a very simple path, like 'C:\pbtemp'. In the Logos Command Box on each computer, type    scan c:\pbtemp   . Since the metadata syncs across desktops, all Logos needs is the compiled file.