S5 Slide show works OK under Mozilla but not on Explorer

Hi all, I am putting together a slide show of a large engineering project. S5 is the framework being used "http://meyerweb.com/eric/tools/s5/". The slide works great under Firefox, but its quite unexecptable under Microsofts Explorer. As the majority of the target audence would almost certainly be running windows, I appear to have a problem. THe way the slide show works is one changes frames with the page up/down keys. The frame is divided into three sections. The top section containing the comments to go with the image, the middle portion is the image, the lower section containing the overall title. Explorer takes no notice of this formating, not even using the selected fonts just displays a series of images with text in between them using whatever default font Exlploer has. Unfortunately although now running Linux for around 20 years I no nothing about web programming, or in this case xhtml and css what ever they are? :-(. Anything I can do? Help would very much be apreciated. Lindsay

You may find a lot of Windows users are also using either Firefox or Chrome. So may be less of a problem than you are anticipating. Also a good opportunity to promote users away from Explorer and to Firefox or Chrome. Viewers with an engineering background should not have much trouble using Chrome or Firefox. Cheers Daniel. PS: BTW this topic probably best on Luv-talk. On Thu, 30 Apr 2015 19:12:51 +1000 zlinw@mcmedia.com.au wrote:
Hi all,
I am putting together a slide show of a large engineering project. S5 is the framework being used "http://meyerweb.com/eric/tools/s5/". The slide works great under Firefox, but its quite unexecptable under Microsofts Explorer. As the majority of the target audence would almost certainly be running windows, I appear to have a problem.
THe way the slide show works is one changes frames with the page up/down keys. The frame is divided into three sections. The top section containing the comments to go with the image, the middle portion is the image, the lower section containing the overall title. Explorer takes no notice of this formating, not even using the selected fonts just displays a series of images with text in between them using whatever default font Exlploer has.
Unfortunately although now running Linux for around 20 years I no nothing about web programming, or in this case xhtml and css what ever they are? :-(.
Anything I can do? Help would very much be apreciated.
Lindsay _______________________________________________ luv-main mailing list luv-main@luv.asn.au http://lists.luv.asn.au/listinfo/luv-main
-- dan062 <dan062@yahoo.com.au>

On 30.04.15 21:43, Dan062 wrote:
PS: BTW this topic probably best on Luv-talk.
Surely not. How to use linux to achieve compatibility with less enlightened computer users must be 100% on-topic. My only related experience is trying to display html emails generated by an unenlightened vendor when firefox can't deal with the embedded "=E5"-style gibberish. I just put those messages through a couple of lines of awk, and the problem goes away. And the question did refer to sed, which is as old-unix as awk, and so nullifies __any__ hint of OT-ishness, I assure you. Erik

On Fri, May 01, 2015 at 04:47:55PM +1000, Erik Christiansen wrote:
My only related experience is trying to display html emails generated by an unenlightened vendor when firefox can't deal with the embedded "=E5"-style gibberish.
that "gibberish" is called quoted-printable[1]. it's not only used for html email. it's not even primarily used for that, it's one of the common methods for encoding messages containing 8-bit characters into 7-bit characters suitable for transmission by/through older MTAs that can't handle 8-bit mail. the most likely cause of firefox not being able to display it correctly is because the sender's MUA didn't set the correct mime-type header when creating the email...probably outlook or one of the many crappy, half-arsed MUAs on windows that don't bother implementing standards correctly. firefox has no problem with QP if the mime headers are set correctly...in fact, most if not all linux browsers and mail clients can decode and display it...most modern mail clients on any OS should be able to read and display QP, if not send it. [1] http://en.wikipedia.org/wiki/Quoted-printable "Quoted-Printable, or QP encoding, is an encoding using printable ASCII characters (alphanumeric and the equals sign "=") to transmit 8-bit data over a 7-bit data path or, generally, over a medium which is not 8-bit clean.[1] It is defined as a MIME content transfer encoding for use in e-mail. QP works by using the equals sign "=" as an escape character. It also limits line length to 76, as some software has limits on line length." the rest of the article is worth reading for an understanding of what QP is and how to encode/decode it correctly (in short, the number after the = sign is a 2-hex-digit number, 00-FF, specifying the 8-bit character) .
I just put those messages through a couple of lines of awk, and the problem goes away.
And the question did refer to sed, which is as old-unix as awk, and so nullifies __any__ hint of OT-ishness, I assure you.
it would probably be better and more reliable to write a simple perl filter using MIME::Decoder[2], which uses subclasss MIME::QuotedPrint::Perl[3] - the MIME:Decoder docs have an example filter in 3 lines of perl: use MIME::Decoder; $decoder = new MIME::Decoder 'quoted-printable' or die "unsupported"; $decoder->decode(\*STDIN, \*STDOUT); awk and/or sed can probably handle 90+% of cases, or at least make them less ugly to view. a decoder script should handle 100%, and convert them back to 8-bit text. [2] http://search.cpan.org/~dskoll/MIME-tools-5.505/lib/MIME/Decoder.pm [3] http://search.cpan.org/~gaas/MIME-Base64-3.15/QuotedPrint.pm craig -- craig sanders <cas@taz.net.au> BOFH excuse #360: Your parity check is overdrawn and you're out of cache.

On 01.05.15 17:24, Craig Sanders wrote:
it would probably be better and more reliable to write a simple perl filter using MIME::Decoder[2], which uses subclasss MIME::QuotedPrint::Perl[3] - the MIME:Decoder docs have an example filter in 3 lines of perl:
use MIME::Decoder;
$decoder = new MIME::Decoder 'quoted-printable' or die "unsupported"; $decoder->decode(\*STDIN, \*STDOUT);
awk and/or sed can probably handle 90+% of cases, or at least make them less ugly to view. a decoder script should handle 100%, and convert them back to 8-bit text.
Many thanks, Craig. I'll read the article, but I can't promise to do battle with perl. Too many years of too intimate familiarity with awk have made the pain of learning perl too much to endure. (Tried about a decade ago, even bought several books. Sold or gave away most of them.) You're right, the html pages were horribly ugly to view, but fixing half a dozen QP-isms renders them apparently flawless. (Perhaps I was lucky) <OT> With encroaching seniority, energy flags, and today it was more fun to put a new phase capacitor in the quarter-century old alternator for the farm, so it again generates 240v, rather than just 190v, which made it hard for fluoro's to light up. </OT> Erik

zlinw@mcmedia.com.au <zlinw@mcmedia.com.au> wrote:
I am putting together a slide show of a large engineering project. S5 is the framework being used "http://meyerweb.com/eric/tools/s5/". The slide works great under Firefox, but its quite unexecptable under Microsofts Explorer. As the majority of the target audence would almost certainly be running windows, I appear to have a problem.
More recent versions of Microsoft Internet Explorer are reputedly more compliant with standards than were earlier releases. If you aren't testing with the latest version, try upgrading. Every recent book on JavaScript programming that I've consulted tells the same story. They introduce a standard language feature or API, then say "Microsoft Internet Explorer (prior to version x) doesn't support it", or supports a non-standard feature instead, or has a major bug in its implmeentation of the standard. Sometimes these comments are made about other browsers, but it's mostly MSIE 8 and earlier. So, definitely try the latest release, or suggest to the recipients that they use Firefox, Chrome or something else.
participants (5)
-
Craig Sanders
-
Dan062
-
Erik Christiansen
-
Jason White
-
zlinw@mcmedia.com.au