[xep-support] [SPAM] RE: Xep-support Digest, Vol 24, Issue 6

From: Meyer, Lauren <lmeyer@vocollect.com> Date: Fri Sep 28 2012 - 04:41:24 PDT · >From xep.xml:

--
Gru?/Regards,
    Thomas Schraitle
------------------------------
Message: 2
Date: Thu, 27 Sep 2012 14:05:45 +0400
From: Alexey Gagarinov <agagarinov@renderx.com>
To: RenderX Community Support List <xep-support@renderx.com>
Subject: [xep-support] Re: Rendering Thai font in PDF
Message-ID: <506424F9.5070909@renderx.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Lauren,
Could you please send the xep.xml and a sample FO (as small as possible) to support@renderx.com?
Regards,
   Alexey Gagarinov
RenderX
---
www.renderx.com
------------------------------
Message: 3
Date: Thu, 27 Sep 2012 14:16:17 +0400
From: Alexey Gagarinov <agagarinov@renderx.com>
To: RenderX Community Support List <xep-support@renderx.com>
Subject: [xep-support] Re: Abort when Image File not found?
Message-ID: <50642771.7020404@renderx.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Thomas,
> when XEP tries to find an image file and it can't, it proceeds in the 
> rendering process and shows the 404 image in the output format.
> I would like to stop XEP in case an image cannot be found.
>
> How can I do this?
There is no "official" way to stop XEP when an image is not found.
Where and why you need this behavior?
Regards,
   Alexey Gagarinov
RenderX
---
www.renderx.com
------------------------------
Message: 4
Date: Thu, 27 Sep 2012 12:03:56 +0100
From: John Maddock <boost.regex@virgin.net>
To: "RenderX Community Support List" <xep-support@renderx.com>
Subject: [xep-support] Re: Abort when Image File not found?
Message-ID: <E297E7BEAD8B4202BAAEFE34023AE1AA@acerlaptop>
Content-Type: text/plain; format=flowed; charset="UTF-8";
	reply-type=original
> when XEP tries to find an image file and it can't, it proceeds in the 
> rendering process and shows the 404 image in the output format.
> I would like to stop XEP in case an image cannot be found.
>
> How can I do this?
I'd like to know that as well, the default behavior just generates a warning for a missing image too, should be listed as an error in the output at least.
John Maddock. 
!DSPAM:87,506432b263731498812583!
------------------------------
Message: 5
Date: Thu, 27 Sep 2012 13:23:31 +0200
From: Michael Sulyaev <msulyaev@renderx.com>
To: RenderX Community Support List <xep-support@renderx.com>
Subject: [xep-support] Re: Abort when Image File not found?
Message-ID: <50643733.1040808@renderx.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 09/27/2012 12:16 PM, Alexey Gagarinov wrote:
> There is no "official" way to stop XEP when an image is not found.
One could implement his own logger (see devkit), match the events of interest and terminate processing.
Regards,
Mike
------------------------------
Message: 6
Date: Thu, 27 Sep 2012 14:00:09 +0200
From: Thomas Schraitle <tom_schr@web.de>
To: xep-support@renderx.com
Subject: [xep-support] Re: Abort when Image File not found?
Message-ID: <20120927140009.43df4276@edison.suse.de>
Content-Type: text/plain; charset=UTF-8
Hi Alexey,
On Thu, 27 Sep 2012 14:16:17 +0400
Alexey Gagarinov <agagarinov@renderx.com> wrote:
 
> > when XEP tries to find an image file and it can't, it proceeds in 
> > the rendering process and shows the 404 image in the output format.
> > I would like to stop XEP in case an image cannot be found.
> >
> > How can I do this?
> 
> There is no "official" way to stop XEP when an image is not found.
> Where and why you need this behavior?
Well, consider it as an early "quality control alarm". :) If XEP has built a PDF, is the PDF correct? Maybe, maybe not. If you haven't looked at the (error?) messages, you can't tell.
The only way to tell is to browse through your 600 or so pages to find the missing images. Not very nice.
The question is, should XEP abort the rendering process if it can't find an image. Well, probably the FO spec gives you some freedom in this regard. I would propose to make it either an option in the configuration or in the command line. 
With such a configuration method, people can switch the behaviour: when they are writing their documents, missing images are not very serious as they will be added later. However, if they create the final document, any missing pieces should are fatal and so should be any error messages (which means, abort).
That would make such an error obvious and you won't deliver broken PDFs anymore.
--
Gru?/Regards,
    Thomas Schraitle
