As far as I am aware, there in no difference in the handling of accented characters between v1.4.3.1 and v1.5.0 so the problem is likely to be caused by something else.

It looks like the first 4 images in your 'PreselectEIv15' gallery (the ones with accented characters) do not exist in their correct locations (or at all) on your web server.
If I try to view the 1st image in your gallery directly in a browser (bypassing Juicebox entirely), I get an error 404 (file not found).

Maybe something happened during the initial upload process that has resulted in the first 4 images not being uploaded to your web server.
Try re-uploading your v1.5.0 gallery's image files and you should hopefully see your images in your v1.5.0 gallery as you do in your v1.4.3.1 gallery.

Also, as an image filename forms part of a URL when uploaded to a web server, it would be wise to use only web-safe characters within image filenames. Please see section 2.3 of this document for details.

JuiceboxBuilder-Pro can handle all images whose filenames use any or all of these unreserved characters.

Stick to web-safe characters for filenames (rather than accented characters or other non-web-safe characters such as spaces) and continue to use accented characters in your image titles and captions and you should be fine.

Many thanks for providing the link to your gallery.

The problem is that you've set expandInNewPage="TRUE" (in conjunction with useFullscreenExpand="TRUE").
The gallery can be expanded either on top of its own embedding page (with useFullscreenExpand="TRUE" or useFullscreenExpand="TRUE") or on a new page of its own (by setting expandInNewPage="TRUE").
The gallery can be displayed using the Fullscreen API only when it is expanded on its own embedding page. (The Fullscreen API cannot be invoked when the gallery is expanded on a new page.)

Therefore, when expandInNewPage="TRUE", useFullscreenExpand is redundant and it not used.
Just set expandInNewPage="AUTO" (or remove the entry completely as the default value for this option is AUTO) and this should resolve your problem.

Incidentally, when expandInNewPage="TRUE" (and useFullscreenExpand is not used), the Expand Button will be displayed on the Button Bar only if the gallery is embedded at less that 100% x 100%.

Please let me know how you get on. Thank you.

[Posts split from Feature Request forum to new thread.]

Unfortunately, it is not possible to include image data in a gallery's embedding code.
Currently, every Juicebox gallery must have a separate JSON or XML configuration file, even if you use Flickr as a source of images (so imageURLs and thumbURLs are not required) and set all your configuration options in the embedding code.

I realise that this is not the answer that you were hoping for but it should at least clarify things for you.
Thank you for posting this as a suggestion in the Feature Requests forum thread (along with your other suggestion).

What you are describing is the Splash Page.
Please see this forum post for more information about the Splash Page (and how to use and configure it).

Your 'ngmsigns' gallery sets showSplashPage="AUTO" (Juicebox will display the Splash Page on mobile devices) whereas your 'gundogbreeds' gallery sets showSplashPage="NEVER".

