I am trying to build out bullet points in keynote

I am doing a keynote presentation and want my bullets to disappear, one at a time, except one. Or have that one highlighted.
More than ___% of all kids are cute.
A. 6
B. 10
C. 20
D. 30
I want to highlight the question and the answer and have the other answers either fade or disappear.
Any ideas?

1   place text box with opening statement
2   place the responses;  A B C D in separate text boxes in a dark colour
3   place 4 other text boxes ; A B C D    directly on top of  dark text;  with either white text to disappear or gray boxes to shadow down
4   set up a build for each of the responses so that a text of box in gray appears on top of the bold text to create a shadow effect.
build 1 is the dark text of box A
build 2 is the gray text on top of box  B     etc
the bold text of each box is auto built  -  seen the arrows in the grab above
this grab shows the gray text on top of the bold text

Similar Messages

  • Has anyone worked out Bullet Point Indentation?

    Lets say i have four bullet point list of text. Some of the text goes on for two or three lines how do you sort this issue of getting them aligned?
    • Sample text here
    • Sample text here
    • Sample text here. This text goes on to
    the second line. So it is not aligned as it should be.
    • Sample text here
    The only way i cold achieve this was to create a second text box which only contains the bullet points and place that next to it. But there has to be an easier way. Anyone?
    Thanks.

    I am not at a computer so I cannot look at your files at the moment and typing code on a smartphone is no fun!So I would do it this way:
    sym.$("button").bind('mouseenter', function(){
    sym.$("button").css({'background-color':'black'});
    sym.$("button").bind('click',function(){
    sym.$("button").css({'background-color':'red'});
    I will look at your files tomorrow. I usually group buttons' code so it is more compact.
    On Tue, Nov 4, 2014 at 7:34 PM, majedsahi <[email protected]>

  • Bullet points in my website

    Hello,
    I'm in the middle of doing a website in Dreamweaver CS5, and i'm trying to get the bullet points to look nice.
    Unfortunately, it looks all out of whack. The problem is with the forth point (see snapshot), as there's 3 lines of text.
    I've created the points using padding and margins in the CSS definition rule box, which seems fine, until I have a point
    with more than 1 line of text. The points bunch up together.
    Can someone please tell me how to fix this? Attached is how it looks now (wrong!) and the second has been create in InDesign,
    and how i'd like it to look.
    please help!!
    Michael

    My guess is that you're using a background image and it is repeating.
    Use an unordered list and a list style image.
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
    <title>Unordered Lists</title>
    <style type="text/css">
    ul li {
    margin:0;
    width: 200px;
    padding: 6px 0 6px 0;
    li {list-style: url(your_bullet_img.gif);}
    </style>
    </head>
    <body>
    <ul>
    <li>list item </li>
    <li>list item that is much longer than the other list items</li>
    <li>list item </li>
    <li>list item </li>
    </ul>
    </body>
    </html>
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    http://twitter.com/altweb

  • Help needed with Microsoft Word - Bullet Points

    I recently bought a Macbook Pro and when I am trying to use the bullet points in Microsoft Word they come up as boxes instead of bullet points. Can anyone assist me? Thanks

    Go to File->Open Recent->Clear Recent and the 'recent' menu will be empty.
    Clinton

  • When I connect my MacBook Air to iPads through a powered USB hub the power cord for the hub explodes and trips the fuse on the building. I've tried different iPads, cords, power points to no avail.

    When I connect my mac air to some iPads through a powered USB hub for VPP/Configurator, the power point for the hub blows out (tripping the fuse in the building). I've tried different iPads, cords, power points and of course hubs. Also the computer has a habit of shutting down when any type of USB device is removed from it. Does anyone have any suggestions?

    I've done some experimenting, and this is what I've found out:
    1) The problem persists when I reformatted the USB HDD devices to ExFAT, so the problem apparently wasn't due to NTFS for Mac OS X by Paragon.
    2) The problem persists even when BackBlaze is paused, so I don't think that it's due to BackBlaze.
    3) The internet cuts out as soon as data begins transferring either to or from a USB HDD device and won't reconnected until I eject and unplug the device.
    4) The problem affects data transfers through either USB port.

  • Can I build in then build out before building in next bullet?

    I cannot figure out how to build in a bullet then build out said bullet before adding next bullet.

    This requires a separate text box for each line of text:
    add a text box to the slide
    enter the text for the first box
    add the in and out builds to the box
    duplicate the boxes for the required lines of text so the builds are the same as the first box
    add the text to the duplicated boxes

  • Trying to figure out difference between Access Point & Gateway

    Hello All,
    I am trying to figure out how to expand my home network and getting confused by the terms. The following is what I have for equipment"
    WRT 130N
    WRT 54GS
    4 hard wired assorted items hard wired to the 130N
    Here is what I want to do and not sure if I can do it:
    I would like to use the wireless side of the 54GS to connect to the wireless side of the 130N. By [lacing the 54GS on a different floor of our home  we will have four more hard wire ports to utilize for addition hardware we want to network.
    My questions are as follows:
    Is there a way that using the firmware in the 130N & 54GS to do this> The 54GS is V.7 and the 130N is only about six months old so it's the most current firmware. I am completely confused as to what the difference is between a gateway and an access point.
    Today was spent reading everything on the net about after market upgrades and in the end I am only more confused.
    Can anyone offer me some advise or guidance?
    Thanks,
    Ted

    access point:
    A device that allows wireless-equipped computers and other devices to communicate with a wired network. Also used to expand the range of a wireless network.
    gateway:
    A device that interconnects networks with different, incompatible communications protocols
    Analyzing the network environment that you want to create, is it?
    1. wrt130N )))))                                    (((((  wrt54gs  ))))                              ((((( 4 devices 
    2. wrt130N )))))                                    (((((  wrt54gs ----------------------------------------- 4 devices
    If it is figure 1. it is not possible, neither  figure 2. to  get it working that way, because wireless routers can only function as a wireless router, wired router and an access point.
    What you can do though is :
     wrt54gs- at least fw: 7.50.5   ))))))             ((((( wap54g - in repeater mode -  ))))))            (((((( pc
     wrt54gs- at least fw: 7.50.5   ))))))             ((((( wap54g - access point client mode- wrt130n - dhcp disabled  --------------------- 4 devices
    Take note though that wrt54gs has not been know to work with wpa54g access access point client mode
    Your best bet is to just wire wrt130n to wrt54gs and change the ip address of the latter to i.e. 192.168.5.1.
    " I can do all things through Christ which strengthens me. "

  • Trying to build HTMLDOC

    Hi all
    I'm trying to build HTMLDOC as part of my larger attempt to install FOG which is a free ghost clone. I'm running into a make error 1 presumably related to the png configuration. But if it is the png conf, I'm not sure how to pinpoint what part is causing the error. Your help is kindly appreciated.
    [indata@poweredge1600sc ~]$ cd htmldoc-1.8.27/
    [indata@poweredge1600sc htmldoc-1.8.27]$ sudo make
    [sudo] password for indata:
    Making all in htmldoc...
    Compiling image.cxx...
    In file included from /usr/include/pngconf.h:72:0,
    from /usr/include/png.h:446,
    from image.cxx:58:
    image.cxx: In function ‘int image_load_png(image_t*, FILE*, int, int)’:
    image.cxx:1502:16: error: invalid use of incomplete type ‘png_struct {aka struct png_struct_def}’
    if (setjmp(pp->jmpbuf))
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:556:16: error: forward declaration of ‘png_struct {aka struct png_struct_def}’
    typedef struct png_struct_def png_struct;
    ^
    image.cxx:1529:11: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    if (info->color_type & PNG_COLOR_MASK_PALETTE)
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1538:16: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    else if (info->bit_depth < 8)
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1543:16: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    else if (info->bit_depth == 16)
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1546:11: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    if (info->color_type & PNG_COLOR_MASK_COLOR)
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1557:21: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    img->width = info->width;
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1558:21: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    img->height = info->height;
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1560:12: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    if ((info->color_type & PNG_COLOR_MASK_ALPHA) || info->num_trans)
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1560:56: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    if ((info->color_type & PNG_COLOR_MASK_ALPHA) || info->num_trans)
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1597:34: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    rows = (png_bytep *)calloc(info->height, sizeof(png_bytep));
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1599:28: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    for (i = 0; i < (int)info->height; i ++)
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1613:12: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    if ((info->color_type & PNG_COLOR_MASK_ALPHA) || info->num_trans)
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1613:56: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    if ((info->color_type & PNG_COLOR_MASK_ALPHA) || info->num_trans)
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    image.cxx:1642:19: error: invalid use of incomplete type ‘png_info {aka struct png_info_def}’
    if (gray && info->color_type & PNG_COLOR_MASK_COLOR)
    ^
    In file included from image.cxx:58:0:
    /usr/include/png.h:570:16: error: forward declaration of ‘png_info {aka struct png_info_def}’
    typedef struct png_info_def png_info;
    ^
    make[1]: *** [image.o] Error 1
    [indata@poweredge1600sc htmldoc-1.8.27]$
    # "$Id: Makefile.in 1397 2005-04-24 19:20:32Z mike $"
    # Makefile for HTMLDOC, an HTML document processing program.
    # Copyright 1997-2005 by Easy Software Products.
    # These coded instructions, statements, and computer programs are the
    # property of Easy Software Products and are protected by Federal
    # copyright law. Distribution and use rights are outlined in the file
    # "COPYING.txt" which should have been included with this file. If this
    # file is missing or damaged please contact Easy Software Products
    # at:
    # Attn: ESP Licensing Information
    # Easy Software Products
    # 44141 Airport View Drive, Suite 204
    # Hollywood, Maryland 20636-3142 USA
    # Voice: (301) 373-9600
    # EMail: [email protected]
    # WWW: http://www.easysw.com
    # Include common definitions...
    include Makedefs
    # Software packaging...
    EPM = epm -v --output-dir dist
    # Subdirectories...
    DIRS = htmldoc doc
    INSTALLDIRS = fonts data doc htmldoc
    # Make all targets...
    all: Makedefs Makefile config.h htmldoc.list
    for dir in $(DIRS); do\
    echo Making all in $$dir...;\
    (cd $$dir; $(MAKE) -$(MAKEFLAGS)) || break;\
    done
    # Remove object and target files...
    clean:
    for dir in $(DIRS); do\
    echo Cleaning in $$dir...;\
    (cd $$dir; $(MAKE) -$(MAKEFLAGS) clean) || break;\
    done
    $(RM) *.bak
    $(RM) *.bck
    $(RM) core
    $(RM) core.*
    $(RM) -r autom4te*.cache
    $(RM) config.h config.log config.status
    # Install object and target files...
    install:
    $(MAKE) all
    for dir in $(INSTALLDIRS); do\
    echo Installing in $$dir...;\
    (cd $$dir; $(MAKE) -$(MAKEFLAGS) install) || break;\
    done
    # Makedefs
    Makedefs: Makedefs.in configure
    if test -f config.status; then \
    ./config.status --recheck; \
    ./config.status; \
    else \
    ./configure; \
    fi
    touch config.h
    # Makefile
    Makefile: Makefile.in configure
    if test -f config.status; then \
    ./config.status --recheck; \
    ./config.status; \
    else \
    ./configure; \
    fi
    touch config.h
    # config.h
    config.h: config.h.in configure
    if test -f config.status; then \
    ./config.status --recheck; \
    ./config.status; \
    else \
    ./configure; \
    fi
    touch config.h
    # htmldoc.list
    htmldoc.list: htmldoc.list.in configure
    if test -f config.status; then \
    ./config.status --recheck; \
    ./config.status; \
    else \
    ./configure; \
    fi
    touch config.h
    # Make a portable binary distribution using EPM.
    # EPM = ESP Package Manager, available at "http://www.easysw.com/epm/".
    epm:
    $(RM) -r dist
    $(EPM) htmldoc
    # End of "$Id: Makefile.in 1397 2005-04-24 19:20:32Z mike $".
    pngconf.h
    /* pngconf.h - machine configurable file for libpng
    * libpng version 1.2.7 - September 12, 2004
    * For conditions of distribution and use, see copyright notice in png.h
    * Copyright (c) 1998-2004 Glenn Randers-Pehrson
    * (Version 0.96 Copyright (c) 1996, 1997 Andreas Dilger)
    * (Version 0.88 Copyright (c) 1995, 1996 Guy Eric Schalnat, Group 42, Inc.)
    /* Any machine specific code is near the front of this file, so if you
    * are configuring libpng for a machine, you may want to read the section
    * starting here down to where it starts to typedef png_color, png_text,
    * and png_info.
    #ifndef PNGCONF_H
    #define PNGCONF_H
    #ifdef PNG_USER_CONFIG
    #include "pngusr.h"
    #endif
    /* This is the size of the compression buffer, and thus the size of
    * an IDAT chunk. Make this whatever size you feel is best for your
    * machine. One of these will be allocated per png_struct. When this
    * is full, it writes the data to the disk, and does some other
    * calculations. Making this an extremely small size will slow
    * the library down, but you may want to experiment to determine
    * where it becomes significant, if you are concerned with memory
    * usage. Note that zlib allocates at least 32Kb also. For readers,
    * this describes the size of the buffer available to read the data in.
    * Unless this gets smaller than the size of a row (compressed),
    * it should not make much difference how big this is.
    #ifndef PNG_ZBUF_SIZE
    # define PNG_ZBUF_SIZE 8192
    #endif
    /* Enable if you want a write-only libpng */
    #ifndef PNG_NO_READ_SUPPORTED
    # define PNG_READ_SUPPORTED
    #endif
    /* Enable if you want a read-only libpng */
    #ifndef PNG_NO_WRITE_SUPPORTED
    # define PNG_WRITE_SUPPORTED
    #endif
    /* Enabled by default in 1.2.0. You can disable this if you don't need to
    support PNGs that are embedded in MNG datastreams */
    #if !defined(PNG_1_0_X) && !defined(PNG_NO_MNG_FEATURES)
    # ifndef PNG_MNG_FEATURES_SUPPORTED
    # define PNG_MNG_FEATURES_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_FLOATING_POINT_SUPPORTED
    # ifndef PNG_FLOATING_POINT_SUPPORTED
    # define PNG_FLOATING_POINT_SUPPORTED
    # endif
    #endif
    /* If you are running on a machine where you cannot allocate more
    * than 64K of memory at once, uncomment this. While libpng will not
    * normally need that much memory in a chunk (unless you load up a very
    * large file), zlib needs to know how big of a chunk it can use, and
    * libpng thus makes sure to check any memory allocation to verify it
    * will fit into memory.
    #define PNG_MAX_MALLOC_64K
    #if defined(MAXSEG_64K) && !defined(PNG_MAX_MALLOC_64K)
    # define PNG_MAX_MALLOC_64K
    #endif
    /* Special munging to support doing things the 'cygwin' way:
    * 'Normal' png-on-win32 defines/defaults:
    * PNG_BUILD_DLL -- building dll
    * PNG_USE_DLL -- building an application, linking to dll
    * (no define) -- building static library, or building an
    * application and linking to the static lib
    * 'Cygwin' defines/defaults:
    * PNG_BUILD_DLL -- (ignored) building the dll
    * (no define) -- (ignored) building an application, linking to the dll
    * PNG_STATIC -- (ignored) building the static lib, or building an
    * application that links to the static lib.
    * ALL_STATIC -- (ignored) building various static libs, or building an
    * application that links to the static libs.
    * Thus,
    * a cygwin user should define either PNG_BUILD_DLL or PNG_STATIC, and
    * this bit of #ifdefs will define the 'correct' config variables based on
    * that. If a cygwin user *wants* to define 'PNG_USE_DLL' that's okay, but
    * unnecessary.
    * Also, the precedence order is:
    * ALL_STATIC (since we can't #undef something outside our namespace)
    * PNG_BUILD_DLL
    * PNG_STATIC
    * (nothing) == PNG_USE_DLL
    * CYGWIN (2002-01-20): The preceding is now obsolete. With the advent
    * of auto-import in binutils, we no longer need to worry about
    * __declspec(dllexport) / __declspec(dllimport) and friends. Therefore,
    * we don't need to worry about PNG_STATIC or ALL_STATIC when it comes
    * to __declspec() stuff. However, we DO need to worry about
    * PNG_BUILD_DLL and PNG_STATIC because those change some defaults
    * such as CONSOLE_IO and whether GLOBAL_ARRAYS are allowed.
    #if defined(__CYGWIN__)
    # if defined(ALL_STATIC)
    # if defined(PNG_BUILD_DLL)
    # undef PNG_BUILD_DLL
    # endif
    # if defined(PNG_USE_DLL)
    # undef PNG_USE_DLL
    # endif
    # if defined(PNG_DLL)
    # undef PNG_DLL
    # endif
    # if !defined(PNG_STATIC)
    # define PNG_STATIC
    # endif
    # else
    # if defined (PNG_BUILD_DLL)
    # if defined(PNG_STATIC)
    # undef PNG_STATIC
    # endif
    # if defined(PNG_USE_DLL)
    # undef PNG_USE_DLL
    # endif
    # if !defined(PNG_DLL)
    # define PNG_DLL
    # endif
    # else
    # if defined(PNG_STATIC)
    # if defined(PNG_USE_DLL)
    # undef PNG_USE_DLL
    # endif
    # if defined(PNG_DLL)
    # undef PNG_DLL
    # endif
    # else
    # if !defined(PNG_USE_DLL)
    # define PNG_USE_DLL
    # endif
    # if !defined(PNG_DLL)
    # define PNG_DLL
    # endif
    # endif
    # endif
    # endif
    #endif
    /* This protects us against compilers that run on a windowing system
    * and thus don't have or would rather us not use the stdio types:
    * stdin, stdout, and stderr. The only one currently used is stderr
    * in png_error() and png_warning(). #defining PNG_NO_CONSOLE_IO will
    * prevent these from being compiled and used. #defining PNG_NO_STDIO
    * will also prevent these, plus will prevent the entire set of stdio
    * macros and functions (FILE *, printf, etc.) from being compiled and used,
    * unless (PNG_DEBUG > 0) has been #defined.
    * #define PNG_NO_CONSOLE_IO
    * #define PNG_NO_STDIO
    #if defined(_WIN32_WCE)
    # include <windows.h>
    /* Console I/O functions are not supported on WindowsCE */
    # define PNG_NO_CONSOLE_IO
    # ifdef PNG_DEBUG
    # undef PNG_DEBUG
    # endif
    #endif
    #ifdef PNG_BUILD_DLL
    # ifndef PNG_CONSOLE_IO_SUPPORTED
    # ifndef PNG_NO_CONSOLE_IO
    # define PNG_NO_CONSOLE_IO
    # endif
    # endif
    #endif
    # ifdef PNG_NO_STDIO
    # ifndef PNG_NO_CONSOLE_IO
    # define PNG_NO_CONSOLE_IO
    # endif
    # ifdef PNG_DEBUG
    # if (PNG_DEBUG > 0)
    # include <stdio.h>
    # endif
    # endif
    # else
    # if !defined(_WIN32_WCE)
    /* "stdio.h" functions are not supported on WindowsCE */
    # include <stdio.h>
    # endif
    # endif
    /* This macro protects us against machines that don't have function
    * prototypes (ie K&R style headers). If your compiler does not handle
    * function prototypes, define this macro and use the included ansi2knr.
    * I've always been able to use _NO_PROTO as the indicator, but you may
    * need to drag the empty declaration out in front of here, or change the
    * ifdef to suit your own needs.
    #ifndef PNGARG
    #ifdef OF /* zlib prototype munger */
    # define PNGARG(arglist) OF(arglist)
    #else
    #ifdef _NO_PROTO
    # define PNGARG(arglist) ()
    # ifndef PNG_TYPECAST_NULL
    # define PNG_TYPECAST_NULL
    # endif
    #else
    # define PNGARG(arglist) arglist
    #endif /* _NO_PROTO */
    #endif /* OF */
    #endif /* PNGARG */
    /* Try to determine if we are compiling on a Mac. Note that testing for
    * just __MWERKS__ is not good enough, because the Codewarrior is now used
    * on non-Mac platforms.
    #ifndef MACOS
    # if (defined(__MWERKS__) && defined(macintosh)) || defined(applec) || \
    defined(THINK_C) || defined(__SC__) || defined(TARGET_OS_MAC)
    # define MACOS
    # endif
    #endif
    /* enough people need this for various reasons to include it here */
    #if !defined(MACOS) && !defined(RISCOS) && !defined(_WIN32_WCE)
    # include <sys/types.h>
    #endif
    #if !defined(PNG_SETJMP_NOT_SUPPORTED) && !defined(PNG_NO_SETJMP_SUPPORTED)
    # define PNG_SETJMP_SUPPORTED
    #endif
    #ifdef PNG_SETJMP_SUPPORTED
    /* This is an attempt to force a single setjmp behaviour on Linux. If
    * the X config stuff didn't define _BSD_SOURCE we wouldn't need this.
    # ifdef __linux__
    # ifdef _BSD_SOURCE
    # define PNG_SAVE_BSD_SOURCE
    # undef _BSD_SOURCE
    # endif
    # ifdef _SETJMP_H
    /* If you encounter a compiler error here, see the explanation
    * near the end of INSTALL.
    __png.h__ already includes setjmp.h;
    __dont__ include it again.;
    # endif
    # endif /* __linux__ */
    /* include setjmp.h for error handling */
    # include <setjmp.h>
    # ifdef __linux__
    # ifdef PNG_SAVE_BSD_SOURCE
    # define _BSD_SOURCE
    # undef PNG_SAVE_BSD_SOURCE
    # endif
    # endif /* __linux__ */
    #endif /* PNG_SETJMP_SUPPORTED */
    #ifdef BSD
    # include <strings.h>
    #else
    # include <string.h>
    #endif
    /* Other defines for things like memory and the like can go here. */
    #ifdef PNG_INTERNAL
    #include <stdlib.h>
    /* The functions exported by PNG_EXTERN are PNG_INTERNAL functions, which
    * aren't usually used outside the library (as far as I know), so it is
    * debatable if they should be exported at all. In the future, when it is
    * possible to have run-time registry of chunk-handling functions, some of
    * these will be made available again.
    #define PNG_EXTERN extern
    #define PNG_EXTERN
    /* Other defines specific to compilers can go here. Try to keep
    * them inside an appropriate ifdef/endif pair for portability.
    #if defined(PNG_FLOATING_POINT_SUPPORTED)
    # if defined(MACOS)
    /* We need to check that <math.h> hasn't already been included earlier
    * as it seems it doesn't agree with <fp.h>, yet we should really use
    * <fp.h> if possible.
    # if !defined(__MATH_H__) && !defined(__MATH_H) && !defined(__cmath__)
    # include <fp.h>
    # endif
    # else
    # include <math.h>
    # endif
    # if defined(_AMIGA) && defined(__SASC) && defined(_M68881)
    /* Amiga SAS/C: We must include builtin FPU functions when compiling using
    * MATH=68881
    # include <m68881.h>
    # endif
    #endif
    /* Codewarrior on NT has linking problems without this. */
    #if (defined(__MWERKS__) && defined(WIN32)) || defined(__STDC__)
    # define PNG_ALWAYS_EXTERN
    #endif
    /* This provides the non-ANSI (far) memory allocation routines. */
    #if defined(__TURBOC__) && defined(__MSDOS__)
    # include <mem.h>
    # include <alloc.h>
    #endif
    /* I have no idea why is this necessary... */
    #if defined(_MSC_VER) && (defined(WIN32) || defined(_Windows) || \
    defined(_WINDOWS) || defined(_WIN32) || defined(__WIN32__))
    # include <malloc.h>
    #endif
    /* This controls how fine the dithering gets. As this allocates
    * a largish chunk of memory (32K), those who are not as concerned
    * with dithering quality can decrease some or all of these.
    #ifndef PNG_DITHER_RED_BITS
    # define PNG_DITHER_RED_BITS 5
    #endif
    #ifndef PNG_DITHER_GREEN_BITS
    # define PNG_DITHER_GREEN_BITS 5
    #endif
    #ifndef PNG_DITHER_BLUE_BITS
    # define PNG_DITHER_BLUE_BITS 5
    #endif
    /* This controls how fine the gamma correction becomes when you
    * are only interested in 8 bits anyway. Increasing this value
    * results in more memory being used, and more pow() functions
    * being called to fill in the gamma tables. Don't set this value
    * less then 8, and even that may not work (I haven't tested it).
    #ifndef PNG_MAX_GAMMA_8
    # define PNG_MAX_GAMMA_8 11
    #endif
    /* This controls how much a difference in gamma we can tolerate before
    * we actually start doing gamma conversion.
    #ifndef PNG_GAMMA_THRESHOLD
    # define PNG_GAMMA_THRESHOLD 0.05
    #endif
    #endif /* PNG_INTERNAL */
    /* The following uses const char * instead of char * for error
    * and warning message functions, so some compilers won't complain.
    * If you do not want to use const, define PNG_NO_CONST here.
    #ifndef PNG_NO_CONST
    # define PNG_CONST const
    #else
    # define PNG_CONST
    #endif
    /* The following defines give you the ability to remove code from the
    * library that you will not be using. I wish I could figure out how to
    * automate this, but I can't do that without making it seriously hard
    * on the users. So if you are not using an ability, change the #define
    * to and #undef, and that part of the library will not be compiled. If
    * your linker can't find a function, you may want to make sure the
    * ability is defined here. Some of these depend upon some others being
    * defined. I haven't figured out all the interactions here, so you may
    * have to experiment awhile to get everything to compile. If you are
    * creating or using a shared library, you probably shouldn't touch this,
    * as it will affect the size of the structures, and this will cause bad
    * things to happen if the library and/or application ever change.
    /* Any features you will not be using can be undef'ed here */
    /* GR-P, 0.96a: Set "*TRANSFORMS_SUPPORTED as default but allow user
    * to turn it off with "*TRANSFORMS_NOT_SUPPORTED" or *PNG_NO_*_TRANSFORMS
    * on the compile line, then pick and choose which ones to define without
    * having to edit this file. It is safe to use the *TRANSFORMS_NOT_SUPPORTED
    * if you only want to have a png-compliant reader/writer but don't need
    * any of the extra transformations. This saves about 80 kbytes in a
    * typical installation of the library. (PNG_NO_* form added in version
    * 1.0.1c, for consistency)
    /* The size of the png_text structure changed in libpng-1.0.6 when
    * iTXt is supported. It is turned off by default, to support old apps
    * that malloc the png_text structure instead of calling png_set_text()
    * and letting libpng malloc it. It will be turned on by default in
    * libpng-1.3.0.
    #ifndef PNG_iTXt_SUPPORTED
    # if !defined(PNG_READ_iTXt_SUPPORTED) && !defined(PNG_NO_READ_iTXt)
    # define PNG_NO_READ_iTXt
    # endif
    # if !defined(PNG_WRITE_iTXt_SUPPORTED) && !defined(PNG_NO_WRITE_iTXt)
    # define PNG_NO_WRITE_iTXt
    # endif
    #endif
    /* The following support, added after version 1.0.0, can be turned off here en
    * masse by defining PNG_LEGACY_SUPPORTED in case you need binary compatibility
    * with old applications that require the length of png_struct and png_info
    * to remain unchanged.
    #ifdef PNG_LEGACY_SUPPORTED
    # define PNG_NO_FREE_ME
    # define PNG_NO_READ_UNKNOWN_CHUNKS
    # define PNG_NO_WRITE_UNKNOWN_CHUNKS
    # define PNG_NO_READ_USER_CHUNKS
    # define PNG_NO_READ_iCCP
    # define PNG_NO_WRITE_iCCP
    # define PNG_NO_READ_iTXt
    # define PNG_NO_WRITE_iTXt
    # define PNG_NO_READ_sCAL
    # define PNG_NO_WRITE_sCAL
    # define PNG_NO_READ_sPLT
    # define PNG_NO_WRITE_sPLT
    # define PNG_NO_INFO_IMAGE
    # define PNG_NO_READ_RGB_TO_GRAY
    # define PNG_NO_READ_USER_TRANSFORM
    # define PNG_NO_WRITE_USER_TRANSFORM
    # define PNG_NO_USER_MEM
    # define PNG_NO_READ_EMPTY_PLTE
    # define PNG_NO_MNG_FEATURES
    # define PNG_NO_FIXED_POINT_SUPPORTED
    #endif
    /* Ignore attempt to turn off both floating and fixed point support */
    #if !defined(PNG_FLOATING_POINT_SUPPORTED) || \
    !defined(PNG_NO_FIXED_POINT_SUPPORTED)
    # define PNG_FIXED_POINT_SUPPORTED
    #endif
    #ifndef PNG_NO_FREE_ME
    # define PNG_FREE_ME_SUPPORTED
    #endif
    #if defined(PNG_READ_SUPPORTED)
    #if !defined(PNG_READ_TRANSFORMS_NOT_SUPPORTED) && \
    !defined(PNG_NO_READ_TRANSFORMS)
    # define PNG_READ_TRANSFORMS_SUPPORTED
    #endif
    #ifdef PNG_READ_TRANSFORMS_SUPPORTED
    # ifndef PNG_NO_READ_EXPAND
    # define PNG_READ_EXPAND_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_SHIFT
    # define PNG_READ_SHIFT_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_PACK
    # define PNG_READ_PACK_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_BGR
    # define PNG_READ_BGR_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_SWAP
    # define PNG_READ_SWAP_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_PACKSWAP
    # define PNG_READ_PACKSWAP_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_INVERT
    # define PNG_READ_INVERT_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_DITHER
    # define PNG_READ_DITHER_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_BACKGROUND
    # define PNG_READ_BACKGROUND_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_16_TO_8
    # define PNG_READ_16_TO_8_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_FILLER
    # define PNG_READ_FILLER_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_GAMMA
    # define PNG_READ_GAMMA_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_GRAY_TO_RGB
    # define PNG_READ_GRAY_TO_RGB_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_SWAP_ALPHA
    # define PNG_READ_SWAP_ALPHA_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_INVERT_ALPHA
    # define PNG_READ_INVERT_ALPHA_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_STRIP_ALPHA
    # define PNG_READ_STRIP_ALPHA_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_USER_TRANSFORM
    # define PNG_READ_USER_TRANSFORM_SUPPORTED
    # endif
    # ifndef PNG_NO_READ_RGB_TO_GRAY
    # define PNG_READ_RGB_TO_GRAY_SUPPORTED
    # endif
    #endif /* PNG_READ_TRANSFORMS_SUPPORTED */
    #if !defined(PNG_NO_PROGRESSIVE_READ) && \
    !defined(PNG_PROGRESSIVE_READ_NOT_SUPPORTED) /* if you don't do progressive */
    # define PNG_PROGRESSIVE_READ_SUPPORTED /* reading. This is not talking */
    #endif /* about interlacing capability! You'll */
    /* still have interlacing unless you change the following line: */
    #define PNG_READ_INTERLACING_SUPPORTED /* required for PNG-compliant decoders */
    #ifndef PNG_NO_READ_COMPOSITE_NODIV
    # ifndef PNG_NO_READ_COMPOSITED_NODIV /* libpng-1.0.x misspelling */
    # define PNG_READ_COMPOSITE_NODIV_SUPPORTED /* well tested on Intel, SGI */
    # endif
    #endif
    /* Deprecated, will be removed from version 2.0.0.
    Use PNG_MNG_FEATURES_SUPPORTED instead. */
    #ifndef PNG_NO_READ_EMPTY_PLTE
    # define PNG_READ_EMPTY_PLTE_SUPPORTED
    #endif
    #endif /* PNG_READ_SUPPORTED */
    #if defined(PNG_WRITE_SUPPORTED)
    # if !defined(PNG_WRITE_TRANSFORMS_NOT_SUPPORTED) && \
    !defined(PNG_NO_WRITE_TRANSFORMS)
    # define PNG_WRITE_TRANSFORMS_SUPPORTED
    #endif
    #ifdef PNG_WRITE_TRANSFORMS_SUPPORTED
    # ifndef PNG_NO_WRITE_SHIFT
    # define PNG_WRITE_SHIFT_SUPPORTED
    # endif
    # ifndef PNG_NO_WRITE_PACK
    # define PNG_WRITE_PACK_SUPPORTED
    # endif
    # ifndef PNG_NO_WRITE_BGR
    # define PNG_WRITE_BGR_SUPPORTED
    # endif
    # ifndef PNG_NO_WRITE_SWAP
    # define PNG_WRITE_SWAP_SUPPORTED
    # endif
    # ifndef PNG_NO_WRITE_PACKSWAP
    # define PNG_WRITE_PACKSWAP_SUPPORTED
    # endif
    # ifndef PNG_NO_WRITE_INVERT
    # define PNG_WRITE_INVERT_SUPPORTED
    # endif
    # ifndef PNG_NO_WRITE_FILLER
    # define PNG_WRITE_FILLER_SUPPORTED /* same as WRITE_STRIP_ALPHA */
    # endif
    # ifndef PNG_NO_WRITE_SWAP_ALPHA
    # define PNG_WRITE_SWAP_ALPHA_SUPPORTED
    # endif
    # ifndef PNG_NO_WRITE_INVERT_ALPHA
    # define PNG_WRITE_INVERT_ALPHA_SUPPORTED
    # endif
    # ifndef PNG_NO_WRITE_USER_TRANSFORM
    # define PNG_WRITE_USER_TRANSFORM_SUPPORTED
    # endif
    #endif /* PNG_WRITE_TRANSFORMS_SUPPORTED */
    #define PNG_WRITE_INTERLACING_SUPPORTED /* not required for PNG-compliant
    encoders, but can cause trouble
    if left undefined */
    #if !defined(PNG_NO_WRITE_WEIGHTED_FILTER) && \
    defined(PNG_FLOATING_POINT_SUPPORTED)
    # define PNG_WRITE_WEIGHTED_FILTER_SUPPORTED
    #endif
    #ifndef PNG_NO_WRITE_FLUSH
    # define PNG_WRITE_FLUSH_SUPPORTED
    #endif
    /* Deprecated, see PNG_MNG_FEATURES_SUPPORTED, above */
    #ifndef PNG_NO_WRITE_EMPTY_PLTE
    # define PNG_WRITE_EMPTY_PLTE_SUPPORTED
    #endif
    #endif /* PNG_WRITE_SUPPORTED */
    #ifndef PNG_1_0_X
    # ifndef PNG_NO_ERROR_NUMBERS
    # define PNG_ERROR_NUMBERS_SUPPORTED
    # endif
    #endif /* PNG_1_0_X */
    #if defined(PNG_READ_USER_TRANSFORM_SUPPORTED) || \
    defined(PNG_WRITE_USER_TRANSFORM_SUPPORTED)
    # ifndef PNG_NO_USER_TRANSFORM_PTR
    # define PNG_USER_TRANSFORM_PTR_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_STDIO
    # define PNG_TIME_RFC1123_SUPPORTED
    #endif
    /* This adds extra functions in pngget.c for accessing data from the
    * info pointer (added in version 0.99)
    * png_get_image_width()
    * png_get_image_height()
    * png_get_bit_depth()
    * png_get_color_type()
    * png_get_compression_type()
    * png_get_filter_type()
    * png_get_interlace_type()
    * png_get_pixel_aspect_ratio()
    * png_get_pixels_per_meter()
    * png_get_x_offset_pixels()
    * png_get_y_offset_pixels()
    * png_get_x_offset_microns()
    * png_get_y_offset_microns()
    #if !defined(PNG_NO_EASY_ACCESS) && !defined(PNG_EASY_ACCESS_SUPPORTED)
    # define PNG_EASY_ACCESS_SUPPORTED
    #endif
    /* PNG_ASSEMBLER_CODE was enabled by default in version 1.2.0
    even when PNG_USE_PNGVCRD or PNG_USE_PNGGCCRD is not defined */
    #if defined(PNG_READ_SUPPORTED) && !defined(PNG_NO_ASSEMBLER_CODE)
    # ifndef PNG_ASSEMBLER_CODE_SUPPORTED
    # define PNG_ASSEMBLER_CODE_SUPPORTED
    # endif
    # if !defined(PNG_MMX_CODE_SUPPORTED) && !defined(PNG_NO_MMX_CODE)
    # define PNG_MMX_CODE_SUPPORTED
    # endif
    #endif
    /* If you are sure that you don't need thread safety and you are compiling
    with PNG_USE_PNGCCRD for an MMX application, you can define this for
    faster execution. See pnggccrd.c.
    #define PNG_THREAD_UNSAFE_OK
    #if !defined(PNG_1_0_X)
    #if !defined(PNG_NO_USER_MEM) && !defined(PNG_USER_MEM_SUPPORTED)
    # define PNG_USER_MEM_SUPPORTED
    #endif
    #endif /* PNG_1_0_X */
    /* Added at libpng-1.2.6 */
    #if !defined(PNG_1_0_X)
    #ifndef PNG_SET_USER_LIMITS_SUPPORTED
    #if !defined(PNG_NO_SET_USER_LIMITS) && !defined(PNG_SET_USER_LIMITS_SUPPORTED)
    # define PNG_SET_USER_LIMITS_SUPPORTED
    #endif
    #endif
    #endif /* PNG_1_0_X */
    /* Added at libpng-1.0.16 and 1.2.6. To accept all valid PNGS no matter
    * how large, set these limits to 0x7fffffffL
    #ifndef PNG_USER_WIDTH_MAX
    # define PNG_USER_WIDTH_MAX 1000000L
    #endif
    #ifndef PNG_USER_HEIGHT_MAX
    # define PNG_USER_HEIGHT_MAX 1000000L
    #endif
    /* These are currently experimental features, define them if you want */
    /* very little testing */
    #ifdef PNG_READ_SUPPORTED
    # ifndef PNG_READ_16_TO_8_ACCURATE_SCALE_SUPPORTED
    # define PNG_READ_16_TO_8_ACCURATE_SCALE_SUPPORTED
    # endif
    #endif
    /* This is only for PowerPC big-endian and 680x0 systems */
    /* some testing */
    #ifndef PNG_READ_BIG_ENDIAN_SUPPORTED
    # define PNG_READ_BIG_ENDIAN_SUPPORTED
    #endif
    /* Buggy compilers (e.g., gcc 2.7.2.2) need this */
    #define PNG_NO_POINTER_INDEXING
    /* These functions are turned off by default, as they will be phased out. */
    #define PNG_USELESS_TESTS_SUPPORTED
    #define PNG_CORRECT_PALETTE_SUPPORTED
    /* Any chunks you are not interested in, you can undef here. The
    * ones that allocate memory may be expecially important (hIST,
    * tEXt, zTXt, tRNS, pCAL). Others will just save time and make png_info
    * a bit smaller.
    #if defined(PNG_READ_SUPPORTED) && \
    !defined(PNG_READ_ANCILLARY_CHUNKS_NOT_SUPPORTED) && \
    !defined(PNG_NO_READ_ANCILLARY_CHUNKS)
    # define PNG_READ_ANCILLARY_CHUNKS_SUPPORTED
    #endif
    #if defined(PNG_WRITE_SUPPORTED) && \
    !defined(PNG_WRITE_ANCILLARY_CHUNKS_NOT_SUPPORTED) && \
    !defined(PNG_NO_WRITE_ANCILLARY_CHUNKS)
    # define PNG_WRITE_ANCILLARY_CHUNKS_SUPPORTED
    #endif
    #ifdef PNG_READ_ANCILLARY_CHUNKS_SUPPORTED
    #ifdef PNG_NO_READ_TEXT
    # define PNG_NO_READ_iTXt
    # define PNG_NO_READ_tEXt
    # define PNG_NO_READ_zTXt
    #endif
    #ifndef PNG_NO_READ_bKGD
    # define PNG_READ_bKGD_SUPPORTED
    # define PNG_bKGD_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_cHRM
    # define PNG_READ_cHRM_SUPPORTED
    # define PNG_cHRM_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_gAMA
    # define PNG_READ_gAMA_SUPPORTED
    # define PNG_gAMA_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_hIST
    # define PNG_READ_hIST_SUPPORTED
    # define PNG_hIST_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_iCCP
    # define PNG_READ_iCCP_SUPPORTED
    # define PNG_iCCP_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_iTXt
    # ifndef PNG_READ_iTXt_SUPPORTED
    # define PNG_READ_iTXt_SUPPORTED
    # endif
    # ifndef PNG_iTXt_SUPPORTED
    # define PNG_iTXt_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_READ_oFFs
    # define PNG_READ_oFFs_SUPPORTED
    # define PNG_oFFs_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_pCAL
    # define PNG_READ_pCAL_SUPPORTED
    # define PNG_pCAL_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_sCAL
    # define PNG_READ_sCAL_SUPPORTED
    # define PNG_sCAL_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_pHYs
    # define PNG_READ_pHYs_SUPPORTED
    # define PNG_pHYs_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_sBIT
    # define PNG_READ_sBIT_SUPPORTED
    # define PNG_sBIT_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_sPLT
    # define PNG_READ_sPLT_SUPPORTED
    # define PNG_sPLT_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_sRGB
    # define PNG_READ_sRGB_SUPPORTED
    # define PNG_sRGB_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_tEXt
    # define PNG_READ_tEXt_SUPPORTED
    # define PNG_tEXt_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_tIME
    # define PNG_READ_tIME_SUPPORTED
    # define PNG_tIME_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_tRNS
    # define PNG_READ_tRNS_SUPPORTED
    # define PNG_tRNS_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_zTXt
    # define PNG_READ_zTXt_SUPPORTED
    # define PNG_zTXt_SUPPORTED
    #endif
    #ifndef PNG_NO_READ_UNKNOWN_CHUNKS
    # define PNG_READ_UNKNOWN_CHUNKS_SUPPORTED
    # ifndef PNG_UNKNOWN_CHUNKS_SUPPORTED
    # define PNG_UNKNOWN_CHUNKS_SUPPORTED
    # endif
    # ifndef PNG_NO_HANDLE_AS_UNKNOWN
    # define PNG_HANDLE_AS_UNKNOWN_SUPPORTED
    # endif
    #endif
    #if !defined(PNG_NO_READ_USER_CHUNKS) && \
    defined(PNG_READ_UNKNOWN_CHUNKS_SUPPORTED)
    # define PNG_READ_USER_CHUNKS_SUPPORTED
    # define PNG_USER_CHUNKS_SUPPORTED
    # ifdef PNG_NO_READ_UNKNOWN_CHUNKS
    # undef PNG_NO_READ_UNKNOWN_CHUNKS
    # endif
    # ifdef PNG_NO_HANDLE_AS_UNKNOWN
    # undef PNG_NO_HANDLE_AS_UNKNOWN
    # endif
    #endif
    #ifndef PNG_NO_READ_OPT_PLTE
    # define PNG_READ_OPT_PLTE_SUPPORTED /* only affects support of the */
    #endif /* optional PLTE chunk in RGB and RGBA images */
    #if defined(PNG_READ_iTXt_SUPPORTED) || defined(PNG_READ_tEXt_SUPPORTED) || \
    defined(PNG_READ_zTXt_SUPPORTED)
    # define PNG_READ_TEXT_SUPPORTED
    # define PNG_TEXT_SUPPORTED
    #endif
    #endif /* PNG_READ_ANCILLARY_CHUNKS_SUPPORTED */
    #ifdef PNG_WRITE_ANCILLARY_CHUNKS_SUPPORTED
    #ifdef PNG_NO_WRITE_TEXT
    # define PNG_NO_WRITE_iTXt
    # define PNG_NO_WRITE_tEXt
    # define PNG_NO_WRITE_zTXt
    #endif
    #ifndef PNG_NO_WRITE_bKGD
    # define PNG_WRITE_bKGD_SUPPORTED
    # ifndef PNG_bKGD_SUPPORTED
    # define PNG_bKGD_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_cHRM
    # define PNG_WRITE_cHRM_SUPPORTED
    # ifndef PNG_cHRM_SUPPORTED
    # define PNG_cHRM_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_gAMA
    # define PNG_WRITE_gAMA_SUPPORTED
    # ifndef PNG_gAMA_SUPPORTED
    # define PNG_gAMA_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_hIST
    # define PNG_WRITE_hIST_SUPPORTED
    # ifndef PNG_hIST_SUPPORTED
    # define PNG_hIST_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_iCCP
    # define PNG_WRITE_iCCP_SUPPORTED
    # ifndef PNG_iCCP_SUPPORTED
    # define PNG_iCCP_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_iTXt
    # ifndef PNG_WRITE_iTXt_SUPPORTED
    # define PNG_WRITE_iTXt_SUPPORTED
    # endif
    # ifndef PNG_iTXt_SUPPORTED
    # define PNG_iTXt_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_oFFs
    # define PNG_WRITE_oFFs_SUPPORTED
    # ifndef PNG_oFFs_SUPPORTED
    # define PNG_oFFs_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_pCAL
    # define PNG_WRITE_pCAL_SUPPORTED
    # ifndef PNG_pCAL_SUPPORTED
    # define PNG_pCAL_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_sCAL
    # define PNG_WRITE_sCAL_SUPPORTED
    # ifndef PNG_sCAL_SUPPORTED
    # define PNG_sCAL_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_pHYs
    # define PNG_WRITE_pHYs_SUPPORTED
    # ifndef PNG_pHYs_SUPPORTED
    # define PNG_pHYs_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_sBIT
    # define PNG_WRITE_sBIT_SUPPORTED
    # ifndef PNG_sBIT_SUPPORTED
    # define PNG_sBIT_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_sPLT
    # define PNG_WRITE_sPLT_SUPPORTED
    # ifndef PNG_sPLT_SUPPORTED
    # define PNG_sPLT_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_sRGB
    # define PNG_WRITE_sRGB_SUPPORTED
    # ifndef PNG_sRGB_SUPPORTED
    # define PNG_sRGB_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_tEXt
    # define PNG_WRITE_tEXt_SUPPORTED
    # ifndef PNG_tEXt_SUPPORTED
    # define PNG_tEXt_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_tIME
    # define PNG_WRITE_tIME_SUPPORTED
    # ifndef PNG_tIME_SUPPORTED
    # define PNG_tIME_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_tRNS
    # define PNG_WRITE_tRNS_SUPPORTED
    # ifndef PNG_tRNS_SUPPORTED
    # define PNG_tRNS_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_zTXt
    # define PNG_WRITE_zTXt_SUPPORTED
    # ifndef PNG_zTXt_SUPPORTED
    # define PNG_zTXt_SUPPORTED
    # endif
    #endif
    #ifndef PNG_NO_WRITE_UNKNOWN_CHUNKS
    # define PNG_WRITE_UNKNOWN_CHUNKS_SUPPORTED
    # ifndef PNG_UNKNOWN_CHUNKS_SUPPORTED
    # define PNG_UNKNOWN_CHUNKS_SUPPORTED
    # endif
    # ifndef PNG_NO_HANDLE_AS_UNKNOWN
    # ifndef PNG_HANDLE_AS_UNKNOWN_SUPPORTED
    # define PNG_HANDLE_AS_UNKNOWN_SUPPORTED
    # endif
    # endif
    #endif
    #if defined(PNG_WRITE_iTXt_SUPPORTED) || defined(PNG_WRITE_tEXt_SUPPORTED) || \
    defined(PNG_WRITE_zTXt_SUPPORTED)
    # define PNG_WRITE_TEXT_SUPPORTED
    # ifndef PNG_TEXT_SUPPORTED
    # define PNG_TEXT_SUPPORTED
    # endif
    #endif
    #endif /* PNG_WRITE_ANCILLARY_CHUNKS_SUPPORTED */
    /* Turn this off to disable png_read_png() and
    * png_write_png() and leave the row_pointers member
    * out of the info structure.
    #ifndef PNG_NO_INFO_IMAGE
    # define PNG_INFO_IMAGE_SUPPORTED
    #endif
    /* need the time information for reading tIME chunks */
    #if defined(PNG_tIME_SUPPORTED)
    # if !defined(_WIN32_WCE)
    /* "time.h" functions are not supported on WindowsCE */
    # include <time.h>
    # endif
    #endif
    /* Some typedefs to get us started. These should be safe on most of the
    * common platforms. The typedefs should be at least as large as the
    * numbers suggest (a png_uint_32 must be at least 32 bits long), but they
    * don't have to be exactly that size. Some compilers dislike passing
    * unsigned shorts as function parameters, so you may be better off using
    * unsigned int for png_uint_16. Likewise, for 64-bit systems, you may
    * want to have unsigned int for png_uint_32 instead of unsigned long.
    typedef unsigned long png_uint_32;
    typedef long png_int_32;
    typedef unsigned short png_uint_16;
    typedef short png_int_16;
    typedef unsigned char png_byte;
    /* This is usually size_t. It is typedef'ed just in case you need it to
    change (I'm not sure if you will or not, so I thought I'd be safe) */
    #ifdef PNG_SIZE_T
    typedef PNG_SIZE_T png_size_t;
    # define png_sizeof(x) png_convert_size(sizeof (x))
    #else
    typedef size_t png_size_t;
    # define png_sizeof(x) sizeof (x)
    #endif
    /* The following is needed for medium model support. It cannot be in the
    * PNG_INTERNAL section. Needs modification for other compilers besides
    * MSC. Model independent support declares all arrays and pointers to be
    * large using the far keyword. The zlib version used must also support
    * model independent data. As of version zlib 1.0.4, the necessary changes
    * have been made in zlib. The USE_FAR_KEYWORD define triggers other
    * changes that are needed. (Tim Wegner)
    /* Separate compiler dependencies (problem here is that zlib.h always
    defines FAR. (SJT) */
    #ifdef __BORLANDC__
    # if defined(__LARGE__) || defined(__HUGE__) || defined(__COMPACT__)
    # define LDATA 1
    # else
    # define LDATA 0
    # endif
    /* GRR: why is Cygwin in here? Cygwin is not Borland C... */
    # if !defined(__WIN32__) && !defined(__FLAT__) && !defined(__CYGWIN__)
    # define PNG_MAX_MALLOC_64K
    # if (LDATA != 1)
    # ifndef FAR
    # define FAR __far
    # endif
    # define USE_FAR_KEYWORD
    # endif /* LDATA != 1 */
    /* Possibly useful for moving data out of default segment.
    * Uncomment it if you want. Could also define FARDATA as
    * const if your compiler supports it. (SJT)
    # define FARDATA FAR
    # endif /* __WIN32__, __FLAT__, __CYGWIN__ */
    #endif /* __BORLANDC__ */
    /* Suggest testing for specific compiler first before testing for
    * FAR. The Watcom compiler defines both __MEDIUM__ and M_I86MM,
    * making reliance oncertain keywords suspect. (SJT)
    /* MSC Medium model */
    #if defined(FAR)
    # if defined(M_I86MM)
    # define USE_FAR_KEYWORD
    # define FARDATA FAR
    # include <dos.h>
    # endif
    #endif
    /* SJT: default case */
    #ifndef FAR
    # define FAR
    #endif
    /* At this point FAR is always defined */
    #ifndef FARDATA
    # define FARDATA
    #endif
    /* Typedef for floating-point numbers that are converted
    to fixed-point with a multiple of 100,000, e.g., int_gamma */
    typedef png_int_32 png_fixed_point;
    /* Add typedefs for pointers */
    typedef void FAR * png_voidp;
    typedef png_byte FAR * png_bytep;
    typedef png_uint_32 FAR * png_uint_32p;
    typedef png_int_32 FAR * png_int_32p;
    typedef png_uint_16 FAR * png_uint_16p;
    typedef png_int_16 FAR * png_int_16p;
    typedef PNG_CONST char FAR * png_const_charp;
    typedef char FAR * png_charp;
    typedef png_fixed_point FAR * png_fixed_point_p;
    #ifndef PNG_NO_STDIO
    #if defined(_WIN32_WCE)
    typedef HANDLE png_FILE_p;
    #else
    typedef FILE * png_FILE_p;
    #endif
    #endif
    #ifdef PNG_FLOATING_POINT_SUPPORTED
    typedef double FAR * png_doublep;
    #endif
    /* Pointers to pointers; i.e. arrays */
    typedef png_byte FAR * FAR * png_bytepp;
    typedef png_uint_32 FAR * FAR * png_uint_32pp;
    typedef png_int_32 FAR * FAR * png_int_32pp;
    typedef png_uint_16 FAR * FAR * png_uint_16pp;
    typedef png_int_16 FAR * FAR * png_int_16pp;
    typedef PNG_CONST char FAR * FAR * png_const_charpp;
    typedef char FAR * FAR * png_charpp;
    typedef png_fixed_point FAR * FAR * png_fixed_point_pp;
    #ifdef PNG_FLOATING_POINT_SUPPORTED
    typedef double FAR * FAR * png_doublepp;
    #endif
    /* Pointers to pointers to pointers; i.e., pointer to array */
    typedef char FAR * FAR * FAR * png_charppp;
    /* libpng typedefs for types in zlib. If zlib changes
    * or another compression library is used, then change these.
    * Eliminates need to change all the source files.
    typedef charf * png_zcharp;
    typedef charf * FAR * png_zcharpp;
    typedef z_stream FAR * png_zstreamp;
    * Define PNG_BUILD_DLL if the module being built is a Windows
    * LIBPNG DLL.
    * Define PNG_USE_DLL if you want to *link* to the Windows LIBPNG DLL.
    * It is equivalent to Microsoft predefined macro _DLL that is
    * automatically defined when you compile using the share
    * version of the CRT (C Run-Time library)
    * The cygwin mods make this behavior a little different:
    * Define PNG_BUILD_DLL if you are building a dll for use with cygwin
    * Define PNG_STATIC if you are building a static library for use with cygwin,
    * -or- if you are building an application that you want to link to the
    * static library.
    * PNG_USE_DLL is defined by default (no user action needed) unless one of
    * the other flags is defined.
    #if !defined(PNG_DLL) && (defined(PNG_BUILD_DLL) || defined(PNG_USE_DLL))
    # define PNG_DLL
    #endif
    /* If CYGWIN, then disallow GLOBAL ARRAYS unless building a static lib.
    * When building a static lib, default to no GLOBAL ARRAYS, but allow
    * command-line override
    #if defined(__CYGWIN__)
    # if !defined(PNG_STATIC)
    # if defined(PNG_USE_GLOBAL_ARRAYS)
    # undef PNG_USE_GLOBAL_ARRAYS
    # endif
    # if !defined(PNG_USE_LOCAL_ARRAYS)
    # define PNG_USE_LOCAL_ARRAYS
    # endif
    # else
    # if defined(PNG_USE_LOCAL_ARRAYS) || defined(PNG_NO_GLOBAL_ARRAYS)
    # if defined(PNG_USE_GLOBAL_ARRAYS)
    # undef PNG_USE_GLOBAL_ARRAYS
    # endif
    # endif
    # endif
    # if !defined(PNG_USE_LOCAL_ARRAYS) && !defined(PNG_USE_GLOBAL_ARRAYS)
    # define PNG_USE_LOCAL_ARRAYS
    # endif
    #endif
    /* Do not use global arrays (helps with building DLL's)
    * They are no longer used in libpng itself, since version 1.0.5c,
    * but might be required for some pre-1.0.5c applications.
    #if !defined(PNG_USE_LOCAL_ARRAYS) && !defined(PNG_USE_GLOBAL_ARRAYS)
    # if defined(PNG_NO_GLOBAL_ARRAYS) || (defined(__GNUC__) && defined(PNG_DLL))
    # define PNG_USE_LOCAL_ARRAYS
    # else
    # define PNG_USE_GLOBAL_ARRAYS
    # endif
    #endif
    #if defined(__CYGWIN__)
    # undef PNGAPI
    # define PNGAPI __cdecl
    # undef PNG_IMPEXP
    # define PNG_IMPEXP
    #endif
    /* If you define PNGAPI, e.g., with compiler option "-DPNGAPI=__stdcall",
    * you may get warnings regarding the linkage of png_zalloc and png_zfree.
    * Don't ignore those warnings; you must also reset the default calling
    * convention in your compiler to match your PNGAPI, and you must build
    * zlib and your applications the same way you build libpng.
    #if defined(__MINGW32__) && !defined(PNG_MODULEDEF)
    # ifndef PNG_NO_MODULEDEF
    # define PNG_NO_MODULEDEF
    # endif
    #endif
    #if !defined(PNG_IMPEXP) && defined(PNG_BUILD_DLL) && !defined(PNG_NO_MODULEDEF)
    # define PNG_IMPEXP
    #endif
    #if defined(PNG_DLL) || defined(_DLL) || defined(__DLL__ ) || \
    (( defined(_Windows) || defined(_WINDOWS) || \
    defined(WIN32) || defined(_WIN32) || defined(__WIN32__) ))
    # ifndef PNGAPI
    # if defined(__GNUC__) || (defined (_MSC_VER) && (_MSC_VER >= 800))
    # define PNGAPI __cdecl
    # else
    # define PNGAPI _cdecl
    # endif
    # endif
    # if !defined(PNG_IMPEXP) && (!defined(PNG_DLL) || \
    0 /* WINCOMPILER_WITH_NO_SUPPORT_FOR_DECLIMPEXP */)
    # define PNG_IMPEXP
    # endif
    # if !defined(PNG_IMPEXP)
    # define PNG_EXPORT_TYPE1(type,symbol) PNG_IMPEXP type PNGAPI symbol
    # define PNG_EXPORT_TYPE2(type,symbol) type PNG_IMPEXP PNGAPI symbol
    /* Borland/Microsoft */
    # if defined(_MSC_VER) || defined(__BORLANDC__)
    # if (_MSC_VER >= 800) || (__BORLANDC__ >= 0x500)
    # define PNG_EXPORT PNG_EXPORT_TYPE1
    # else
    # define PNG_EXPORT PNG_EXPORT_TYPE2
    # if defined(PNG_BUILD_DLL)
    # define PNG_IMPEXP __export
    # else
    # define PNG_IMPEXP /*__import */ /* doesn't exist AFAIK in
    VC++ */
    # endif /* Exists in Borland C++ for
    C++ classes (== huge) */
    # endif
    # endif
    # if !defined(PNG_IMPEXP)
    # if defined(PNG_BUILD_DLL)
    # define PNG_IMPEXP __declspec(dllexport)
    # else
    # define PNG_IMPEXP __declspec(dllimport)
    # endif
    # endif
    # endif /* PNG_IMPEXP */
    #else /* !(DLL || non-cygwin WINDOWS) */
    # if (defined(__IBMC__) || defined(__IBMCPP__)) && defined(__OS2__)
    # ifndef PNGAPI
    # define PNGAPI _System
    # endif
    # else
    # if 0 /* ... other platforms, with other meanings */
    # endif
    # endif
    #endif
    #ifndef PNGAPI
    # define PNGAPI
    #endif
    #ifndef PNG_IMPEXP
    # define PNG_IMPEXP
    #endif
    #ifndef PNG_EXPORT
    # define PNG_EXPORT(type,symbol) PNG_IMPEXP type PNGAPI symbol
    #endif
    #ifdef PNG_USE_GLOBAL_ARRAYS
    # ifndef PNG_EXPORT_VAR
    # define PNG_EXPORT_VAR(type) extern PNG_IMPEXP type
    # endif
    #endif
    /* User may want to use these so they are not in PNG_INTERNAL. Any library
    * functions that are passed far data must be model independent.
    #ifndef PNG_ABORT
    # define PNG_ABORT() abort()
    #endif
    #ifdef PNG_SETJMP_SUPPORTED
    # define png_jmpbuf(png_ptr) ((png_ptr)->jmpbuf)
    #else
    # define png_jmpbuf(png_ptr) \
    (LIBPNG_WAS_COMPILED_WITH__PNG_SETJMP_NOT_SUPPORTED)
    #endif
    #if defined(USE_FAR_KEYWORD) /* memory model independent fns */
    /* use this to make far-to-near assignments */
    # define CHECK 1
    # define NOCHECK 0
    # define CVT_PTR(ptr) (png_far_to_near(png_ptr,ptr,CHECK))
    # define CVT_PTR_NOCHECK(ptr) (png_far_to_near(png_ptr,ptr,NOCHECK))
    # define png_strcpy _fstrcpy
    # define png_strncpy _fstrncpy /* Added to v 1.2.6 */
    # define png_strlen _fstrlen
    # define png_memcmp _fmemcmp /* SJT: added */
    # define png_memcpy _fmemcpy
    # define png_memset _fmemset
    #else /* use the usual functions */
    # define CVT_PTR(ptr) (ptr)
    # define CVT_PTR_NOCHECK(ptr) (ptr)
    # define png_strcpy strcpy
    # define png_strncpy strncpy /* Added to v 1.2.6 */
    # define png_strlen strlen
    # define png_memcmp memcmp /* SJT: added */
    # define png_memcpy memcpy
    # define png_memset memset
    #endif
    /* End of memory model independent support */
    /* Just a little check that someone hasn't tried to define something
    * contradictory.
    #if (PNG_ZBUF_SIZE > 65536L) && defined(PNG_MAX_MALLOC_64K)
    # undef PNG_ZBUF_SIZE
    # define PNG_ZBUF_SIZE 65536L
    #endif
    #ifdef PNG_READ_SUPPORTED
    /* Prior to libpng-1.0.9, this block was in pngasmrd.h */
    #if defined(PNG_INTERNAL)
    /* These are the default thresholds before the MMX code kicks in; if either
    * rowbytes or bitdepth is below the threshold, plain C code is used. These
    * can be overridden at runtime via the png_set_mmx_thresholds() call in
    * libpng 1.2.0 and later. The values below were chosen by Intel.
    #ifndef PNG_MMX_ROWBYTES_THRESHOLD_DEFAULT
    # define PNG_MMX_ROWBYTES_THRESHOLD_DEFAULT 128 /* >= */
    #endif
    #ifndef PNG_MMX_BITDEPTH_THRESHOLD_DEFAULT
    # define PNG_MMX_BITDEPTH_THRESHOLD_DEFAULT 9 /* >= */
    #endif
    /* Set this in the makefile for VC++ on Pentium, not here. */
    /* Platform must be Pentium. Makefile must assemble and load pngvcrd.c .
    * MMX will be detected at run time and used if present.
    #ifdef PNG_USE_PNGVCRD
    # define PNG_HAVE_ASSEMBLER_COMBINE_ROW
    # define PNG_HAVE_ASSEMBLER_READ_INTERLACE
    # define PNG_HAVE_ASSEMBLER_READ_FILTER_ROW
    #endif
    /* Set this in the makefile for gcc/as on Pentium, not here. */
    /* Platform must be Pentium. Makefile must assemble and load pnggccrd.c .
    * MMX will be detected at run time and used if present.
    #ifdef PNG_USE_PNGGCCRD
    # define PNG_HAVE_ASSEMBLER_COMBINE_ROW
    # define PNG_HAVE_ASSEMBLER_READ_INTERLACE
    # define PNG_HAVE_ASSEMBLER_READ_FILTER_ROW
    #endif
    /* - see pnggccrd.c for info about what is currently enabled */
    #endif /* PNG_INTERNAL */
    #endif /* PNG_READ_SUPPORTED */
    #endif /* PNGCONF_H */

    First, I agree with Karol, use the AUR so that pacman can do its job.  Second, when you do your make, there is no reason to run it as root (until you do the make install)  For the initial build, it is much safer to not use root; plus all the files in your home directory will continue to belong to use, not to root.
    But, try the AUR.

  • Braille display not showing bullet points in pages.

    I'm trying to help out a blind friend of mine. She has a mac, and needs to use a word processor on a daily basis. The problem is that her braille display doesn't show bullet points, and text properties such as italic or bold. She has tried openoffice, but there, VoiceOver doesn't say anything, probably because it uses a different UI kit.

    I would recommend trying TextEdit and Nisus Writer as well, as sometimes these are superior to Pages.

  • Building in and then building out

    I have a series of bullet points that I'd like to have build in then out one at a time so there's only one bullet at a time on a particular slide. When I try to rearrange the bullet points in the Build Order box of the Inspector it only allows me to move all the Build Ins or all the Build Outs but not one at a time. I'd like to have bullet one build in on the first click and then build out on the second click and same thing with the next two bullets. Is there a way to do this?
    Thanks,
    Marc

    Is there a way to do this? Yes.
    See the Build Inspector, select all the bullets, Build IN, and Delivery by Paragraph
    then
    select all the bullets, Build Out, and Delivery by Paragraph,
    then
    in the Drawer, start shuffling and altering the Start Build until you get what you want.
    Alternately, have each bullet item as a separate object (text block) (which is effectively what the above does) and manipulate as desired.
    Or
    have each bullet on a separate slide and just do a slide transition without builds.

  • How to handle weird characters in form fields (like bullet points from Word docs)

    hi there
    lots of my users copy and paste from MS Word documents into a
    text area
    my app takes that form.textarea data and inserts it in a
    MYSQL db.
    when we output that cell from the db, we often find there are
    ? [question marks] where there once were special characters in the
    Word doc text.
    it seems that bullet points in word docs are the worst
    offenders.
    each time i spot a new one i try to find out the chr() number
    for it and make a substitiution before the text is stored in the
    db, but its a bit hit and miss (relies on me spotting it) and its v
    time consuming
    ive tried using functions safetext and demoronize - but they
    dont seem to do what i need
    im sure im not the first person to run into this - any
    suggestions anyone?
    thanks very much indeed for any help you can give.
    kind regards
    Nick

    Thanks Paul and Azadi
    Paul - when you say "change it to unicode" do you mean the
    page or a setting in the db? forgive me if i'm being stupid but
    this is all new territory to me. Thank you ever so much for your
    help - does sound logical what you say :)
    Azadi - thanks very much for this (I'm pressuming that
    there's a charge for this udf) so i'll try to implement Paul's
    solution and if I can't do that I'll buy the the udf - thanks very
    much indeed for your help, really is much apprecaited.
    kind regards
    Nick

  • Build failure when trying to build haproxy with SSL support.

    Hello everybody,
    I don't know if this is the right "context" to submit this question.
    How ever I'm having problem with building haproxy 1.5.5 with SSL support.
    I'm running SLES 11 SP3 with the latest updates via YAST2.
    Building without SSL support works fine.
    I use the syntax:
    make TARGET=linux2628 USE_OPENSSL=1
    And here is the output:
    gcc -Iinclude -Iebtree -Wall -O2 -g -fno-strict-aliasing -DCONFIG_HAP_LINUX_SPLICE -DTPROXY -DCONFIG_HAP_LINUX_TPROXY -DCONFIG_HAP_CRYPT -DENABLE_POLL -DENABLE_EPOLL -DUSE_CPU_AFFINITY -DASSUME_SPLICE_WORKS -DUSE_ACCEPT4 -DNETFILTER -DUSE_GETSOCKNAME -DUSE_OPENSSL -DUSE_SYSCALL_FUTEX -DCONFIG_HAPROXY_VERSION=\"1.5.5\" -DCONFIG_HAPROXY_DATE=\"2014/10/07\" \
    -DBUILD_TARGET='"linux2628"' \
    -DBUILD_ARCH='""' \
    -DBUILD_CPU='"generic"' \
    -DBUILD_CC='"gcc"' \
    -DBUILD_CFLAGS='"-O2 -g -fno-strict-aliasing"' \
    -DBUILD_OPTIONS='"USE_OPENSSL=1"' \
    -c -o src/haproxy.o src/haproxy.c
    In file included from include/types/acl.h:33,
    from include/types/proxy.h:40,
    from include/proto/log.h:32,
    from includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
    from src/haproxy.c:61:
    include/types/server.h:29:25: error: openssl/ssl.h: No such file or directory
    In file included from include/types/connection.h:30,
    from include/types/server.h:36,
    from include/types/acl.h:33,
    from include/types/proxy.h:40,
    from include/proto/log.h:32,
    from includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
    from src/haproxy.c:61:
    include/types/listener.h:127: error: expected specifier-qualifier-list before SSL_CTX
    In file included from include/types/acl.h:33,
    from include/types/proxy.h:40,
    from include/proto/log.h:32,
    from includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
    from src/haproxy.c:61:
    include/types/server.h:207: error: expected specifier-qualifier-list before SSL_CTX
    In file included from src/haproxy.c:90:
    include/proto/listener.h: In function bind_conf_alloc:
    include/proto/listener.h:130: error: struct bind_conf has no member named file
    include/proto/listener.h:131: error: struct bind_conf has no member named line
    include/proto/listener.h:133: error: struct bind_conf has no member named by_fe
    include/proto/listener.h:133: error: struct bind_conf has no member named by_fe
    include/proto/listener.h:133: error: struct bind_conf has no member named by_fe
    include/proto/listener.h:133: error: struct bind_conf has no member named by_fe
    include/proto/listener.h:133: error: struct bind_conf has no member named by_fe
    include/proto/listener.h:135: error: struct bind_conf has no member named arg
    include/proto/listener.h:137: error: struct bind_conf has no member named ux
    include/proto/listener.h:138: error: struct bind_conf has no member named ux
    include/proto/listener.h:139: error: struct bind_conf has no member named ux
    include/proto/listener.h:141: error: struct bind_conf has no member named listeners
    include/proto/listener.h:141: error: struct bind_conf has no member named listeners
    include/proto/listener.h:141: error: struct bind_conf has no member named listeners
    In file included from src/haproxy.c:107:
    include/proto/ssl_sock.h: At top level:
    include/proto/ssl_sock.h:46: error: expected declaration specifiers or ... before SSL_CTX
    src/haproxy.c: In function display_build_opts:
    src/haproxy.c:272: error: expected ) before OPENSSL_VERSION_TEXT
    src/haproxy.c:274: warning: implicit declaration of function SSLeay_version
    src/haproxy.c:274: error: SSLEAY_VERSION undeclared (first use in this function)
    src/haproxy.c:274: error: (Each undeclared identifier is reported only once
    src/haproxy.c:274: error: for each function it appears in.)
    src/haproxy.c:275: error: OPENSSL_VERSION_NUMBER undeclared (first use in this function)
    src/haproxy.c:275: warning: implicit declaration of function SSLeay
    src/haproxy.c:275: warning: format %s expects type char *, but argument 2 has type int
    src/haproxy.c: In function deinit:
    src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
    src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
    src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
    src/haproxy.c:1188: warning: left-hand operand of comma expression has no effect
    src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
    src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
    src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
    src/haproxy.c:1196: error: struct bind_conf has no member named file
    src/haproxy.c:1197: error: struct bind_conf has no member named arg
    src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
    src/haproxy.c:1198: warning: type defaults to int in declaration of __ret
    src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
    src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
    src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
    src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
    src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
    make: *** [src/haproxy.o] Error 1
    I'm I missing some libs or sources from OpenSSL ?
    And/or need to point them out so that make/gcc can find them?
    I have copy haproxy from another machine where I did the build process on.
    But I would like to be able to build it on my SLES 11 SP3 installation.
    Thank you in advance.

    Originally Posted by smflood
    On 17/10/2014 15:36, mattias bjork wrote:
    > I don't know if this is the right "context" to submit this question.
    >
    > How ever I'm having problem with building haproxy 1.5.5 with SSL
    > support.
    >
    > I'm running SLES 11 SP3 with the latest updates via YAST2.
    >
    > Building without SSL support works fine.
    >
    > I use the syntax:
    >
    > make TARGET=linux2628 USE_OPENSSL=1
    >
    > And here is the output:
    >
    > gcc -Iinclude -Iebtree -Wall -O2 -g -fno-strict-aliasing
    > -DCONFIG_HAP_LINUX_SPLICE -DTPROXY -DCONFIG_HAP_LINUX_TPROXY
    > -DCONFIG_HAP_CRYPT -DENABLE_POLL -DENABLE_EPOLL -DUSE_CPU_AFFINITY
    > -DASSUME_SPLICE_WORKS -DUSE_ACCEPT4 -DNETFILTER -DUSE_GETSOCKNAME
    > -DUSE_OPENSSL -DUSE_SYSCALL_FUTEX -DCONFIG_HAPROXY_VERSION=\"1.5.5\"
    > -DCONFIG_HAPROXY_DATE=\"2014/10/07\" \
    > -DBUILD_TARGET='"linux2628"' \
    > -DBUILD_ARCH='""' \
    > -DBUILD_CPU='"generic"' \
    > -DBUILD_CC='"gcc"' \
    > -DBUILD_CFLAGS='"-O2 -g -fno-strict-aliasing"' \
    > -DBUILD_OPTIONS='"USE_OPENSSL=1"' \
    > -c -o src/haproxy.o src/haproxy.c
    > In file included from include/types/acl.h:33,
    > from include/types/proxy.h:40,
    > from include/proto/log.h:32,
    > from
    > includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
    > from src/haproxy.c:61:
    > include/types/server.h:29:25: error: openssl/ssl.h: No such file or
    > directory
    > In file included from include/types/connection.h:30,
    > from include/types/server.h:36,
    > from include/types/acl.h:33,
    > from include/types/proxy.h:40,
    > from include/proto/log.h:32,
    > from
    > includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
    > from src/haproxy.c:61:
    > include/types/listener.h:127: error: expected specifier-qualifier-list
    > before �SSL_CTX�
    > In file included from include/types/acl.h:33,
    > from include/types/proxy.h:40,
    > from include/proto/log.h:32,
    > from
    > includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
    > from src/haproxy.c:61:
    > include/types/server.h:207: error: expected specifier-qualifier-list
    > before �SSL_CTX�
    > In file included from src/haproxy.c:90:
    > include/proto/listener.h: In function �bind_conf_alloc�:
    > include/proto/listener.h:130: error: �struct bind_conf� has no member
    > named �file�
    > include/proto/listener.h:131: error: �struct bind_conf� has no member
    > named �line�
    > include/proto/listener.h:133: error: �struct bind_conf� has no member
    > named �by_fe�
    > include/proto/listener.h:133: error: �struct bind_conf� has no member
    > named �by_fe�
    > include/proto/listener.h:133: error: �struct bind_conf� has no member
    > named �by_fe�
    > include/proto/listener.h:133: error: �struct bind_conf� has no member
    > named �by_fe�
    > include/proto/listener.h:133: error: �struct bind_conf� has no member
    > named �by_fe�
    > include/proto/listener.h:135: error: �struct bind_conf� has no member
    > named �arg�
    > include/proto/listener.h:137: error: �struct bind_conf� has no member
    > named �ux�
    > include/proto/listener.h:138: error: �struct bind_conf� has no member
    > named �ux�
    > include/proto/listener.h:139: error: �struct bind_conf� has no member
    > named �ux�
    > include/proto/listener.h:141: error: �struct bind_conf� has no member
    > named �listeners�
    > include/proto/listener.h:141: error: �struct bind_conf� has no member
    > named �listeners�
    > include/proto/listener.h:141: error: �struct bind_conf� has no member
    > named �listeners�
    > In file included from src/haproxy.c:107:
    > include/proto/ssl_sock.h: At top level:
    > include/proto/ssl_sock.h:46: error: expected declaration specifiers or
    > �...� before �SSL_CTX�
    > src/haproxy.c: In function �display_build_opts�:
    > src/haproxy.c:272: error: expected �)� before �OPENSSL_VERSION_TEXT�
    > src/haproxy.c:274: warning: implicit declaration of function
    > �SSLeay_version�
    > src/haproxy.c:274: error: �SSLEAY_VERSION� undeclared (first use in this
    > function)
    > src/haproxy.c:274: error: (Each undeclared identifier is reported only
    > once
    > src/haproxy.c:274: error: for each function it appears in.)
    > src/haproxy.c:275: error: �OPENSSL_VERSION_NUMBER� undeclared (first use
    > in this function)
    > src/haproxy.c:275: warning: implicit declaration of function �SSLeay�
    > src/haproxy.c:275: warning: format �%s� expects type �char *�, but
    > argument 2 has type �int�
    > src/haproxy.c: In function �deinit�:
    > src/haproxy.c:1188: error: �struct bind_conf� has no member named
    > �by_fe�
    > src/haproxy.c:1188: error: �struct bind_conf� has no member named
    > �by_fe�
    > src/haproxy.c:1188: error: �struct bind_conf� has no member named
    > �by_fe�
    > src/haproxy.c:1188: warning: left-hand operand of comma expression has
    > no effect
    > src/haproxy.c:1188: error: �struct bind_conf� has no member named
    > �by_fe�
    > src/haproxy.c:1188: error: �struct bind_conf� has no member named
    > �by_fe�
    > src/haproxy.c:1188: error: �struct bind_conf� has no member named
    > �by_fe�
    > src/haproxy.c:1196: error: �struct bind_conf� has no member named
    > �file�
    > src/haproxy.c:1197: error: �struct bind_conf� has no member named �arg�
    > src/haproxy.c:1198: error: �struct bind_conf� has no member named
    > �by_fe�
    > src/haproxy.c:1198: warning: type defaults to �int� in declaration of
    > �__ret�
    > src/haproxy.c:1198: error: �struct bind_conf� has no member named
    > �by_fe�
    > src/haproxy.c:1198: error: �struct bind_conf� has no member named
    > �by_fe�
    > src/haproxy.c:1198: error: �struct bind_conf� has no member named
    > �by_fe�
    > src/haproxy.c:1198: error: �struct bind_conf� has no member named
    > �by_fe�
    > src/haproxy.c:1198: error: �struct bind_conf� has no member named
    > �by_fe�
    > make: *** [src/haproxy.o] Error 1
    >
    >
    > I'm I missing some libs or sources from OpenSSL ?
    >
    > And/or need to point them out so that make/gcc can find them?
    >
    > I have copy haproxy from another machine where I did the build process
    > on.
    >
    > But I would like to be able to build it on my SLES 11 SP3 installation.
    So you're trying to build HAProxy 1.5.5 from source?
    Do you have libopenssl and libopenssl-devel installed? What does "rpm
    -qa | grep ssl" report?
    You might have better luck installing HAProxy 1.5.5 already built for
    SLES11 SP3 via the openSUSE Build Service @
    https://build.opensuse.org/package/s...ackage=haproxy
    HTH.
    Simon
    Novell Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below. Thanks.
    Hello Simon,
    Yes I'm trying to build it from source.
    Unfortunately I don't have them installed.
    Here is the output:
    sudo -i rpm -qa | grep -i ssl
    openssl-0.9.8j-0.62.1
    libopenssl0_9_8-0.9.8j-0.62.1
    libopenssl0_9_8-32bit-0.9.8j-0.62.1
    perl-IO-Socket-SSL-1.38-5.2.2
    perl-Net-SSLeay-1.35-2.14
    openssl-certs-1.97-0.3.1
    Thank you for your speedy reply.

  • Animated QuickTime backgrounds with text bullet points over it????

    The bullet point lines would need to animate on screen at the user's interaction (clicking the mouse or pressing arrow key). I tried this in PowerPoint and it didn't work. Every time you hit the arrow key or click the mouse to animate the first bullet point the movie in the background freezes and comes to the front covering the bulleted text.
    Mac Pro   Mac OS X (10.4.9)  
    Mac Pro   Mac OS X (10.4.9)  

    yes, you can do this in Keynote. The only issues might be that on some machines, if you are using the presenter layout on your laptop screen, the video will stutter as you build in each bullet. Turning off the presenter tools usually takes care of that. Also, you can't extend the video onto a second slide, so anything you want to build in front of that video must be on THAT slide. Lastly, video currently pauses during a slide transition in Keynote, so even if you do a cross dissolve to the next slide, hoping for a smooth video to video transition, it won't be smooth, the video will freeze as it fades into the next one, which will also be frozen, then the next one will start playing.

  • Bullet point alignment problem

    Hi I am having a problem with the alignment when I use bullet points?
    the body of the text is aligned so it does not exceed the screen width. But once I enter bullet points it exceeds the right hand side alignment. How do I make the alignment remain the same?
    i.e.
    blah blah blah blah blah blah
    blah blah blah blah blah blah
    blah blah blah blah blah blah
    blah blah blah blah blah blah
    blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah
    blah blah blah blah blah blah blah blah blah blah blah blah Blah
    blah blah blah blah blah blah blah blah blah blah blah blah
    blah blah blah blah blah blah
    blah blah blah blah blah blah
    blah blah blah blah blah blah
    blah blah blah blah blah blah
    I have written codes as
        <!-- InstanceEndEditable -->
    </div>
    <div id="content">
      <p> </p>
      <!-- InstanceBeginEditable name="ContentEditRegion" -->
      <p><strong>What is BioprimeTM  &ndash; and why do you need it?</strong><br />
    BioprimeTM   is a simple, inexpensive soil conditioner which allows farmers to change  the nature of soil biology. It is a way to weed out the bad bugs and give the  good bugs a boost. The outcome is better soil health, better plant production  and better root disease management. 
      <p><br />
      <strong>BioprimeTM</strong>
      <ul>
        <li>is made in Perth. </li>
        <li>is backed by trial data from work done in WA.</li>
        <li>does not cost a fortune (per liter and per  hectare it is probably the cheapest input you will use this season).</li>
        <li>does  not require a leap of faith to use, nor any rocket science to understand what  it is and why it works.</li>
      </ul>
      <p>BioprimeTM was originally developed about 15  years ago for vegetable producers as a way to control root disease. In those  days you couldn&rsquo;t actually prove what was going on, but growers kept buying it  because it did what it was intended to do &ndash; it stopped root disease.<br />

    Below is the complete page code including a doctype, the <head> and <body> tags.
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
    <link href="../CSS/Bio_CSS.css" rel="stylesheet" type="text/css" media="all" />
    <script src="../Scripts/swfobject_modified.js" type="text/javascript"></script>
    <title>Welomce to Bioscience</title>
    <style type="text/css">
    body {height:100%;
    max-height:100%;
    overflow:hidden;
    padding:0;
    margin:0;
    border:0;
    #content {
    overflow:auto;
    position:absolute;
    z-index:3;
    top:150px;
    bottom:20px;
    left:270px;
    right:0;
    background-color: #FFFFCC;
    color: #000;
    font-size:14px;
    * html #content {
    top:0;
    left:0;
    right:0;
    bottom:0;
    height:100%;
    max-height:100%;
    width:100%;
    overflow:auto;
    position:absolute;
    z-index:3;
    border-top:150px solid #fff;
    border-bottom:25px solid #fff;
    border-left:270px solid #fff;
    font-family: Verdana, Geneva, sans-serif;
    font-size: 14px;
    font-style: normal;
    line-height: 25px;
    #head {
    position:absolute;
    margin:0;
    top:-2px;
    left:-2px;
    display:block;
    width:100%;
    height:150px;
    background-position:0 0;
    background-repeat:no-repeat;
    font-size:4em;
    z-index:5;
    overflow:hidden;
    color:#000;
    background-color: #9acc99;
    #foot {
    position:absolute;
    margin:0;
    bottom:-3px;
    left:2px;
    display:block;
    width:100%;
    height:25px;
    font-size:1em;
    z-index:5;
    overflow:hidden;
    color:#fff;
    background-color: #66CC99;
    text-align: center;
    font-family: Verdana, Geneva, sans-serif;
    visibility: visible;
    #content p {
    color: #000;
    text-align:justify;
    line-height:1.5;
    font-family:Verdana, Geneva, sans-serif;
    font-size:1em;
    padding-top: 0px;
    padding-right:40px;
    padding-bottom:0px;
    padding-left:40px;
    width:950px;
    #content h1 {
    color: #663300;
    padding: 0px;
    text-indent: 30px;
    #content h2 {
    font-family: "Trebuchet MS", Arial, Helvetica, sans-serif;
    font-size: 18px;
    color: #000;
    text-indent: 30px;
    #content h3 {
    font-family: Verdana, Geneva, sans-serif;
    font-size: 14px;
    color: #000;
    text-indent: 50px;
    * html #left {
    position:absolute;
    left:0;
    top:150px;
    bottom:25px;
    width:270px;
    height: 100%;
    #left {
    position:absolute;
    left:0px;
    top:149px;
    bottom:20px;
    width:270px;
    font-size:1em;
    z-index:4;
    overflow:auto;
    background-repeat:no-repeat;
    background-color: #9acc99;
    color: #663300;
    text-align: left;
    vertical-align: middle;
    background-image: url(../Assets/Side_Background7.jpg);
    font-family: Andalus, "Palatino Linotype", "Times New Roman";
    #left h2 {
    text-indent: 15px;
    #left h3 {
    text-indent: 30px;
    #left ul{
    margin:0;
    padding:0;
    list-style:none;
    #left a {
    colour#663300;
    #left li a:link,#left li a:visited{
    padding:0 0;
    display:block;
    text-decoration:none;
    font:Andalus, Georgia, "Times New Roman";
    color:#FFFFFF;
    #left li a:hover {
    background:#306726;
    color:#FFF;
    #left li a.current,#left li a.current:hover,#left li a.current:active {
    color:#663300;
    background:#ffffcc;
    cursor:default;
    * html #left li a.current,#left li a.current:hover,#left li a.current:active,#left li a.current:visited {
    color:#663300;
    background:#ffffcc;
    cursor:default;
    #content ul {
    margin: 0;
    padding: 0 0 12px 55px;
    #content li {
    margin: 0 0 5px 0;
    padding: 0;
    font-family: Verdana, Geneva, sans-serif;
    font-size: 14px;
    </style>
    </head>
    <body>
    <div id="head"><img src="../Assets/BioLogo.jpg" width="300" height="150" align="left">
      <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="980" height="150" id="FlashID">
        <param name="movie" value="../Assets/Bio_980x150_Banner.swf">
        <param name="quality" value="high">
        <param name="wmode" value="opaque">
        <param name="swfversion" value="6.0.65.0">
        <!-- This param tag prompts users with Flash Player 6.0 r65 and higher to download the latest version of Flash Player. Delete it if you don’t want users to see the prompt. -->
        <param name="expressinstall" value="../Scripts/expressInstall.swf">
        <!-- Next object tag is for non-IE browsers. So hide it from IE using IECC. -->
        <!--[if !IE]>-->
        <object data="../Assets/Bio_980x150_Banner.swf" type="application/x-shockwave-flash" width="980" height="150">
          <!--<![endif]-->
          <param name="quality" value="high">
          <param name="wmode" value="opaque">
          <param name="swfversion" value="6.0.65.0">
          <param name="expressinstall" value="../Scripts/expressInstall.swf">
          <!-- The browser displays the following alternative content for users with Flash Player 6.0 and older. -->
          <div>
            <h4>Content on this page requires a newer version of Adobe Flash Player.</h4>
            <p><a href="http://www.adobe.com/go/getflashplayer"><img src="http://www.adobe.com/images/shared/download_buttons/get_flash_player.g if" alt="Get Adobe Flash player" width="112" height="33" /></a></p>
          </div>
          <!--[if !IE]>-->
        </object>
        <!--<![endif]-->
      </object>
    </div>
    <div id="foot">&copy;2010 Bioscience Pty Ltd, 488 Nicholson Road Forrestdale, WA, 6112, Ph: (08) 9397 2446, Fax: (08) 9397 2447, Email: <a href="mailto:[email protected] ">[email protected] </a></div>
    <div id="left">
    <ul>
    <li>
      <h2>
      <a href="../index.html">Home</a>
      <a href="../Enviro/enviro_acid.html">Environmental</a>
      <a href="../Water/water.html">Water</a>
      <a href="soil.html" class="current">Soil</a>      
      </h2>
    </li>
    <li>
      <h3>
      <a href="soil_diversity.html">Soil Biodiversity</a>
      <a href="soil_microbial.html">Soil Microbial Ecology</a>
      <a href="soil_bioprime.html">Bioprime<sup>TM</sup></a>
      <a href="soil_orderform.html">Order Form</a>  
      </h3>
    </li>
    <li>
      <h2>
      <a href="../Geotech/geotech.html">Geotechnical</a>
      <a href="../Horti/horti.html">Horticultural</a>
      <a href="../Analyt/analyt.html">Analytical</a>
      <a href="../Research/research.html">Research </a>
      <a href="../Products/products.html">Products</a>
      </h2>
    </li>
    </ul>  
    </div>
    <div id="content">
      <p> </p>
    <p><strong>What is Bioprime<sup>TM</sup>  &ndash; and why do you need it?</strong><br />
    Bioprime<sup>TM</sup>   is a simple, inexpensive soil conditioner which allows farmers to change  the nature of soil biology. It is a way to weed out the bad bugs and give the  good bugs a boost. The outcome is better soil health, better plant production  and better root disease management.<br />
    <br><strong>Bioprime<sup>TM</sup></strong></p>
    <ul>
      <li>is made in Perth. </li>
      <li>is backed by trial data from work done in WA.</li>
      <li>does not cost a fortune (per liter and per  hectare it is probably the cheapest input you will use this season).</li>
      <li>does not require a leap of faith to use, nor any rocket science to understand what  it is and why it works.</li>
    </ul>
    <p>Bioprime<sup>TM</sup> was originally developed about 15  years ago for vegetable producers as a way to control root disease. In those  days you couldn&rsquo;t actually prove what was going on, but growers kept buying it  because it did what it was intended to do &ndash; it stopped root disease.<br />
      In the last 10 years there have been many advances in  understanding what microbes are in soil, and what they are doing. This has  largely come about because of the so-called DNA revolution. By using this DNA  technology, we can now see exactly what changes occur in soil microbiology when  Bioprime<sup>TM</sup> is applied. <br />
    <br> <strong>How is it made ?</strong> <strong></strong><br />
      Bioprime<sup>TM</sup>  is made by fermentation of molasses using  baker&rsquo;s yeast. This sounds really simple, but there are a number of factors involved  to make it work. <br />
      The amount of oxygen in the fermentation determines how much  alcohol, acid or CO2 is made from the sugar in molasses.  Bioprime<sup>TM</sup> is made with the amount  of air carefully controlled in order to make a maximum amount of both alcohols  and acids. These then condense to form esters.   Bioprime<sup>TM</sup> is full of esters.<br />
      With Bioprime<sup>TM</sup> we want lots of yeast, so  nutrients are added to make the yeast grow quickly. At the end of the process  we have a lot of biomass, because just like in Vegemite, yeast biomass contains  a lot of protein and vitamins.<br />
      The fermentation which makes Bioprime<sup>TM</sup> doesn&rsquo;t  stop completely, it slows down as it becomes pickled in its own acids. We then  arrest the process by bursting the yeast cells, making a stable, long-life  product. <br />
    <br><strong>How does it work ?</strong><br />
      Looking at soil microbiology using DNA shows it is very  complex. There are tens of thousands of different species in each gram of soil.  There is no point in looking at any single species, for they all seem to come  and go with changing seasons and conditions.<br />
      Instead we look at the major groups and the diversity within  each group. We look at 5 major groups:</p>
    <ul>
      <li>Proteobacteria:   These are simple, fast growing bacteria (formerly called gram  negatives), can dominate anaerobic (no oxygen) environments, live off simple  organic matter &ndash; they generally don&rsquo;t do your soil much good.</li>
      <li>Fermicutes: More complex, also fast growing  (formerly called gram positives), some are important pathogens, can be  anaerobic or aerobic, also don&rsquo;t do soil much good.</li>
      <li>Archea: These are tough and ancient life forms,  slow growing, but live in extreme environments (hot, salty, acidic etc). Their importance  in soil was only realised with DNA methods. They build up to significant  numbers in cultivated soil.</li>
      <li>Actinobacteria: These are quite complex bacteria  which are involved in soil carbon dynamics. They are slow growing but feisty,  as they are the chemical warfare specialists in soil. (Most of the antibiotics  and drugs we use come from this group). When there are plenty present, root pathogens  are suppressed.</li>
      <li>Fungi: These are more complex than bacteria, and  fall into two groups, the lower fungi are mainly moulds, and the higher fungi,  the Dikarya are the mushrooms and the mycorrhyza.</li>
    </ul>
    <p>The more diverse a soil&rsquo;s microbial population, the  healthier it is. All the above five groups should be present, but because the  Actinobacteria and Fungi are beneficial to plant growth, high diversity in  these groups is particularly important.<br />
      When Bioprime<sup>TM</sup> is added to soil, the  Actinobacteria and Dikarya get a boost because they get a dose of vitamins. The  proteobacteria get suppressed, firstly because the way they communicate with  each other, a process called quorum sensing, is interrupted. Secondly, they can&rsquo;t  grow s easily on the complex esters, but higher bacteria and fungi can.<br />
      When we look at the way group diversity changes, we see short  term and longer term impacts. In the short term, anaerobic bacteria are quickly  suppressed. Then we see Dikarya and Actinobacteria start to build up numbers.<br />
      These changes mean the best time to use Bioprime<sup>TM</sup> is  when you sow your crop, then again once it is established &ndash; at the two to four  leaf stage. <br />
      In moist soil, grains take a few days to imbibe water and  start to germinate. During this time, the presence of proteobacteria can be  harmful, as they can feed on the exudates produced by a germinating seed and  make a local anaerobic zone in wet soil, slowing down emergence. On the other  hand, you want Dikarya active, for within this group are the mycorrhyzal fungi  which colonize roots and help plant phosphorous uptake.  There is plenty of competition in soil, so the  quicker they can colonise the root, the more likely they will persist.<br />
      There are a number of important pathogenic organisms which  lurk in soil, and they often go unnoticed until stress hits the plant. An  important control against pathogens is the Actinobacteria which feed on the  pathogens. They also antagonise the simple bacteria which mineralise nitrogen.<br />
      So Bioprime<sup>TM</sup> does quite a lot of things, all of  which are good for the ability of soil to support healthy plant growth.<br />
    <br><strong>How much to use ?</strong><br />
      The optimal application rate depends on two important  factors, pH and soil organic matter.<br />
      Bioprime<sup>TM</sup> works best at a soil pH of 7 &ndash; and this  is the point of optimal plant nutrient availability. We always advise to lime  soil to get it to pH 7 &ndash; because we now we realise this is also the point of  maximum microbial diversity. <br />
      At a pH of 7, you only need to apply 3 liters per hectare at  each application to get a maximal response. If the pH is lower, you get a  better response by applying more &ndash; 5 liters per hectare at pH 4.5 &ndash; 5.5, and 4  liters per hectare at pH 5.5 &ndash; 6.5.<br />
      The amount of organic matter in soil also influences the  best application rate, but in a complex way. At low soil organic matter (under  0.5% organic carbon), a low rate works well (but adjusted for pH). If your soil  carbon is between 0.5 &ndash; 1.5%, it takes a bit more for maximal impact because  there is more background microbes living off that carbon, so you apply about  50% more. But if your soil carbon is very good (say 1.5 &ndash; 2.5%), you can drop the  rate back again. If organic carbon is above 2.5% - you are blessed, and you  soil is likely to already be very healthy and it is unlikely Bioprime<sup>TM</sup>  will give you a further benefit. The following  table summarises the best application rate.</p>
    <p align="center">
    <table border="4" cellpadding="2" cellspacing="2" width="50%">
    <tr>
    <td>Application Rates</td>
    <td colspan="3">Organic Carbon   </td>
    </tr>
    <tr>
    <td>pH Range</td>
    <td>0 - 0.5%</td>
    <td>0.5 - 1.5%</td>
    <td>1.5 - 2.5%</td>
    </tr>
    <tr>
    <td>4.5 - 5.5</td>
    <td>5 L/ha</td>
    <td>7.5 L/ha</td>
    <td>5 L/ha</td>
    </tr>
    <tr>
    <td>5.5 - 6.5</td>
    <td>4 L/ha</td>
    <td>6 L/ha</td>
    <td>4 L/ha</td>
    </tr>
    <tr>
    <td>6.5 - 7.5</td>
    <td>3 L/ha</td>
    <td>4.5 L/ha</td>
    <td>3 L/ha</td>
    </tr>
    </table>  
    <p align="left">
    <p><strong>How to apply Bioprime<sup>TM</sup> </strong><br />
      If you have a liquid system on your drill rig, it is best to  apply Bioprime<sup>TM</sup> as a spray into the drill row after the press  wheel. Simply dilute the volume you need in sufficient water to get even  spread.<br />
      Application with a boom spray just before seeding is an  acceptable alternative. Again, simply dilute Bioprime<sup>TM</sup> with water  to get even spread.<br />
      Once your crop is up and established, the second application  can be with a boom spray. Bioprime<sup>TM</sup> is acidic and completely water  soluble, so it is compatible with most chemicals (but check first with a jar  test).<br />
    <br><strong>Bad Start ?</strong><br />
      Sometimes the seasons are unkind &ndash; sow dry and no rain  comes, or too much rain comes and paddocks waterlog.  Bioprime<sup>TM</sup> opens an opportunity  window for about 3 weeks. If you dry sow and it hasn&rsquo;t rained in the first  three weeks, it is probably worth another application once it rains. Likewise  if things get too wet and the crop starts to get stressed and yellow, another  application of Bioprime<sup>TM</sup> will help it get back on its feet.<br />
    <br><strong>Seeing Bioprime<sup>TM</sup>  at work</strong><br />
      We always encourage you to sow a bit of your crop without  Bioprime<sup>TM</sup> so you can see it at work. You should see earlier  emergence, and once the crop is established, compare the root structure between  treated and untreated areas. If you believe root structure is important, you  will be impressed.<br />
      If you want to get into detail, Bioscience provides an assay  of soil microbial diversity which is a world first. Send us a 50 g sample of  soil (sampled properly from the top 150 mm, and put into a refrigerator and  send it to us on ice). We extract the DNA, then measure how many types of  microbes are present in significant numbers in each of the 5 major groups. From  this we can derive a biodiversity index and a health index. If you are  interested in soil biology and soil health, this leading-edge assay can show  you how your soil changes from year to year, guiding you with information on  what treatments work and what doesn&rsquo;t.<br />
    <br><strong>Is there anything  else like Bioprime<sup>TM</sup> ?</strong><br />
      There are a number of products which come and go which make  claims about improving soil health. They never come with a technical  description of what they are, and they never come with field trial data.  Usually there are lots of testimonials from someone in Utah or New Delhi, and  there are pictures of a guy holding big onions in one hand and small onions in  the other.<br />
      We take notice when farmers start talking positively about  getting a good response from a product, so we go out and buy some and pull it  apart in our lab.  There are only two we  have found which are somewhat similar. TM21, made by Best in Canada is  fermented molasses, but it is lot thinner, and poorly stabilised &ndash; smells a bit  putrid compared to Bioprime<sup>TM</sup> .  Vitazyme is  made in the USA, but it is fermented corn syrup rather than molasses, but for  some odd reason they add vitamin D to it (even though there is no known  function for Vitamin D in anything other than higher vertebrates!<br />
      But the huge difference is the price. <br />
    <br><strong>What does</strong> <strong>Bioprime<sup>TM</sup> Cost and How Do I Get  It ?</strong><br />
      Getting Bioprime<sup>TM</sup> is easy. You buy it online  direct from the manufacturer. It is only sold in 1000L IBC&rsquo;s for $2 per liter (FOB). <br />
    If you have your own IBC&rsquo;s, drop them off and we will fill  them up. If you don&rsquo;t, you will have to pay $150 for a serviceable second hand  one.</p>
    <p align="justify"> </p>
      <br>
    </div>
    <script type="text/javascript">
    <!--
    swfobject.registerObject("FlashID");
    //-->
    </script>
    </body>
    </html>

  • Spry menu bar showing up as bullet points insted of the menu bar when previewed

    Hi
    this is my first post so i am sorry if i miss out any information
    i am creating a pretty simple website for my family company and i've tried to incorporate a menu bar so users can navigate between pages it once worked when previwed in firefox and chrome but not internet explorer. i then went on to recreate the menu bar only to find now it only shows in the bullet points and not how it should. can some one help becuse its really getting me annoyed. the website is not live at the moment however i could upload it if this would help.
    Thanks

    Hi & thanks -
    No time for the IE problem now, but on the "bulletpoints" page, these supporting files are either incorrectly linked in your page, or not uploaded to expected folder.
    <script src="file://///Nas-box/work/Business/website/ijjservices 2012/Scripts/swfobject_modified.js" type="text/javascript"></script>
    <script src="file://///Nas-box/work/Business/website/ijjservices 2012/Templates/bar/ajxmenu.js" type="text/javascript"></script>
    (linked to your local computer)
    <script src="/SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    (not uploaded)
    They are correctly linked on the IE page except for the ajax file which is linked to your local conputer.
    No links should start with file://///

Maybe you are looking for

  • HT201322 How do you hide a song from other family members but keep it on your devices?

    I have some movies and content that should not be shared with my 7 year old daughter but I'd like to keep them on my devices - is there a way to selectively share? Thanks in advance.

  • Two ipod touches one apple id

    Hi My two kids both have an ipod touch, and I have the apple id on my computer.   However when my daughter sends and receives messages from her ipod my son can read them and join in conversation (which is annoying my daughter)  how can I stop this ha

  • Workbook does not exist in document store

    Hi All, I have transported a workbook by selecting Role with "only necessry objects" then selected only my workbook, that transport was successful. My Role has different folders, this workbook is part of one of the folder.when this transport went thr

  • Old Computer, Old Office (Version 2002)

    I have chosen not to put a newer version on my computer, because it is slow/old. It does all of the things that I need to do, so that's OK. My Word version: Word 2002 (10.6612.6626) Do you know how to prevent Word from opening a new window when I cli

  • Exceuting work items from the outlook

    Hello, We use the MM release strategy triggering W item which are sent to outlook. When we double click on the work item, we receive the pop up for the login (sapgui shortcut-logon(sys id, client, lang,*swnwiex) the user id is defaulted but not the p