!DSPAM:87,50643fe863731083312073!
------------------------------
Message: 7
Date: Thu, 27 Sep 2012 17:23:37 +0000
From: Kirch Fritz <Friedrich.Kirch@it2media.de>
To: RenderX Community Support List <xep-support@renderx.com>
Subject: [xep-support] [SPAM] AW:  Re: Abort when Image File not
	found?
Message-ID:
	<C5E8452D51566246BBFAD52197F976EE1635119B@IT2m1234.it2mbizz.de>
Content-Type: text/plain; charset="utf-8"
Hi,
the easiest thing would be to create XEPOUT intermediate format in a first step.
If XEPOUT doesn?t contain the 404 image everything is ok and you can continue producing a correct PDF.
Otherwise don?t create the PDF.
Fritz Kirch
-----Urspr?ngliche Nachricht-----
Von: xep-support-bounces@renderx.com [mailto:xep-support-bounces@renderx.com] Im Auftrag von Thomas Schraitle
Gesendet: Donnerstag, 27. September 2012 14:00
An: xep-support@renderx.com
Betreff: [xep-support] Re: Abort when Image File not found?
Hi Alexey,
On Thu, 27 Sep 2012 14:16:17 +0400
Alexey Gagarinov <agagarinov@renderx.com> wrote:
 
> > when XEP tries to find an image file and it can't, it proceeds in 
> > the rendering process and shows the 404 image in the output format.
> > I would like to stop XEP in case an image cannot be found.
> >
> > How can I do this?
> 
> There is no "official" way to stop XEP when an image is not found.
> Where and why you need this behavior?
Well, consider it as an early "quality control alarm". :) If XEP has built a PDF, is the PDF correct? Maybe, maybe not. If you haven't looked at the (error?) messages, you can't tell.
The only way to tell is to browse through your 600 or so pages to find the missing images. Not very nice.
The question is, should XEP abort the rendering process if it can't find an image. Well, probably the FO spec gives you some freedom in this regard. I would propose to make it either an option in the configuration or in the command line. 
With such a configuration method, people can switch the behaviour: when they are writing their documents, missing images are not very serious as they will be added later. However, if they create the final document, any missing pieces should are fatal and so should be any error messages (which means, abort).
That would make such an error obvious and you won't deliver broken PDFs anymore.
--
Gru?/Regards,
    Thomas Schraitle
_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w ww.renderx.com/terms-of-service.html
**********************************************************************
Diese E-Mail wurde auf Viren ueberprueft.
mailsweeper@it2media.de
**********************************************************************
***SPAM***
!DSPAM:87,50648bbb63731490315428!
------------------------------
Message: 8
Date: Thu, 27 Sep 2012 10:55:50 -0700
From: "Kevin Brown" <kevin@renderx.com>
To: "'RenderX Community Support List'" <xep-support@renderx.com>
Subject: [xep-support] Re: [SPAM] AW:  Re: Abort when Image File not
	found?
