Problem with gallery description

mercphoto

If you go to http://mercphoto.smugmug.com/gallery/730588 you will find that the first sentence is not a large font, even though I have inserted the font size = "+1" stuff in the description.

This was working yesterday. Oddly enough, the font directive for blue text is working.

colourbox

On a similar note, I inserted the high-ASCII code for a typographically correct apostrophe in a gallery description, and it worked in the old site but on the new site it displays the character codes literally. I have replaced it with a regular straight quote for now. It appears as if the new description is not interpreting HTML at all.

jfriend

It's coming out <font size=" 1">, not +1

mercphoto wrote:

If you go to http://mercphoto.smugmug.com/gallery/730588 you will find that the first sentence is not a large font, even though I have inserted the font size = "+1" stuff in the description.

This was working yesterday. Oddly enough, the font directive for blue text is working.

If you look at the generated HTML, it comes out with <font size=" 1">, with no plus character. You might check out your customization. If that's still got the plus in it, then maybe smugmug broke something that's changing the plus to a space. I did see some escape and unescape routines in their Javascript that do replace some chars with spaces, but I haven't studied it well enough to know if that's what is biting you. You might try using an absolute number that doens't need a "+" sign and see if that works better.

--John

jfriend

Try using the HTML code instead of the high-ascii char

colourbox wrote:

On a similar note, I inserted the high-ASCII code for a typographically correct apostrophe in a gallery description, and it worked in the old site but on the new site it displays the character codes literally. I have replaced it with a regular straight quote for now. It appears as if the new description is not interpreting HTML at all.

I don't know that this is your problem, but I would suggest using the HTML code for that character rather than the high-ascii code directly. See http://www.tedmontgomery.com/tutorial/HTMLchrc.html for a listing of those codes.

--John

colourbox

Looks like I was using the wrong terminology. I actually was entering the HTML code for the character (like I said, it worked great in the old smugmug). Thanks for the handy reference link by the way. I use a conversion utility but sometimes it's nice to have a table.

mercphoto

jfriend wrote:

If you look at the generated HTML, it comes out with <font size=" 1">, with no plus character.

And I keep putting it back in.

jfriend

ajaxDecode function looks like it could be causing your problem

mercphoto wrote:

And I keep putting it back in.

I'm guessing that this is a new bug related to the move to Ajax programming. I see in the JavaScript that there are JavaScript functions for escaping and unescaping of text strings. This function:

function ajaxDecode(str) {
return unescape(str.replace(/\+/g, " "));
} looks very suspicious because it's replacing the plus signs with a space and that's what is happening to you.

I think we need JT to weigh in here.

--John

{JT}

There is a slight problem with plus signs yes, but until we figure out a way to pass them back and not have the page break - use pixels instead <span style="font-size: 12px">text</span>

jfriend wrote:

I'm guessing that this is a new bug related to the move to Ajax programming. I see in the JavaScript that there are JavaScript functions for escaping and unescaping of text strings. This function:

function ajaxDecode(str) {
return unescape(str.replace(/\+/g, " "));
} looks very suspicious because it's replacing the plus signs with a space and that's what is happening to you.

I think we need JT to weigh in here.

--John