Ron Wheeler created FOP-2543:
Summary: The avalon-framework-api-4.2.0 is broken and 4.3.1 is the
current version
Key: FOP-2543
URL: https://issues.apache.org/jira/browse/FOP-2543
Project: FOP
apply.
Thanks
Ron
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
, Ron Wheeler
rwhee...@artifact-software.com
mailto:rwhee...@artifact-software.com wrote:
You are right , of course.
However, this very large community ( one DITA LinkedIn group has
4,600 members, the Technical Doc group has over 14,000 members)
does not see themselves as users
improved, although I agree that
there is room for improvement in this feature.
On 5/23/14, 4:14 PM, Ron Wheeler wrote:
The conversation below shows one of the reasons why I would like to see DITA
become part of the XMLGraphics family.
One of the most experienced and influential DITA
/fo:block
/fo:block
I'm viewing the PDFs in Abobe Reader, but that hasn't made a difference
in the past.
Any idea what's going on?
Thanks for any insights.
yyy
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype
On 01/04/2014 1:33 PM, Jan Tosovsky wrote:
On 2014-03-30 Ron Wheeler wrote:
On 30/03/2014 5:19 PM, Jan Tosovsky wrote:
I personally think it would be much easier to attract developers
to create a completely new paged media CSS engine than to add
several niche XSL-FO features into FOP. But when
, Jan Tosovsky wrote:
On 2014-03-26 Ron Wheeler wrote:
On 26/03/2014 2:59 PM, Jan Tosovsky wrote:
On 2014-03-26 Christopher R. Maden wrote:
Although I don’t get a vote, I completely agree with Glenn that DITA
integration into FOP is completely inappropriate.
+1
FOP consumes standardized XSL-FO
:
On 27/03/14 18:32, Ron Wheeler wrote:
I think that you are right about being a sister project to FOP within
XMLGraphics.
The discussion from everyone has been very helpful even if the writer
was
negative to the idea.
//I would be happy to see some interaction in a number of areas.
a) Clearly
for the DITA community. That way there
would be some links between the 2 projects and an oversight of both
from a common committee. This should help to improve interoperability
a little although perhaps not to the extent you had hoped for.
Thanks,
Chris
On 26/03/2014 14:42, Ron Wheeler wrote:
The DITA
in considering adding front-end XML
processing to the FOP production project?
Ron
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
On 26/03/2014 11:46 AM, Glenn Adams wrote:
On Wed, Mar 26, 2014 at 8:42 AM, Ron Wheeler
rwhee...@artifact-software.com
mailto:rwhee...@artifact-software.com wrote:
The DITA-OT (DITA Open Toolkit) (http://www.ditaopentoolkit.org/)
is an open source project that depends on FOP
On 26/03/2014 12:25 PM, Glenn Adams wrote:
On Wed, Mar 26, 2014 at 10:14 AM, Ron Wheeler
rwhee...@artifact-software.com
mailto:rwhee...@artifact-software.com wrote:
On 26/03/2014 11:46 AM, Glenn Adams wrote:
On Wed, Mar 26, 2014 at 8:42 AM, Ron Wheeler
rwhee...@artifact
the
enhancement plans.
~Chris
[*] My entire experience with DITA has been around an MS-Word-centric
publication system, going into and out of Office Open XML, with no XSL
in sight.
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970
fixed.
They have tended to accept that FOP is static and can not respond to the
needs of the document makers.
Jan
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
14 matches
Mail list logo
