Anyone have correct PBB methods for the following problems?
Customer service referred me back to the web for the first of these three "problems":
1) When compiling a PBB with graphics, the .lbxoeb version that I upload to the forum appears to be missing the digrams (example: Traditional Bible Study Methods according to a forum user). The graphic are fine in the simultaneously compiled .lbxpbb file on my machine. Suggestions?
2) The auto-recognition of scriptural references fails inside <td> tags? I already use <span> tags to ensure that books beginning with a numeral work correctly but this doesn't fix the <td> problem. Any ideas short of manually tagging them?
3) I use a Dreamweaver template to create most of my PBB files. The template appears as comments within the HTML used to create the PBB. From feedback on the newsgroups this also seemed to create problems (unreadable file) in the .lbxoeb version while the .lbxpbb version worked fine. Any better idea that my removing the comments before compiling? This appears to "work" but can be a hassle for file maintenance. Any better ideas?
Thanks for your help.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
Comments
-
MJ. Smith said:
1) When compiling a PBB with graphics, the .lbxoeb version that I upload to the forum appears to be missing the digrams (example: Traditional Bible Study Methods according to a forum user). The graphic are fine in the simultaneously compiled .lbxpbb file on my machine. Suggestions?
What? An "lbxpbb" file is just a little xml file that keeps track of where your project files are located. How can the graphics be fine in that?
Well, anyway this is going to sound presumptuous but it sounds like you're using absolute urls in your image tags(e.g. a path like "C:/Documents and Settings/...da da da da da da...../myGraphic.gif" ) You need to use relative urls (just the file name), let the compiler discover the image file and take it from there. If you use an absolute path then the only machine that will be able to find the image will be your own.
That's probably not what you're doing but I thought I might as well mention it.
MJ. Smith said:2) The auto-recognition of scriptural references fails inside <td> tags? I already use <span> tags to ensure that books beginning with a numeral work correctly but this doesn't fix the <td> problem. Any ideas short of manually tagging them?
They do? I've never heard of that before. Better go check it out for myself. Let me just put you on hold for a second. You can listen to some beautiful music while I'm gone ....... "Gooood morning star shi-ine..... Glibby glop gloopy, Nibby nabby nooby..............."
There, I'm back.
Well what do you know? You're absolutely right. Auto tagging doesn't work inside of table cells. Unless you can get the troops at Logos to patch in a fix in a real hurry I don't see any other option but to manually tag them. I hope your table isn't huge. I hope I'm not driving you crazy with this very unhelpful advice.
Yours in Christ
John
0 -
John McComb said:MJ. Smith said:
1) When compiling a PBB with graphics, the .lbxoeb version that I upload to the forum appears to be missing the digrams (example: Traditional Bible Study Methods according to a forum user). The graphic are fine in the simultaneously compiled .lbxpbb file on my machine. Suggestions?
Well, anyway this is going to sound presumptuous but it sounds like you're using absolute urls in your image tags(e.g. a path like "C:/Documents and Settings/...da da da da da da...../myGraphic.gif" ) You need to use relative urls (just the file name), let the compiler discover the image file and take it from there. If you use an absolute path then the only machine that will be able to find the image will be your own.
Wait a minute. Come to think of it that's not as far fetched as I first thought since you're using DreamWeaver. DreamWeaver wants to be linked to a server and it has a habit of appending and prepending things to link and image urls. Even if you have it set up for relative links it will stick a slash on the beginning of your url string because that says "root directory" to your server. (I.E. it will change <img href="myGraphic.gif":> to <img href="/myGraphic.gif"> behind your back.). I don't know what kind of effect that will have on the PBB compiler but it might cause the problem you mentioned. You never know.
Yours in Christ
John
0 -
John McComb said:
Well, anyway this is going to sound presumptuous but it sounds like you're using absolute urls in your image tags(e.g. a path like "C:/Documents and Settings/...da da da da da da...../myGraphic.gif" ) You need to use relative urls (just the file name), let the compiler discover the image file and take it from there. If you use an absolute path then the only machine that will be able to find the image will be your own.
This is a possibility as I have not defined a root URL for the Dreamweaver project ... yup absolute it is ...<img src="file:///C|/Documents and Settings/name/My Documents/My Web/LayLiturgicalResources/Images/LBS_methods_forms/LBS_methods_application_2.jpg" ... so I'll try a relative URL and hope
Thanks.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Put the pictures in a subfolder named "images" of the pbb working folder, named "*", in the example following. Then PBB will have an easy time finding them and will incorporate them successfully. Example: G:\Libronix Personal Book Files\*\images0
-
John McComb said:
An "lbxpbb" file is just a little xml file that keeps track of where your project files are located. How can the graphics be fine in that?
Fascinating question ... unusually deep ... probably associated with red face ... you are correct; I am embarassed - I made an assumption based on the path used to open the file in Libronix and the assumption was very bad. And to think that I frequently had an employee put up a sign "don't assume" . Thanks
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
MJ. Smith said:
This is a possibility as I have not defined a root URL for the Dreamweaver project .
Yeah, well, good luck with that. Some of my favorite nightmares come from trying to get DreamWeaver to leave the stupid urls alone. I would protest loudly. "why on earth can't you just leave them the way I typed them? I set them that way for a reason". The program would balk and say, "Look buddy, I'm either going to set them to absolute paths on disk or prepend them with slashes and default image folder names. Take it or leave it, you whinny clown".
That was so long ago that I don't remember what I did to finally get the thing to behave the way I wanted it to or even if that's an accurate description of what I went through. However I do remember being very frustrated by this ridiculously overpriced product. Maybe, if you bought the package relatively recently, you won't have to go through the same headaches. My version is pretty old now.
Yours in Christ
John
0 -
John McComb said:
Maybe, if you bought the package relatively recently, you won't have to go through the same headaches. My version is pretty old now.
I'm on my third version of Dreamweaver which I get at an academic discount. I'd used the editor built into Netscape before that ... raise your hands if you remember Netscape! I've certainly had my fights with the Dreamweaver but I generally find the behavior predictable. I try not to even remember testing that little product from Redmond. I get so frustrated with Logos because I find its quirks to be unpredictable. I mean, if you are right on the root of the image problem, who would have "thunK" that the PBB compiler doesn't package the images with the text for distribution
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
MJ. Smith said:
simultaneously compiled .lbxpbb file on my machine
My BAD ... the lbxpbb file is simply a pointer to the .liboeb file ... the difference is between the behavior on my machine (the creator) and the distributed file. My apologies if I confused others.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
MJ. Smith said:
I'm on my third version of Dreamweaver which I get at an academic discount. I'd used the editor built into Netscape before that ... raise your hands if you remember Netscape! I've certainly had my fights with the Dreamweaver but I generally find the behavior predictable. I try not to even remember testing that little product from Redmond. I get so frustrated with Logos because I find its quirks to be unpredictable. I mean, if you are right on the root of the image problem, who would have "thunK" that the PBB compiler doesn't package the images with the text for distribution
It does. What it doesn't do is adjust absolute urls to point to images it discovers. They just get copied into the resource as is. Since the resource window is just a browser window it has no problem finding "file:///C:/Documents and Settings/... da da da da da da ..../image.jpg" when it's running on your machine because that file exists in that location on your machine. However on somebody else's machine the location probably doesn't even exist. If the image is in your PBB project folder and the compiler discovers it then it will copy the image into the resource. However, if you don't link to it with a simple file name or a path that has the project folder as it's root then the compiler isn't smart enough to associate that link to the discovered image file.
I don't know if this is the design intent of the product but it does have a happy side effect. That is, it allows you to make PBBs with links to other types of files (e.g. media files) that can't be discovered by PBB. For now the only types of files that can be discovered are HTML files, images and style sheets. If you want javascript in your projects you can only do it inline which, of course, limits severely what you can do. However you can do some nifty things like make expandable/collapsible contents menus and stuff like that.
Yours in Christ
John
0
