Steven:

Thanks for your prompt and thorough reply.

Per the https://jalbum.net/forum/thread.jspa?messageID=318904 thread, here's some info for you:

- My filetypes.xml was properly configured, per the second post.

Per the fourth post:

- Settings > Pages, Copy originals if needed: already checked.

- Settings > Advanced > General, Exclude new images by default: already unchecked.

- Include xmp metadata in generated images: was checked, but I just unchecked it, and generated a new gallery. I didn't upload it to my server, but I did look at the generated folder on the Mac, and the PNG image was properly added to the hi-res folder. So that did the trick.

- Settings > Images > Advanced, Force JPEG writing: unchecked the entire time.

Which brings me to a follow-up question: should I care about "Include xmp metadata in generated images" setting?

That is, all these settings that you were talking about are ones that I just left at their default, haven't concerned myself with them, and so forth.

Additionally, that PNG file that I discovered was missing in my non-test gallery yesterday: I just copied the original PNG to the hi-res directory on the server. That took care of the problem, of course, and I can't recall messing with anything but JPG files in 100 or so galleries that I've put up.

Thus, is unchecking "Include xmp metadata in generated images" something that will have any side-effects that I should worry about?

Thanks again,

Bill P.

I didn't realize that much was involved. I thought maybe I was missing setting some option (although I reviewed them, before posting here) that would allow this.

Family viewers of my non-embedded galleries almost invariably want to take a closer look as some pic, and more or less instinctively these days try to pinch it larger. There's a YouTube video out there that I viewed a year or so ago: a toddler -- obviously used to playing with iPads and suchlike -- is given a paper magazine, with a printed picture showing, and the tyke is shown trying to do a pinch gesture on the picture.

In any event, thank you very much for the thorough explanation, and for your time.

Cheers,

Bill P.

Ah, yes, I should have been more specific.

Right you are, I had remembered that (one?) time, when the meta tag was updated. That precluded my using a Python script I wrote to replace my hundred or so jbcore directories (from a new jbcore folder I copy over to the server, upon new releases, for just that purpose -- see post https://juicebox.net/forum/viewtopic.php?id=147).

Since I use the jAlbum skin, "as is" -- no embedding or anything else tricky -- I guess I should go ahead and re-generate the galleries, since I gather I do, in fact, make use of the index.html jAlbum generates. (It's not as easy as using the Python script, because in the course of moving from a PC to a Mac, almost two years ago, I seemed to have lost track of some .jap files. OTOH, if I can't find them, they can't be that important to me and my occasional viewers.)

Thank you for your thorough and prompt answer.

Cheers,

Bill P.

Steven:

I use Juicebox Pro with the jAlbum skin, and have a specified languageList that I have saved in a sort of template that I use for my galleries. I open that template for each new gallery, and then do a Save As (name of new gallery), and then change the location of the source photos, etc.

Can't a similar methodology be employed when using JB Pro directly?

Cheers,

Bill P.

Thanks, Steven, for the thorough answer and for your time.

Cheers,

Bill P.

You bet. Thanks.

Well, that was intuitively obvious, that right-click (which, with my new one-button Mouse 2, is really a Control-click) on what appears to be a file. Yes, indeed, doing that, and expanding every returned folder in sight eventually results in finding this location:

/Applications/JuiceboxBuilder-Pro.app/Contents/Resources/template/jbcore/

What are you, a Mac expert in search of a Mac?

Nice research.

Cheers,

Bill P.

Steven:

What I did was to download the JB-Pro zip file again. I managed to butcher it, before I discovered that by default you move a file, instead of copy it, on a Mac.

Next, I ran jAlbum, with the Lite version of Juicebox installed. Then, I followed your instructions in the readme.txt that is included in the skin download (visible after changing that to a .zip file):

"To open the skin's folder, go to 'Tools -> Open Directories -> Skin directory' from jAlbum's drop-down menu."

That gave me a Finder window in the proper location. That location, by the way, is:

/Users/[user name]/Library/JAlbum/skins/Juicebox/res/Juicebox/jbcore

However, I can't seem to navigate to it myself, so I'm doing something wrong with Finder, or maybe it's some sort of alias, or maybe it's hidden to me. Doesn't matter, I got there courtesy of that menu instruction.

[Update: yeah, that particular Library folder is normal invisible. I installed Invisible -- https://www.macupdate.com/app/mac/47448/invisible -- which is easier than running assorted terminal commands. Now I can navigate directly to that location myself, but it's still easier to let jAlbum open it for me, as opposed to trying to remember that location myself.]

Then I closed jAlbum. Didn't want the skin open, but Finder was left open.

Then I ran another Finder, and opened the downloaded JB-Pro zip file. Now, having researched drag-and-copy better, I just dragged the jbcore from that Finder window to the one that was showing the skins folder (having navigated to the /juicebox/jbcore area).

Oh, yeah, I replaced spinner.gif there, too.

This was actually pretty easy, i.e., let jAlbum open a folder for me, and use the jbcore from the zip file for JB-Pro. I never did find out where jbcore is residing permanently, as part of JuiceboxBuilder-Pro, and I looked.

So, good suggestions you gave me, but it was ultimately the simple part of readme.txt that steered me in the right direction.

Thanks,

Bill P.

Sorry to trick you, re the vertical vs. horizontal. My eyes aren't what they used to be.

I'll just leave this alone, since I just got through updating a bunch of galleries for the viewport issue, and because it's not a big deal. If this is really a bug, I'll just wait for it to get fixed. Hopefully, the repair will just involve replacing the jbcore directories of the galleries with a new improved version (and so I can use my python script for that).

Thanks for your help.

Cheers,

Bill P.

The HTML validator at W3C -- https://validator.w3.org/ -- shows a few errors in the code. I'm not familiar with Lightroom, but you might want to address those errors, to see whether it makes a difference in the display.

Cheers,

Bill P.