Community @ The Turning Gate

Thanks, Ben. I guess then that it's not possible to define any equivalence; it's a matter of playing with the settings to see what results are achieved. As I said, I'm happy with the results I'm getting and probably will simply leave things as they are.

Thanks, Rod, for pointing that out. My template setting is 69% (possibly the default on implementation; I can't be sure if I changed it or not but probably not). And that was set up two months ago, easy to forget. What is the equivalent Lightroom value? As Jeffrey Friedl pointed out:

"Adding to the confusion for Lightroom users is the fact that Lightroom's JPEG quality setting is unique: it's different from every other photo-processing app I know, including other Adobe products. “Quality 73” in Lightroom, for example, is not the same as “Quality 73” in Photoshop or any other app that I know of."

The same photographs exported from Lightroom at Quality = 55 still add up to 7.8 MB.  Quality = 50 goes a bit weird and adds up to 7.99 MB. So, although the 69% I have set is affecting the results, something else is affecting the compression as well.

That works if a single image is selected, but I want the random selection which works at the lower level.

The problem appears in my test region where I'm implementing Backlight 2. Any photograph which contacts the black bar at the top of the screen; the hook in the "g" of my name is being cut off: http://charleskinghorn.com/bl2test/galleries/.

I have put all my font size changes into custom.css and removed the duplicate execution of this code. I have also reinstalled the Backlight 2 modules so that my earlier changes directly to the code have been removed. Right now I have two albums published in http://charleskinghorn.com/bl2test/galleries/, one with the caption and one without. In both cases the bottoms of the tallest vertical photographs are being truncated.

There is actually only one occurrence of custom.css in my code. Originally, when I started switching over to the Pangolin modules by rebuilding everything back in early December and introduced an Adobe typekit, I executed custom.css before and after the reference to the Adobe typkit because I thought it might be the solution to a problem I was having at the time. Actually at that point I had two versions of custom.css, custom and custom2 which ended up containing the same code. I deleted custom2.css and the first reference, the one before the Adobe typekit line; but it keeps showing up when I execute the code.

My code on the server:
function head() {
    echo'
    <link rel="stylesheet" type="text/css" href="https://use.typekit.net/mxy6glm.css">
    <link rel="stylesheet" href="/bl2test/backlight/custom/css/custom.css" />
    ';
}

The code on execution:
    <link rel="stylesheet" href="/bl2test/backlight/custom/css/custom.css" />
    <link rel="stylesheet" type="text/css" href="https://use.typekit.net/mxy6glm.css">
    <link rel="stylesheet" href="/bl2test/backlight/custom/css/custom.css" />

I don't know why the custom.css line appears before the Adobe one when I execute the code. It seems to be a ghost from the past.

You couldn't see the lower part of the "g" (the hook) being cut off? It's on my test version http://charleskinghorn.com/bl2test/galleries/. The worst case is 6 of 21. It's happening on all three of my browsers, Opera, Chrome, and Edge.

I have modified the font-size rem values in the following code:

figcaption php: to resize the fonts in the gallery descriptions in the descriptive thumbnail grid
fancybox.php: to affect the caption font size, but now reverted to the original 0.75rem
pallet_top_bottom.php: to resize the font for the copyright message at the bottom of each screen

The problem, of course, is that I will have to remake these changes with any upgrade to Backlight 2 which affects the changed code. Although I have spent many years programming, it has all been on the mainframe, not on PCs. I can make my way around the code in Backlight 2 sufficiently well to make these small changes; but I don't have enough experience to set up the necessary custom code from scratch.

The solution to one problem causes another. See http://community.theturninggate.net/vie … 445#p57445.

I am not sure, but my thinking is that the Adobe font that I am using for the text in my website is smaller than normal at 16px. That means that any text at .75rem is too small when displayed on the screen. This issue affected both the font size in the descriptive grid thumbnail entries and in the captions. I modified the code for both to get the size of text I wanted. Hence the 1.25rem for captions. I will have to play with it to see if I can get a balance where the caption is still readable without squinting; otherwise it goes.

It would seem to me that it might be a good idea to allow the user to set their own caption and thumbnail grid description font sizes instead of depending on a fixed fraction of the rem value.