I think you mentioned exploring HTML+CSS for print a few days ago. Is
that because FO might be at the end of it's road?
Thanks!
Peter
On Tue, Dec 10, 2013 at 9:49 AM, Norman Walsh wrote:
> "Jan Tosovsky" writes:
>
>> On 2013-12-09 Norman Walsh wrote:
>>>
>>> ... future work on XSL FO has large
"Jan Tosovsky" writes:
> On 2013-12-09 Norman Walsh wrote:
>>
>> ... future work on XSL FO has largely been abandoned.
>
> Does it mean that XSL-FO 2.0/next is not planned any more? Is there any
> citation for this?
http://www.w3.org/XML/XPPL/
"This WOrking (sic) Group is no longer active, b
On 10/12/13 09:41, Frank Arensmeier wrote:
10 dec 2013 kl. 07:59 skrev davep :
On 09/12/13 16:09, Norman Walsh wrote:
I can see you getting 80% with html and CSS... My penneth says
you'll fall over on the 20% so I'm -1 on this. Do you believe
you can do it? What of re-ordering, toc etc?
Oh,
10 dec 2013 kl. 07:59 skrev davep :
> On 09/12/13 16:09, Norman Walsh wrote:
>
>>> I can see you getting 80% with html and CSS...
>>> My penneth says you'll fall over on the 20% so I'm -1 on this.
>>> Do you believe you can do it?
>>> What of re-ordering, toc etc?
>>
>> Oh, you'd need a "for p
On 09/12/13 16:09, Norman Walsh wrote:
I can see you getting 80% with html and CSS...
My penneth says you'll fall over on the 20% so I'm -1 on this.
Do you believe you can do it?
What of re-ordering, toc etc?
Oh, you'd need a "for print" HTML stylesheet. There's lots of things
that CSS can'
On 2013-12-09 Norman Walsh wrote:
>
> ... future work on XSL FO has largely been abandoned.
Does it mean that XSL-FO 2.0/next is not planned any more? Is there any
citation for this?
Thanks, Jan
-
To unsubscribe, e-mail: docbo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/09/2013 10:11 AM, Norman Walsh wrote:
> You can't cut and paste the verbatim display's now either. In
> fact, one reason to go with tables is to make that part work. All
> the numbers go in the first column, the lines in the second, so you
> can,
Bob Stayton writes:
> What composition engines do you have in mind for rendering HTML+CSS to print?
I've tried both PrinceXML and AntennaHouse with some success.
Be seeing you,
norm
--
Norman Walsh | Time i
"Jan Tosovsky" writes:
> While I don't plan to upgrade my generating workflow to XSL 2.0 stylesheets
> in the near future, I am quite curious whether the proposed HTML+CSS
> approach can really cover all common needs:
>
> 1. ToC and Index with page numbers
> 2. Bookmarks
> 3. Double-sided version
David Cramer writes:
> One caveat about using tables for line numbers. It generally makes it
> impossible to cut and paste the code sample without getting all the line
> numbers. One thing I like about the syntax highlighter above is that
> when you click on the code sample, the callouts go away a
davep writes:
> No problem with line numbers. I guess it's the outcome we want
> rather than how it is done?
> Would that work with insertions too? E.g. lines with (6) etc
> which are referred to in commentary?
Yes, that should still work.
>> As long as I'm airing dirty laundry, I'm also tempt
11 matches
Mail list logo
