RE: FM 12 + RH 11 OR WebWorks ePublisher

2014-03-15 Thread Keith Soltys
I’m running WebWorks on a six-year-old quad-core Pentium with 2 GB RAM under Windows XP, with my books and projects stored on our network, and have never found performance to be a serious issue. Mind you, my largest document is only about 300 pages if printed. I don’t think getting stationery

Re: FM 12 + RH 11 OR WebWorks ePublisher

2014-03-15 Thread Robert Lauriston
Are you speaking specifically about PDF there? I found the web help stationery usable pretty much out of the box. On Thu, Mar 13, 2014 at 7:47 AM, gr...@hedgewizard.net gr...@hedgewizard.net wrote: ePub is quite good at creating PDFs, but there are a couple of caveats: ... Finally: It takes

RE: FM 12 + RH 11 OR WebWorks ePublisher

2014-03-15 Thread gr...@hedgewizard.net
Hey Keith— I'm pleased to read that ePub is working for you. I don't find it a *bad* tool, just problematic (and every tool has its own problems). I was reporting on the experience I and the other writers at my current employer have found; which was that the more local you could make things, the

Re: FM 12 + RH 11 OR WebWorks ePublisher

2014-03-15 Thread gr...@hedgewizard.net
I wasn't around for the OOB version, so I don't know how much work needed to be done for the initial setup; I just know by anecdote that maintenance for both was apparently a PITA for the person responsible. On March 13, 2014 at 2:33 PM Robert Lauriston rob...@lauriston.com wrote: Are you

Re: TOC Failure

2014-03-15 Thread Robert Lauriston
I think you can rename the bad file, create a new TOC with the add file command, and cut and paste the reference page content from the old file to the new one. On Thu, Mar 13, 2014 at 2:20 PM, Craig, Alison alison.cr...@ultrasonix.com wrote: I received a request for help from my counterparts at

Re: TOC Failure

2014-03-15 Thread Heiko Haida
Hi Alison, this is a problem that I very often have: My colleagues are using the English installation of FrameMaker which uses name extensions like TOC, SIX, and para formats like body, and so on, whereas my German Frame uses IVZ, IX, Haupttext, and so on. My installation does not always

Turkish Font Issue

2014-03-15 Thread Alan Salo (Ariens Plant 1)
Happy Friday! My team is using FrameMaker 11 to build our international manuals. This problem occurs on two of the workstations: When using Adobe Distiller to print a Turkish-language file to a PDF we have font errors where certain characters do not distill correctly and appear as boxes. The

tracking Help page usage

2014-03-15 Thread hessiansx4
We are currently not doing context-sensitive help; instead, users click a Help icon which launches a nice, long doc. Do any of you Framers have any experience tracking doc/page usage? We are comparing Google analytics or RH server. Is anyone using some open source tool they would recommend?

xdocbook not preserving white space

2014-03-15 Thread Robert Carel
Framemaker keeps removing white space (for the programlisting element, for example) upon import, or save and reopen, for xDocbook documents. I changed the control in the maker.ini file, RemoveExtraWhiteSpacesOnXMLImport=Off, but this appears to do nothing. Am I missing something? Robert Carel

Re: What do you all recommend for showing space characters?

2014-03-15 Thread Ed Nodland
How about ␣ (Unicode U+2423, decimal 9251, *open box*). Source: http://en.wikipedia.org/wiki/Whitespace_character Visible Symbol. back in the 70's we used a ^ near the bottom of the line, but that was when writing out code on paper was done before punching it onto cards or paper tape. Ed

Re: tracking Help page usage

2014-03-15 Thread David Spreadbury
I question why ...one long doc... when there are so many easy to use, free or almost free, tools available that can produce a usable help file with full TOC and hyperlinks across chapters from the original source. Context sensitive help is great is time allows for it. It requires collaboration

RE: What do you all recommend for showing space characters?

2014-03-15 Thread Syed Zaeem Hosain (syed.hos...@aeris.net)
Hi, Alan. An update (sent to the list too, in case it helps others). In LaTeX, the \textvisiblespace{} worked perfectly. In FrameMaker, not surprisingly, it depends on the font. Some fonts have the U+2423 Open Box character, others do not (even though they may have other Unicode characters).