If you set showSplashPage="NEVER" for your 'ngmsigns' gallery, (in JuiceboxBuilder-Pro's 'Customize -> Splash Page' section), then this should hopefully resolve your problem.

You're welcome. I hope it helps a bit.
Even if it's not a complete solution to your problem, it's perhaps a step in the right direction.

@support+juicebox

Thanks for the update! It's most appreciated.

No, unfortunately not. The only control you have over the preloading of images is the imagePreloading configuration option (in JuiceboxBuilder-Pro's 'Customize -> Main Image' section).

I think your issue is a direct consequence of setting enableLooping="TRUE".
Normally, Juicebox-Pro will preload both the previous and next images in the gallery (both images adjacent to the current image) so that they are ready to be displayed should the user click the 'previous' or 'next' navigation button.
If enableLooping="TRUE", then the previous image will be the last image in the gallery (in your case No. 9) and Juicebox just seems to preload this before No. 2, No. 3, etc.

As you are aware, large file sizes and a slow connection are also contributing factors.

As an example, if you were to create a gallery using JuiceboxBuilder-Pro with all default values, then the resulting image sizes would be around 120KB. With even just an 'average' connection speed, this would probably not be an issue.
However, real-life constraints (such as a slow connection speed) will certainly make a difference and you might need to counteract such factors by doing thing like reducing your image sizes (especially if you know that your gallery's target audience is likely to have a slow connection).

The other option would be to set enableLooping="FALSE". Perhaps not something you'd like to do in an ideal scenario but a compromise that would help to resolve your problem.

Please also see my notes regarding Muti-Size Image galleries in your other thread. They might be of interest to you.

If you'd like to suggest an idea for a future version, please feel free to post in the Feature Requests forum thread.
This keeps all the ideas together and ensures that they are not overlooked by the developers.
I do not know the likelihood of any suggestions being implemented but this is certainly the best place for all ideas.
Thank you.

Thank you for reporting this. It certainly looks like a bug (thumbnails do not AutoHide when showInfoButton="TRUE" and overlay is toggled off). I've notified the developers.

It looks like the problem is directly related to the Info Button so a workaround might be to set showInfoButton="FALSE".

If you still want to display the Button Bar but just don't want it to be overlaid on top of your images, you can set buttonBarPosition="TOP" (in JuiceboxBuilder-Pro's 'Customize -> Button Bar' section). The Button Bar will then always be positioned at the top of the gallery above the images (not on top of them). You can set the topAreaHeight (in JuiceboxBuilder-Pro's 'Customize -> General' section) if you like.

If you don't want the Button Bar to be displayed at all, then you can set buttonBarPosition="NONE" (in JuiceboxBuilder-Pro's 'Customize -> Button Bar' section).

Thanks again for reporting the problem.

If your web host is GoDaddy, then they provide your web space but where files and folders are uploaded to within your web space (and ultimately located) is up to you.
If you are not already using an FTP program to transfer your files from your computer to your web space, then I'd recommend trying one (such as Filezilla). Once you're logged into your hosting account, you'll be able to drag and drop files and folders from your computer into the FTP interface to upload them to wherever you like within your web space.

'public_html' is the name of the directory on your web server that represents your web root. ('public_html' does not form part of a URL.)
For example, if you upload a file named 'main.html' to your 'public_html' directory, then it will be accessible at http://adriannelugo.com/main.html.

As you seem to have followed the regular embedding instructions here, all you should need to do to have your http://adriannelugo.com/juicebox_portfolio.html gallery work correctly is upload the contents of your gallery folder to your web root directory (the 'public_html' directory). The gallery's 'images' folder should reside directly inside the 'public_html' directory (alongside the gallery's 'thumbs' folder).

As long as you follow the embedding instructions correctly, then there should be no need to change any paths in the embedding code (or elsewhere).
If you changed the structure of your gallery, then you could (if you wanted to):
(1) Use a configUrl in your embedding code to point towards a specific XML configuration file (if you have moved or renamed the gallery's 'config.xml' file).
(2) Use a baseUrl in your embedding code to point towards a complete gallery folder (if you have uploaded a complete gallery folder to your web server rather than just the contents of a gallery folder). The baseUrl method of embedding is documented here.

Short descriptions of configUrl and baseUrl can be found in the Embed Options section of the Config Options page.

The paths to the images themselves can be found inside the XML configuration file. (You can open a gallery's XML configuration file in a plain text editor and change the imageURL and thumbURL paths if you like.)
Relative paths are relative to the web page containing the gallery's embedding code (or a baseUrl if one is used).
(imageURL and thumbURL entries can be absolute as well as relative.)

All you should need to do though, is make sure that your gallery's 'images' folder is directly inside your 'public_html' directory, alongside your gallery's 'thumbs' folder. If it is already there, then check its permissions (as I suggested in my post above).
This should hopefully solve your problem.

The only other thing I can think of would be to start AutoPlay when the Juicebox-Pro API determines that the first image has been displayed for the first time (using the onImageChange event).
Try the following:

<!--START JUICEBOX EMBED-->
<script src="jbcore/juicebox.js"></script>
<script>
    var jb = new juicebox({
        containerId: "juicebox-container",
        autoPlayOnLoad: "FALSE",
        enableAutoPlay: "TRUE",
        goNextOnAutoPlay: "FALSE"
    });
    var flag = false;
    jb.onImageChange = function(e) {
        if (flag === false && e.id === 1) {
            jb.toggleAutoPlay();
            flag = true;
        }
    };
</script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->

If this still does not help, then you might need to use a setTimeout() delay (as I noted in my post above) or tweak your gallery's imagePreloading value and/or your image sizes (although I understand that you do not want to do this).

You can set configuration options in the gallery's XML file, in the embedding code or via a query string in the URL.
Please see the Setting Config Options support section for details.
If you have a certain configuration option set in both the embedding code and the XML file, then the value from the embedding code will take precedence. (Options set via the query string will override both embedding code and XML file options.)
I chose to add the configuration options required for my code to function correctly to the gallery's embedding code simply to keep my suggestion to a single chunk of code. You can set all your configuration options in your gallery's 'config.xml' file without any problem.

Yes. You can use whatever valid units you like in your custom CSS.

The reason that only px and % are accepted as galleryWidth and galleryHeight in the gallery's embedding code (as noted in your query here) is that Juicebox sanitizes the values (turning anything that is not a % into a px value) before using them internally as CSS.
Any custom CSS will be used by the browser as is.

For anyone looking to change the font size of gallery text, the following CSS may help. (Just change the values as necessary.)

/* IMAGE TITLE */
.jb-caption .jb-caption-title {
    font-size: 20px !important;
}

/* IMAGE CAPTION */
.jb-caption .jb-caption-desc {
    font-size: 18px !important;
}

/* IMAGE NUMBER */
.jb-cap-frame .jbac-number {
    font-size: 12px !important;
}

You could add this CSS to the end of your gallery's 'jbcore/classic/theme.css' file or wrap it in <style type="text/css"> ... </style> tags and add it to the end of your gallery web page's <head> section (to avoid the need to modify your gallery's 'theme.css' file).

If you do modify your gallery's 'theme.css' file, please remember to make a backup copy of your modified file as it may be overwritten if you upgrade your gallery when a new version of Juicebox is released.

@arachnid

The hash will only appear in the URL automatically (when loading a gallery or selecting a new image) if enableDirectLinks="TRUE".
However, at the moment, you will still be able to manually enter a hash value in a URL (to directly access an image) even if enableDirectLinks="FALSE". This has been logged as a bug and should hopefully be addressed in a future version.