Message-ID: <017901cd9cd9$548040a0$fd80c1e0$@com>
Content-Type: text/plain;	charset="utf-8"
Well, creating XEP format is normally 90% of the job so one could almost as easily just look at the log and see a warning of an image not found. 
Alexey is correct in the proper way. One could get the developer's kit and write their own processing method. 
If you examine the API, you will see all of these messages -- INFO, WARNING and ERROR all are events that are logged. One would parse the WARNING message to determine if the message is from a missing image (they may wish to do the same for a missing font) and raise an event to abort the formatting if that is the case. They could write their own command line (if that is how they are calling it) and add something like -abortonwarning as a switch to that command line to trigger this behavior.
We can take this as a requirement for future release of the software, but we would also be happy to share the code for this in Java to anyone who wishes to implement on their own and provide back to the group.
Kevin Brown
RenderX
-----Original Message-----
From: xep-support-bounces@renderx.com [mailto:xep-support-bounces@renderx.com] On Behalf Of Kirch Fritz
Sent: Thursday, September 27, 2012 10:24 AM
To: RenderX Community Support List
Subject: [xep-support] [SPAM] AW: Re: Abort when Image File not found?
Hi,
the easiest thing would be to create XEPOUT intermediate format in a first step.
If XEPOUT doesn?t contain the 404 image everything is ok and you can continue producing a correct PDF.
Otherwise don?t create the PDF.
Fritz Kirch
-----Urspr?ngliche Nachricht-----
Von: xep-support-bounces@renderx.com [mailto:xep-support-bounces@renderx.com] Im Auftrag von Thomas Schraitle
Gesendet: Donnerstag, 27. September 2012 14:00
An: xep-support@renderx.com
Betreff: [xep-support] Re: Abort when Image File not found?
Hi Alexey,
On Thu, 27 Sep 2012 14:16:17 +0400
Alexey Gagarinov <agagarinov@renderx.com> wrote:
 
> > when XEP tries to find an image file and it can't, it proceeds in 
> > the rendering process and shows the 404 image in the output format.
> > I would like to stop XEP in case an image cannot be found.
> >
> > How can I do this?
> 
> There is no "official" way to stop XEP when an image is not found.
> Where and why you need this behavior?
Well, consider it as an early "quality control alarm". :) If XEP has built a PDF, is the PDF correct? Maybe, maybe not. If you haven't looked at the (error?) messages, you can't tell.
The only way to tell is to browse through your 600 or so pages to find the missing images. Not very nice.
The question is, should XEP abort the rendering process if it can't find an image. Well, probably the FO spec gives you some freedom in this regard. I would propose to make it either an option in the configuration or in the command line. 
With such a configuration method, people can switch the behaviour: when they are writing their documents, missing images are not very serious as they will be added later. However, if they create the final document, any missing pieces should are fatal and so should be any error messages (which means, abort).
That would make such an error obvious and you won't deliver broken PDFs anymore.
--
Gru?/Regards,
    Thomas Schraitle
_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w ww.renderx.com/terms-of-service.html
**********************************************************************
Diese E-Mail wurde auf Viren ueberprueft.
mailsweeper@it2media.de
**********************************************************************
***SPAM***
!DSPAM:87,50648bbb63731490315428!
_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w ww.renderx.com/terms-of-service.html
------------------------------
Message: 9
Date: Thu, 27 Sep 2012 20:50:56 +0200
From: Thomas Schraitle <tom_schr@web.de>
To: kevin@renderx.com, RenderX Community Support List
	<xep-support@renderx.com>
Subject: [xep-support] Re: Abort when Image File not found?
Message-ID: <2018707.9audtalaHf@erde>
Content-Type: text/plain; charset="utf-8"
Hi,
Am Donnerstag, 27. September 2012, 10:55:50 schrieb Kevin Brown:
> Well, creating XEP format is normally 90% of the job so one could 
> almost as easily just look at the log and see a warning of an image not found.
If you don't have a developer kit, it means, parsing the log is the only option. *sigh*
> Alexey is correct in the proper way. One could get the developer's kit 
> and write their own processing method. 
> [...]
I believe the developer kit can do a lot of nice and nifty things. However, 
paying over $1.000 for a developer kit for parsing simple error logs is just 
out of scope, sorry.
 
> We can take this as a requirement for future release of the software, but we
> would also be happy to share the code for this in Java to anyone who wishes
> to implement on their own and provide back to the group.
Please consider it implementing it in a future release. That would really help 
a LOT. 
Thanks! :)
-- 
Gru?/Regards
  Thomas Schraitle
!DSPAM:87,5064a02d63731720410058!
------------------------------
_______________________________________________
Xep-support mailing list
Xep-support@renderx.com
http://lists.renderx.com/mailman/listinfo/xep-support
End of Xep-support Digest, Vol 24, Issue 6
******************************************
This message is intended only for the named recipient. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of this information is strictly prohibited.
***SPAM***
!DSPAM:87,50658d0e63731551385565!
_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
ww.renderx.com/terms-of-service.html