Re: [xep-support] Errors in PDF files generated from XEP

Hello Mats,

(I cannot make the page counter work on PDFs from any version of XEP.)

I really doubt that there is a tool that would calculate color pages and
see if they are adjacent. But you can think of creating one of your own.

The XEP intemediate output format may be used for page counting and
finding non-grayscale elements (not including images) on pages. All with
XSLT. Checking if colored pages are adjacent is also simple.
As for the images, you will need an external tool to see if they are
gray-scale or colored.
See "-xep" output specifier of XEP command line and XEP Intermediate
Format Specification in the reference.

-- 
Best regards,
  Michael Sulyaev   mailto:msulyaev@renderx.com
RenderX
On Wed, 01 Feb 2006 16:59:48 +0300, Broberg, Mats <mabr@flir.se> wrote:
> Michael,
>
> Thanks for your input and comments. Seem like unreliable tools, possibly
> apart from the linearization issue. Odd though, that the page counter
> could calculate correct number of pages in files from XEP 4.3 but not
> from XEP 4.4.
>
> Regarding PDF page counting, we need a tool that counts pages in batches
> of XEP-generated PDF files, and that can generate a TXT, CSV or XLS
> report. We need this report to make approximate purchase prices for our
> users' manuals.
>
> Actually, what we would ideally need is a feature that generates a TXT,
> CSV or XLS report on-the-fly of how many color pages there are in a
> XEP-generated PDF manual and if they are adjacent or non-adjacent to
> each other. That way we could calculate even better prices.
>
> Best regards,
> Mats Broberg
> Technical Documentation Manager
>
> www.flirthermography.com
>
>
>> -----Original Message-----
>> From: owner-xep-support@renderx.com
>> [mailto:owner-xep-support@renderx.com] On Behalf Of Michael Sulyaev
>> Sent: den 1 februari 2006 12:33
>> To: xep-support@renderx.com
>> Subject: Re: [xep-support] Errors in PDF files generated from XEP
>>
>> Hello Mats,
>>
>> You are using very interesting tools:
>>
>> 1) PDF page counter (trial) finds "-1" page in any PDF (I
>> have lots of them), including one created online on the Adobe
>> site from a plaint text file. So the tool seems to be just broken.
>>
>> 2) PDF Desktop Repair Tool finds no errors in
>> examples/hammer.pdf (see XEP
>> distribution) if LINEARIZE="false" in xep.xml (checked on the
>> lastest build of XEP: 4.5 20060123). Otherwize if
>> linearization is enabled, the Repair tool finds one error
>> (The "Length" attribute of the stream object is wrong"). This
>> error could possibly be relevant, because we know there are
>> some limitations in the linearization algorythms.
>> Nevertheless, this file can be opened with Acrobat Reader and
>> printed, issuing no errors or warnings.
>> An interesting thing is that PDF Desktop Repair Tool finds
>> lots of errors in it's own documentation file repd.pdf
>> (although it opens fine in Acrobat Reader). If I choose to
>> repair it, the tool creates a new file, which does not show
>> correctly on Acrobat, and is reported to have many errors by
>> the Tool. The next iteration of "repair" process creates a
>> file with no content and all the original bookmarks.
>> I would not recomment using this tool in production.
>>
>> Now to the page counting.
>> If you have Connectivity Kit
>> (http://www.renderx.com/tools/devkit.html),
>> than you may wish to see the PageCount.java example. It
>> counts number of pages generated during the generation process.
>> If you do not have Connectivity Kit, than you are bound to
>> use third-party tools, or develop one yourself e.g. via a regexp.
>>
>>
>> On Tue, 31 Jan 2006 19:04:44 +0300, Broberg, Mats
>> <mabr@flir.se> wrote:
>>
>> > Michael,
>> > I know that many companies all over the world sucessfully
>> produce PDF
>> > files using XEP. Our company is one of them, as you can read in the
>> > customer success story on the RenderX website... :) And
>> we're a very
>> > grateful customer, too.
>> > The files opens and print fine. I am just curious why these
>> errors are
>> > reported. I checked the file using
>> > http://www.pdf-tools.com/asp/products.asp?name=repd
>> > <http://www.pdf-tools.com/asp/products.asp?name=repd> . The
>> reason I
>> > checked the files was that a PDF page counter I have used
>> for several
>> > years (http://www.sherrodcomputers.com/products_pdfdeluxe.cfm
>> > <http://www.sherrodcomputers.com/products_pdfdeluxe.cfm> )
>> has stopped
>> > working for files from XEP 4.4. For those files it is not
>> possible to
>> > count PDF pages using that software anymore.
>> > I'm curious why these errors are reported.
>> > Best regards,
>> > Mats Broberg
>> > Technical Documentation Manager
>> >
>> > www.flirthermography.com <http://www.flirthermography.com>
>> >
>> > ________________________________
>> >
>> > From: owner-xep-support@renderx.com on behalf of Michael Sulyaev
>> > Sent: Tue 2006-01-31 16:08
>> > To: xep-support@renderx.com
>> > Subject: Re: [xep-support] Errors in PDF files generated from XEP
>> >
>> >
>> >
>> > Hello Mats,
>> >
>> > Any file with half a thouand serious errors would be
>> completely unusable.
>> > Can you open it with Acrobat Reader?
>> >
>> > Many companies and individuals all over the world produce PDF files
>> > using XEP, so I suppose there are less errors in PDF than you say.
>> >
>> > I suspect there is something wrong with the analysis tool
>> or the way
>> > it is used.
>> >
>> > --
>> > Best regards,
>> >   Michael Sulyaev   mailto:msulyaev@renderx.com
>> > <mailto:msulyaev@renderx.com>
>> > RenderX
>> >
>> > On Tue, 31 Jan 2006 12:31:29 +0300, Broberg, Mats
>> <mabr@flir.se> wrote:
>> >
>> >> Dear all,
>> >>
>> >> I ran a PDF analysis tools on a batch of files that were generated
>> >> using XEP 3.8.4, 4.3, and 4.4 and the analysis tool
>> typically returns
>> >> about 400-500 of these errors in each file:
>> >>
>> >>
>> >> "80410052 A begin text operator is missing"
>> >>
>> >> "80410053 An end text operator is missing"
>> >>
>> >> "80410026 The "Length" attribute of the stream object is wrong"
>> >>
>> >>
>> >> Why do these errors occur in PDF files generated using XEP?
>> >>
>> >> Best regards,
>> >> Mats Broberg
>> >> Technical Documentation Manager
>> >>
>> >> www.flirthermography.com
>> >>
>> >> -------------------
>> >> (*) To unsubscribe, send a message with words 'unsubscribe
>> xep-support'
>> >> in the body of the message to majordomo@renderx.com from
>> the address
>> >> you are subscribed from.
>> >> (*) By using the Service, you expressly agree to these Terms of
>> >> Service http://www.renderx.com/terms-of-service.html
>> >> <http://www.renderx.com/terms-of-service.html>
>> >
>> >
>> >
>> > -------------------
>> > (*) To unsubscribe, send a message with words 'unsubscribe
>> xep-support'
>> > in the body of the message to majordomo@renderx.com from
>> the address
>> > you are subscribed from.
>> > (*) By using the Service, you expressly agree to these Terms of
>> > Service http://www.renderx.com/terms-of-service.html
>> > <http://www.renderx.com/terms-of-service.html>
>> >
>> >
>>
>>
>>
>> --
>> Best regards,
>>   Michael Sulyaev   mailto:msulyaev@renderx.com
>> RenderX
>> -------------------
>> (*) To unsubscribe, send a message with words 'unsubscribe
>> xep-support'
>> in the body of the message to majordomo@renderx.com from the address
>> you are subscribed from.
>> (*) By using the Service, you expressly agree to these Terms
>> of Service http://www.renderx.com/terms-of-service.html
>>
>
> -------------------
> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
> in the body of the message to majordomo@renderx.com from the address
> you are subscribed from.
> (*) By using the Service, you expressly agree to these Terms of Service  
> http://www.renderx.com/terms-of-service.html
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html