WYSIWYG vs. Printing Topic

I'm having problems with the formatting of my numbered list
when I print the selected topic, in both the .xpj file and .chm
file. When I view the topic or print from the WYSIWYG editor, the
numbered list looks fine. However, when I print it, the numbers in
the list are in a different font. I have checked the styles
settings, style sheet, etc and everything looks in order. Any
ideas?

I printed one topic to check the layout, etc. It's very
strange. If I print from the WYSIWIG editor, it looks fine.
However, iwhen I view it from the .chm file and/or print it, it's
off. Puzzling. Peter didn't seem to have the same provlem when he
viewed the sample I sent him. He suggested I check my IE settings
for font size and/or not to use a style for a numbered list.

Similar Messages

  • Print topic window problems on unix

    What is used to display the list and status of printers available on unix when using the print topic menu button?
    On HPUX, the printer that I am currently using shows up as not accepting jobs even though the lpstat -a says that it is accepting requests.
    Any Ideas? Is it something wrong with my system configuration?
    I also have a few junk printed names in my list.
    Thanks in advance for any help that you can provide.

    That dialog is displayed directly by the Java Runtime Engine. There is no OHJ code involved in fetching the list of printers. I would upgrade to the latest JRE version on your platform, and if it still reproduces, contact the JRE vendor.

  • Copyright Shown When Printing Topics Only

    Hi All,
    I'm told that we used to be able to display a copyright
    statement only when the user would print topics using WinHelp. The
    copyright would not display when viewing.
    I'd like to do same thing using RoboHelp HTML Help. Is there
    a way to do this?
    So far I've explored footers and templates but to no avail.
    Any help would be appreciated.
    Thanks!
    Larry

    Hi Pete,
    Well, it worked great.
    First, on getting the compiled Help file to open up, I had to
    run MJs Help Diagnostics to get the DLLs registered properly. I
    believe the problems cropped in when I installed Flare -- our new
    Help tool.
    Then, I was able to get the citation working properly with
    your excellent instructions. I placed the following in the style
    sheet for each topic.
    @media screen
    p.copyright { display:none; }
    @media print
    p.copyright { display:block; }
    Unfortunately, the Help system currently uses a number of
    style sheets rather than just one, but it still only took a couple
    minutes to put that code in each .css file.
    Then I added the following to the TrueCode of a template
    footer.
    <p class="copyright">Copyright © 2008 Scantron
    Corporation. All rights reserved. Use permitted only under license.
    No part of the Help may be reproduced in any form, or by any means,
    without permission from Scantron Corporation. www.scantron.com
    I was able to apply this to all 1700 help topics in one fell
    swoop. That saved me a lot of work. At first there was a style
    sheet associated with the template file. This switched each topic's
    style sheet to the template's when I applied the template to some
    sample topics. So I removed the .css file association with the
    template, and then it worked like a charm.
    Thanks again for the insight. I really didn't think that I
    had a chance to provide that functionality when QA requested it.
    Larry

  • Printing Topics using WebHelp

    Can someone tell me how to add controls to my WebHelp project
    that will allow users to print a topic (similar to HTML Help)?
    Using the browser print functionality results in some of the
    page being "cut off".
    Thank you very much for your time and assistance,
    Nat

    Take a look at Snippets on my site.

  • Difficulties in printing topics.

    When I print a topic from a generated layout, the screen shot
    I have is cut off on the right hand side of the screen. The screen
    image is 800x600.

    Miwon -
    800 pixels wide on narrow page margins is about the limit
    when it comes to printing an image full size. Seems close to 100
    pixels per inch when printing a web page. Some solutions might be
    to use your RH Resize tool. It does a nice job of resizing, so you
    can still read any text (sometimes, depending on the degree of
    reduction).
    Or, if you have a primarily IE audience, you can use the
    @media print property of css. This way, you can resize your image
    only when your users print. Otherwise, it displays full screen.
    Here is an example you can try:

  • Printing topics and sub topics

    I'm using RoboHelp 7.0. When I generate MS HTML Help a user
    can select to print a selected topic or the selected heading and
    all the subtopics from the table of contents. When I generate
    WebHelp a user can only select to print one topic at a time. Is
    there any way to allow a user to print a main heading (book) and
    all the subtopics at once?

    Welcome to the forum
    Not in webhelp. The usual solution is to create PDFs and put
    links to them in your topics.

  • Advanced Printing Topic

    Hi All !!
    My Name is Carl & developed a java application using SWING the GUI is great you can see the it in next URL http://www.cs.buap.mx/~carlo/images/Minesys.jpg
    but it's very poor without a interesting print interface, how i do print the JTtextFields & the JTable in a sheet

    Your link doesn't work and your question is too vague, but here's code to print a gui component
    StandardPrint.java
    ===============
    package tjacobs.print;
    import java.awt.*;
    import java.awt.image.BufferedImage;
    import java.awt.print.*;
    import javax.print.PrintException;
    * StandardPrint is pretty groovy. This is one of my most used classes
    * This implements the Printable and Pageable java.awt.print interfaces
    * Allows you to very easily and quickly generate a printout from a component
    public class StandardPrint implements Printable, Pageable {
        Component c;
        SpecialPrint sp;
        PageFormat mFormat;
         boolean mScale = false;
         boolean mMaintainRatio = true;
        public StandardPrint(Component c) {
            this.c = c;
            if (c instanceof SpecialPrint) {
                sp = (SpecialPrint)c;
        public StandardPrint(SpecialPrint sp) {
            this.sp = sp;
         public boolean isPrintScaled () {
              return mScale;
         public void setPrintScaled(boolean b) {
              mScale = b;
         public boolean getMaintainsAspect() {
              return mMaintainRatio;
         public void setMaintainsAspect(boolean b) {
              mMaintainRatio = b;
        public void start() throws PrinterException {
            PrinterJob job = PrinterJob.getPrinterJob();
            if (mFormat == null) {
                mFormat = job.defaultPage();
            job.setPageable(this);
            if (job.printDialog()) {
                job.print();
        public void setPageFormat (PageFormat pf) {
            mFormat = pf;
        public void printStandardComponent (Pageable p) throws PrinterException {
            PrinterJob job = PrinterJob.getPrinterJob();
            job.setPageable(p);
            job.print();
        private Dimension getJobSize() {
            if (sp != null) {
                return sp.getPrintSize();
            else {
                return c.getSize();
        public static Image preview (int width, int height, Printable sp, PageFormat pf, int pageNo) {
            BufferedImage im = new BufferedImage(width, height, BufferedImage.TYPE_INT_RGB);
            return preview (im, sp, pf, pageNo);
        public static Image preview (Image im, Printable sp, PageFormat pf, int pageNo) {
            Graphics2D g = (Graphics2D) im.getGraphics();
            int width = im.getWidth(null);
            int height = im.getHeight(null);
            g.setColor(Color.WHITE);
            g.fillRect(0, 0, width, height);
            double hratio = height / pf.getHeight();
            double wratio = width / pf.getWidth();
            //g.scale(hratio, wratio);
            try {
                   sp.print(g, pf, pageNo);
              catch(PrinterException pe) {
                   pe.printStackTrace();
            g.dispose();
            return im;
        public int print(Graphics gr, PageFormat format, int pageNo) {
            mFormat = format;
            if (pageNo > getNumberOfPages()) {
                return Printable.NO_SUCH_PAGE;
            Graphics2D g = (Graphics2D) gr;
              g.drawRect(0, 0, (int)format.getWidth(), (int)format.getHeight());
            g.translate((int)format.getImageableX(), (int)format.getImageableY());
            Dimension size = getJobSize();
              if (!isPrintScaled()) {
                 int horizontal = getNumHorizontalPages();
                 int vertical = getNumVerticalPages();
                 int horizontalOffset = (int) ((pageNo % horizontal) * format.getImageableWidth());
                 int verticalOffset = (int) ((pageNo / vertical) * format.getImageableHeight());
                 double ratio = getScreenRatio();
                 g.scale(1 / ratio, 1 / ratio);
                 g.translate(-horizontalOffset, -verticalOffset);
                 if (sp != null) {
                     sp.printerPaint(g);
                 else {
                     c.paint(g);
                 g.translate(horizontal, vertical);
                 g.scale(ratio, ratio);
              else {
                 double ratio = getScreenRatio();
                 g.scale(1 / ratio, 1 / ratio);
                   double xScale = 1.0;
                   double yScale = 1.0;
                   double wid;
                   double ht;
                   if (sp != null) {
                        wid = sp.getPrintSize().width;
                        ht = sp.getPrintSize().height;
                   else {
                        wid = c.getWidth();
                        ht = c.getHeight();
                   xScale = format.getImageableWidth() / wid;
                   yScale = format.getImageableHeight() / ht;
                   if (getMaintainsAspect()) {
                        xScale = yScale = Math.min(xScale, yScale);
                   g.scale(xScale, yScale);
                   if (sp != null) {
                        sp.printerPaint(g);
                   else {
                        c.paint(g);
                   g.scale(1 / xScale, 1 / yScale);
                   g.scale(ratio, ratio);
             g.translate((int)-format.getImageableX(), (int)-format.getImageableY());     
            return Printable.PAGE_EXISTS;
        public int getNumHorizontalPages() {
            Dimension size = getJobSize();
            int imWidth = (int)mFormat.getImageableWidth();
            int pWidth = 1 + (int)(size.width / getScreenRatio() / imWidth) - (imWidth == size.width ? 1 : 0);
            return pWidth;
        private double getScreenRatio () {
            double res = Toolkit.getDefaultToolkit().getScreenResolution();
            double ratio = res / 72.0;
            return ratio;
        public int getNumVerticalPages() {
            Dimension size = getJobSize();
            int imHeight = (int)mFormat.getImageableHeight();
            int pHeight = (int) (1 + (size.height / getScreenRatio() / imHeight)) - (imHeight == size.height ? 1 : 0);
            return pHeight;
        public int getNumberOfPages() {
              if (isPrintScaled()) return 1;
            return getNumHorizontalPages() * getNumVerticalPages();
        public Printable getPrintable(int i) {
            return this;
        public PageFormat getPageFormat(int page) {
            if (mFormat == null) {
                PrinterJob job = PrinterJob.getPrinterJob();
                mFormat = job.defaultPage();
            return mFormat;
    SpecialPrint.java
    =============
    * Created on May 24, 2005 by @author Tom Jacobs
    package tjacobs.print;
    import java.awt.Dimension;
    import java.awt.Graphics;
    * Interface for using StandardPrint with something other than a Component or something
    * that needs special printing
    public interface SpecialPrint {
        public Dimension getPrintSize();
        public void printerPaint(Graphics g);
    }

  • WYSIWYG Printing Problems in Month View

    Does anyone know how to get printouts of the monthly calendar view to actually replicate what is on the screen? Even though I have set preferences to suppress times in the Month View (which does work on the screen), the times still appear when I print. Also, even though the text appears in the appropriate color on the screen (according to the color-coded task I have assigned), only the tiny leader bullet appears in color on the printed version.
    I have tried to set everything as an all-day event (which does suppress the times, as well as prints it in the appropriate color capsule), but this impacts the hierarchical ordering of the task on the calendar (ie. red tasks are homework, so I want them to appear as the last items on each day's tasks).
    Thanks for any insight you can offer!

    I'm also having a WYSIWYG in printing iCal. For me it's in the Week view. The event does not print out the way it appears on the screen. The problem started when I moved to the new iMac Intel computer. On my G3, it printed exactly as appeared on the screen. I can see the problem right on the Print screen (new in the latest version.)
    There are no updates for the computer. We've installed them all.
    I don't see any choices in the Preferences or the print screen that change anything. The exact problem is that the event appears as a tiny sliver in the time alloted on the week view - it doesn't take up the full time blocked out. It's as if the program is leaving extra space in case I want to add other events during the same time. When entering the event it looks great.
    Any ideas out there?
    iMac   Mac OS X (10.4.7)  

  • How do I print a topic using skin button?

    I have tried achieving this using the toolbarscripts01.js created by Willem Van Weeden on Peter Grainge's site. I've implemented .js in the skin for use with PDFs before, so I'm pretty sure I'm doing it right, but on click, nothing happens, when it should print. Script and instructions can be found here.
    http://www.grainge.org/pages/authoring/twisty/twisty.htm
    I'm using RH10 and outputting WebHelp.
    I should also mention that I first tried the method called Print Button for WebHelp on this page, but it didn't work either.
    http://www.grainge.org/pages/snippets/snippets.htm#print
    Has anyone else successfully created a print topic button in the skin nav bar? Any suggestions for alternatives or what I might be doing wrong?

    Neither of the scripts would be there unless they had been tried first.
    The first one has a Rh project set up that you can download. First please try that and confirm that it is working there.
    Are you testing on generated output rather than preview?
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Adding a print command to a topic

    Strange that they can't use the Print icon or right click and
    print a topic, but our users want a print command in FlashHelp
    topics that they can click to go to the Windows print dialog. I
    inserted the following javascript in the header of the topic
    template. It looks like this in the header with the actual print
    symbol from Wingdings 2 font:
    [Print symbol] Print Topic
    Here's the javascript:
    <a href="javascript:window.print()"style="x-condition:
    Online;"><span style="font-family: 'Wingdings 2',
    serif;font-size: 14pt; x-condition:
    Online;">6</span><span style="font-family: Arial,
    sans-serif; x-condition: Online;">Print Topic</a>
    I found how to do this at
    http://www.htmlgoodies.com/beyond/javascript/article.php/3471121

    You could write an AppleScript and save it as an application then drag the application to the toolbar. This script seems to work:
    tell application "Finder"
      print selection
    end tell

  • How can I print a topic in in Firefox and Netscape?

    I'm having trouble getting topics to print when webhelp is
    viewed in Netscape or Firefox. They print just fine in IE.
    I created a print link on the toolbar and used the following
    code ---
    javascript:parent.frames[1].bsscright.focus();window.print(); ---.
    It works great in IE, but I can't figure out what I need to do to
    make this work in Netscape or Firefox. I've tried a dozen different
    things, but haven't come up with a solution yet.
    Does anyone have advice? Thank you for any help!

    1. You need a skin that has a Print Topic button; (some don't
    have one).
    2. You need a revised JavaScript to put in the code for the
    Print Topic button. Find this in RH6/7: go to WebHelp Skin Editor
    > Toolbar tab > select Print (or Print Topic) > Edit icon.
    In the Custom Toolbar Item screen, select the Action tab. Click the
    radio button for Javascript, and in the OnClick field enter the NEW
    script below.
    window.parent.frames[1].frames[1].focus();
    window.parent.frames[1].frames[1].print();
    and Save.
    3. Remember to enable the toolbar Print button in Single
    Source Layouts > WebHelp Properties > WebHelp Generic screen.
    I have tested this in Internet Explorer 7, Mozilla Firefox 3,
    and it works OK. It also works in Apple Safari 3.1.2, although the
    printout is reduced in scale to about 80% of correct size (text and
    screenshots).
    Good luck, and please Spread the Word!

  • Problems printing published topics

    I'm sure this is a very basic question, but not being a programmer, I find myself learning as I go with RoboHelp. (Right now I'm using RoboHelp HTML6 - am hoping to upgrade to 8 in the near future.)
    When printing a published topic, the right margins are cut off. I know this happens often when printing from the internet, but am wondering what I can do to keep this from happening when users print topics to read offline. Is there a way to program the topics so they print the entire text (and pictures - the Help files are full of screen shots).
    Right now, the only thing I can tell people to do is set the margins in Page Setup to 0. That seems to work, but adds an extra step for the user.
    Again, I'm more of a writer than a technical person, but I do have access to people who have more programming/IT experience.
    You've been a great help in the past - I hope someone can do it for me again.
    Thanks!

    Try using one of the supplied style sheets to see if that makes a difference. If it does, then compare that CSS with yours. Post back if you need help on that.
    See www.grainge.org for RoboHelp and Authoring tips

  • Print Button on Drop-Down window

    Hello,
    our internal customer wants to be able to print topics from a
    drop-down window.
    This worked well with "RoboHelp for Word" and WinHelp output,
    but I fail to add the same functionality in a "Robohelp for HTML"
    (R 7) project with HTML Help (CHM) output. In fact the
    functionality seems to work (Topic is printed correctly), but in
    the window I immediately get a browser message that the content
    cannot be diplayed (topic disappears). The same is true for the
    "Copy" function (content is copied to windows clipboard but error
    message appears in the window). For the "Close" function the HTML
    help is minimized to the bottom tray. I added the following snippet
    <table x-use-null-cells style="background-color: #808080;
    width: 100%; height: 50px; border-style: 0;"
    height=50 width=100% bgcolor=#808080>
    <tr><td><implicit_p>
    <input type=submit name=button1 value=Print
    onClick="window.print();">
    <input type=submit name=button3 value=Copy
    onClick="javascript:CopiedTxt =
    ocument.body.createTextRange();CopiedTxt.execCommand('Copy')">
    <input type=submit name=button2 value=Close
    onClick="window.blur()">
    </td></tr>
    </table>
    What's wrong? Unfortunately I'm not fluent in Javascript :-(
    Regards, Pinkepunk

    Hi, Pete,
    Thanks for answering.
    > document.body.createTextRange();"
    The 'd' got lost when I formatted the post the forum.
    >onClick="hhctrl.Click()"
    HHCTRL does not seem to be know object in my project.
    The problem is not connected with the topic content. I
    created a test project from scratch with just two topics and the
    snippet in it: Same problem. The error page has the following
    address (right click):
    res://C:\WINNT\system32\shdoclc.dll/dnserror.htm#mk:@MSITStore:C:\Apps\Test\Test%20Buttons \TestSnippets\!SSL!\Microsoft_HTML_Help\TestSnippets.chm::/DropDown.htm?button2=Schlie%DFe n
    It seems that the page name is confusing RoboHelp:
    Schlie%DFen refers to the German "Schließen" which includes a
    special character.
    Regards, Pinkepunk

  • Suddenly unable to print from Win XP PCs to Time Capsule printer

    I have a Canon MP610 printer attached to my early 2009 (dual radio) Time Capsule that worked perfectly on my home LAN until a few weeks ago. Macbook Air and two Win XP PCs could print over the LAN. Suddenly LAN printing for the two Win PCs stopped working - but continues to work fine for the Macbook. The Win problem exists via wired and wifi connections. When I plug the printer directly into either PC's USB port, printing works perfectly. I have set up separate printer names for direct and LAN connections.
    The printer is visible to Bonjour. I re-installed Bonjour on one PC and tested using the printer name that it set up, verified that Norton firewall has USB port 5353 open, even disabled the firewall completely. Any print job sent from the PCs simply fails - the printer never gives any indication that it's receiving data.
    The only change to the Win systems since before I had this problem have been periodic auto-updates with Windows patches, and updated Safari.
    The fact that multiple Windows systems but not the Mac are having problems made me suspect Bonjour, but it can see the printer. If anyone has a clue what might be wrong, let me know.
    -JR

    I was able to solve my printing problem using the instructions at the iFelix site http://tech.ifelix.net/1004.html. The problem was solved after I replaced the printer name with the IP address of my Time Capsule (10.0.1.1) for the existing port that the printer was connected to (instead of creating a new port, I selected the existing port that my printer was connected to and clicked Configure Port). After saving, the next time that I tried to print it worked.
    Thanks to AppleConvert2009 who posted the iFelix URL containing the fix in the "Bonjour - printer found but can't print" topic in the Bonjour for Windows discussion.

  • Can the footer repeat on every printed page?

    I need the footer (part of the master page) to repeat on every printed page of a topic.
    Our client prints topics for use in the field and the footer contains time/date code (that I found on the internet). This date/time info needs to be printed on all pages of each topic. Most of the topics are 2-3 pages in length when printed from the browser. Is it possible to program the footer to repeat? or add HTML code to the topics to do this?
    I'm using RH 9, generating the WebHelp Pro layout for my output. Using IE9 and FireFox9 browsers. I've added a toolbar print button that uses the toolbarscripts01.js script to print the topics. (The script works great and is a HUGE life saver, by the way!! Thanks Peter Grainge!)
    Thanks,
    Shelley

    Hi Shelley
    We've already established in a separate thread that WebHelp Pro is not what you should be creating as you aren't using RoboHelp Server. But that really hasn't got anything to do with the footers.
    What you likely need to do is to supply a PDF that will be used to print. When RoboHelp creates Printed Documentation it first creates a Word document. And if you have elected to create a PDF, the PDF is created from the Word document. So what you can do is to forego the PDF from RoboHelp and manually tweak the Word document to add the desired footers. Then you could create a PDF from that to supply to the user.
    Cheers... Rick
    Helpful and Handy Links
    RoboHelp Wish Form/Bug Reporting Form
    Begin learning RoboHelp HTML 7, 8 or 9 within the day!
    Adobe Certified RoboHelp HTML Training
    SorcerStone Blog
    RoboHelp eBooks

Maybe you are looking for