Hi David,
Why do you have publican/oorexx/publish/oorexx checked into subversion
and have the Makefile remove it?
all: brand
brand:
- rm -r publish/oorexx
publican build --formats xml --langs all --publish
install:
sudo publican install_brand --path /usr/share/publican/
David Ashley wrote:
> I am not 100% sure, but I believe it has to do with elements that will not
> completely fit on a page. For instance, an ordered list or a paragraph. I
> think it is warning that it had to break the element and continue it to
> the next page.
If all the error messages have v
Rick McGuire wrote:
> a 32-bit one would work just fine on Win64.
Thank you both for the feedback. I saw your posts from on-site at the client,
and then whipped up a debug script to run on that x64 system, compare outputs,
and see if I can narrow in on the source of
why the Reg.exe piped into g
Okay, thanks David. That makes sense.
--
Mark Miesfeld
On Thu, Aug 30, 2012 at 2:35 PM, David Ashley wrote:
> I am not 100% sure, but I believe it has to do with elements that will
> not completely fit on a page. For instance, an ordered list or a
> paragraph. I think it is warning that it had
I am not 100% sure, but I believe it has to do with elements that will
not completely fit on a page. For instance, an ordered list or a
paragraph. I think it is warning that it had to break the element and
continue it to the next page.
Just a guess on my part. But they do seem to be harmless warni
Oh, I should have asked you this.
Do you see these types of warning messages?
Aug 30, 2012 11:51:59 AM org.apache.fop.events.LoggingEventListener processEvent
WARNING: Content overflows the viewport of the fo:region-after on page
1532 in block-progression direction by 77 millipoints. (See positio
On Thu, Aug 30, 2012 at 1:09 PM, David Ashley wrote:
> Actually, since you will be the one who mostly maintains the oodialog
> document I guess I do not really care which system you use. Just be
> aware that you will probably have to pipe you output to a file because
> the number of warning gener
Actually, since you will be the one who mostly maintains the oodialog
document I guess I do not really care which system you use. Just be
aware that you will probably have to pipe you output to a file because
the number of warning generated by publican will be far larger than the
buffer your comman
On Thu, Aug 30, 2012 at 9:53 AM, David Ashley wrote:
> Let me know if you see any problems.
I have a problem with the way links are displayed. Take these two
lines under Publican
maximized, it is not restored. In addition, it is not given the focus.
This is exactly equivalent to
the showFast (
Here is the current status for the conversion. All the docs are now
converted with the following 2 exceptions.
oodialog - Mark is finishing up this one.
buildmachine - This doc e is wwaayyy out of date. So I will have to
not only convert it but it will need a major update of the content. I
wi
On Thu, Aug 30, 2012 at 6:19 AM, David Ashley wrote:
> I ran into that problem already on some other docs. The indexterm tag is
> not allowed as a sub tag of varlistentry. You have to move the indexterm
> and associated tags into the para tag used in the varlistentry.
Thanks David. Rick's help
I ran into that problem already on some other docs. The indexterm tag is
not allowed as a sub tag of varlistentry. You have to move the indexterm
and associated tags into the para tag used in the varlistentry.
Remember that index items refer to a position in the text so indexterm
is only allowed i
Michael, Rick's right.
The 32 bit grep works just fine. I use the GnuWin32 tools on all my
64-bit Windows systems. And, I use grep a lot.
--
Mark Miesfeld
On Thu, Aug 30, 2012 at 4:11 AM, Michael Lueck
wrote:
> Greetings,
>
> Does the ooRexx for Windows build process happen to require grep? I
On Thu, Aug 30, 2012 at 3:52 AM, Rick McGuire wrote:
> Just took at look at this with XML Mind, and the only errors it highlights
> is a problem with the index entries associated with THICKFRAME (line 640).
> However, there appear to be a lot of mal-formed xref tags in these files.
> They are cod
No, we don't use grep. And even if we did, a 32-bit one would work just
fine on Win64.
Rick
On Thu, Aug 30, 2012 at 7:11 AM, Michael Lueck
wrote:
> Greetings,
>
> Does the ooRexx for Windows build process happen to require grep? If so,
> where was one for Win64 found?
>
> I make use of GnuWin32
Greetings,
Does the ooRexx for Windows build process happen to require grep? If so, where
was one for Win64 found?
I make use of GnuWin32 tools, use grep from that project, and have need of
finding the same for Win64.
Sincerely,
--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems
Mark,
Just took at look at this with XML Mind, and the only errors it highlights
is a problem with the index entries associated with THICKFRAME (line 640).
However, there appear to be a lot of mal-formed xref tags in these files.
They are coded as
(xref linkend="chpDialogObject" />)
but should
17 matches
Mail list logo
