To use this utility it will require modification of our own Perl modules found
on the FOP SVN site. Whether that requires just a change to the patterns
(path.pm file) or the more complicated requirement of writing our own pattern
subroutine (in the view.pm) I am not yet sure. Unfortunately thoug
I prefer python but bash is fine. OTOH, anything written by Larry Wall
should be avoided like the plague.
On Tue, Jul 15, 2014 at 8:53 AM, Clay Leeds
wrote:
> On Jul 15, 2014, at 7:46 AM, Glenn Adams wrote:
> > I suppose it depends on whether or not we need to hack perl to use the
> facility.
On Jul 15, 2014, at 7:46 AM, Glenn Adams wrote:
> I suppose it depends on whether or not we need to hack perl to use the
> facility. If there is any alternative that doesn't use perl, then that would
> be preferable.
>
> Frankly, I've never been happy with the new MD based documentation, though
I suppose it depends on whether or not we need to hack perl to use the
facility. If there is any alternative that doesn't use perl, then that
would be preferable.
Frankly, I've never been happy with the new MD based documentation, though
Clay has spent an inordinate amount of time tweaking it.
O
Considering ASF-CMS is written in Perl, I wouldn't discount Perl out-of-hand.
However, IMFO (sorry! Typo, but I could t bring myself to change it! ;-) I
would think a solution blessed by infra@ would be acceptable, especially if
they'll bless and/or maintain it!
Cheers!
Clay
--
"My religion i
I will -1 any proposal that involves using Perl.
On Tue, Jul 15, 2014 at 3:35 AM, Robert Meyer wrote:
> Hi All,
>
> This is an update into my investigations on automating the release process
> for FOP. As we're nearing release it looks as though version 2.0 will
> remain a manual process for th
[
https://issues.apache.org/jira/browse/FOP-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Reischenbacher updated FOP-2280:
-
Summary: [PATCH] Retrieved marker content ignores writing-mode (was:
Retrieved mar
[
https://issues.apache.org/jira/browse/FOP-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Reischenbacher updated FOP-2280:
-
Attachment: 2280_hebrew_marker.patch
> Retrieved marker content ignores writing-mod
[
https://issues.apache.org/jira/browse/FOP-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Hennebert updated FOP-2394:
---
Attachment: remove-non-standard-layout-extensions.patch
> [PATCH] Remove non-standard layout ex
Vincent Hennebert created FOP-2394:
--
Summary: [PATCH] Remove non-standard layout extensions
Key: FOP-2394
URL: https://issues.apache.org/jira/browse/FOP-2394
Project: Fop
Issue Type: Improve
Hi All,
This is an update into my investigations on automating the release process for
FOP. As we're nearing release it looks as though version 2.0 will remain a
manual process for the time being. That's not to say that it will forever
remain like that but at present unless a breakthrough occur
11 matches
Mail list logo
