On 12.05.2006 09:50:01 mm wrote:
> > Simon Pepping wrote:
> >
>
> >>
> >> Regarding a configuration file per printing run, recently a similar
> >> possibility was put forward for the user preferences for
> >> printer-specific image handling and other options. In a recent
> >> fop-user post I sugg
On Fri, May 12, 2006 at 03:50:01PM +0800, [EMAIL PROTECTED] wrote:
> > Simon Pepping wrote:
> >
> However, I now feel the need to comment from a developers point of view,
> i.e. a developer who uses fop in high volume backend business processes.
>
> If I would have to deal with creating per docume
> Simon Pepping wrote:
>
>>
>> Regarding a configuration file per printing run, recently a similar
>> possibility was put forward for the user preferences for
>> printer-specific image handling and other options. In a recent
>> fop-user post I suggested the idea of hyphenation exceptions in a
>> c
On Thu, May 11, 2006 at 08:55:24AM +0100, Chris Bowditch wrote:
> Simon Pepping wrote:
>
> >So definitely a configuration external to the FO file. And something
> >like the Java Printing System to know the installed printer
> >configuration and provide the user with the appropriate GUI and
> >choi
Simon Pepping wrote:
Hi,
I read the long discussion between Jeremias and Chris, and Jörg's
note.
I do not like the idea of extension elements. I think, here I refer
back to a recent post by Glen about standard FO files. I like the idea
of a configuration file. Even a different configuration fi
Jeremias Maerki wrote:
We can throw exceptions if no mapping is found, or the stuff is simply
printed on the default paper and people will quickly figure out that
they've done something wrong.
Well, having printed large documents on partly manually fed
special paper I know that even small error
Hi,
I read the long discussion between Jeremias and Chris, and Jörg's
note.
I do not like the idea of extension elements. I think, here I refer
back to a recent post by Glen about standard FO files. I like the idea
of a configuration file. Even a different configuration file for each
single docum
On 09.05.2006 17:13:40 Chris Bowditch wrote:
> Jeremias Maerki wrote:
>
> > On 09.05.2006 16:04:37 Chris Bowditch wrote:
> >
> >>Jeremias Maerki wrote:
> >>
> >>
> >>>On 09.05.2006 13:35:11 Chris Bowditch wrote:
>
> > This renderer configuration is still implemented as an extension. It's
> > j
On 09.05.2006 23:57:24 J.Pietschmann wrote:
> Jeremias Maerki wrote:
> > Attention: long post. :-)
> [snip stuff which reminds me on reinventing TeX/DVI]
>
> Using the page master name to map onto output media suggests that
> different page flows could be printed on different media. Is this
> cor
Jeremias Maerki wrote:
Attention: long post. :-)
[snip stuff which reminds me on reinventing TeX/DVI]
Using the page master name to map onto output media suggests that
different page flows could be printed on different media. Is this
correct?
I don't like the idea of using the name of single-pa
Jeremias Maerki wrote:
On 09.05.2006 16:04:37 Chris Bowditch wrote:
Jeremias Maerki wrote:
On 09.05.2006 13:35:11 Chris Bowditch wrote:
Yes I agree that /MediaType is the most widely used way, but we have
customers out there using /MediaPosition too. The bit I don't understand
in yo
On 09.05.2006 16:04:37 Chris Bowditch wrote:
> Jeremias Maerki wrote:
>
> > On 09.05.2006 13:35:11 Chris Bowditch wrote:
> >>As you've already mentioned in PS there is more than one way of
> >>specifying tray selection. So assuming one particular way (/MediaType)
> >>would be rather limiting i
Jeremias Maerki wrote:
On 09.05.2006 13:35:11 Chris Bowditch wrote:
I'm sorry Jeremias, your arguments here have failed to convince me that
your suggested approach is the best way. I'm still in favour of using
extension elements for PS, PCL and AFP. It should be possible to add the
exte
On 09.05.2006 13:35:11 Chris Bowditch wrote:
> Jeremias Maerki wrote:
>
>
>
> > Conclusion:
> > Using the master-name approach instead of including printer-specific
> > commands adds flexibility for media and paper tray selection. The only
> > thing that will be useful is a parameter to FOP and
Jeremias Maerki wrote:
Conclusion:
Using the master-name approach instead of including printer-specific
commands adds flexibility for media and paper tray selection. The only
thing that will be useful is a parameter to FOP and/or an extension
value in XSL-FO which specifies the actualy printer
15 matches
Mail list logo
