This inspired me to do some digging into the problem now that Rony has determined the cause. It appears that the <emphasis> tag confuses the stlyesheet which would have otherwise picked up the text. However, there are other ways to specify the text, one of which is to include an "xreflable" attribute. I have tried that and it allows one to keep the "emphasis" without generating the error messages. I plan to make the changes shortly so the original look will be preserved and the ??? will be eliminated. Any objections?

Gil

On 3/31/2020 4:48 PM, Gil Barmwater wrote:

Well done! I never would have thought to try that since the documentation would lead one to believe it was legal. Thanks Rony!

Gil

On 3/31/2020 2:52 PM, Rony G. Flatscher wrote:

Found the cause: there are term elements which have their text embedded in emphasis tags causing the error messages:

    Don't know what gentext to create for xref to: "emphasis"

Fixed them in "wineventlog.xml", ran doc2pdf.cmd and doc2html.cmd successfully, therefore committed with [r12032].

---rony


On 31.03.2020 17:41, Gil Barmwater wrote:

There appears to be two issues based on the messages generated by the transform step. The first - Warning: multiple "IDs" for constraint linkend: - occurs 7 times for 3 different values: clsWindowObject, childatpositionwo, and windowatpositionwm. These might be simple typos(?).

The second - Don't know what gentext to create for xref to: "emphasis" - occurs 32 times and seems to correspond with the ??? that appears 32 times in the PDF generated by Publican. Finding the XML for that area seems to show a "linkend=" but the value does not get substituted.

The second issue seems to be confined to the WindowsEventLogClass chapter.

That's as far as I have gotten. Hope it is enough to determine the fix needed.

Gil

On 3/31/2020 11:20 AM, Rick McGuire wrote:


On Tue, Mar 31, 2020 at 11:04 AM Gil Barmwater <gbarmwa...@alum.rpi.edu <mailto:gbarmwa...@alum.rpi.edu>> wrote:

    Well, as I mentioned, this was a problem with the PDF builds as
    well. So I looked in the PDF.xsl for where the "No
    adjustColumnWidths function available" message was generated
    and found that there was a parameter - tablecolumns.extension -
    that controlled that function. Since we don't use Perl and
    don't have the Perl function anyway, I decided to try disabling
    the function by changing the parameter expecting this would
    cause other side effects. Luckily, it didn't. So when this
    surfaced in the HTML generation, I found the same parameter in
    the xhtml-common.xsl file and changed it there too.

    The problems with winextensions are not not related but are due
    to "bad" Docbook code. I know where they are coming from but
    need to understand what the author was attempting to do and
    then determine how to do it "right".

Please explain what the issue it so we can help to decide now to fix it.

Rick

    Gil

    On 3/31/2020 10:26 AM, P.O. Jonsson wrote:
    Ok, missed that part :-(

    I have replaced xhtml-common.xsl now and winextensions build
    as it should, so this was probably the problem. This tiniest
    change cased the problem thus:

    <xsl:param n<xsl:param name="tablecolumns.extension">1</xsl:param>

    changed into

    <xsl:param name="tablecolumns.extension">0</xsl:param> <!--
    changed to 0 since we are not using Perl —>

    How on earth did you find THAT out? Hats off.

    Q: there is no change in pdf.xsl or htmp.xsl, right? If the
    same problem is causing the error messages I see when making a
    pdf of winextensions (32 of them), how do you gas about fixing
    that?

    Should I make another run in Verbose mode for PDF? It is
    REALLY verbose so hope your eyes are still ok ;-)

    I will rerun all HTMLs and come back in an hour and a half. It
    will be available here
    <https://www.dropbox.com/sh/2ea6si4tfgc5wml/AABV-i2_8PsoGaueEbpcNIVda?dl=0> 
when
    it is finished

    Hälsningar/Regards/Grüsse,
    P.O. Jonsson
    oor...@jonases.se <mailto:oor...@jonases.se>



    Am 31.03.2020 um 15:40 schrieb Gil Barmwater
    <gbarmwa...@alum.rpi.edu <mailto:gbarmwa...@alum.rpi.edu>>:

    I replaced it in the delta folder and the "package" zip file
    in my Dropbox. Here
    <https://www.dropbox.com/sh/2teduvgutl8wofb/AAAJ77lC5I6zURpa8UBb7Yu-a?dl=0>
    is a link to the delta folder.

    Gil

    On 3/31/2020 9:33 AM, P.O. Jonsson wrote:
    I saw that message as well but did not see that you had sent
    us a new stylesheet? Where do I get it?

    Hälsningar/Regards/Grüsse,
    P.O. Jonsson
    oor...@jonases.se <mailto:oor...@jonases.se>



    Am 31.03.2020 um 15:31 schrieb Gil Barmwater
    <gbarmwa...@alum.rpi.edu <mailto:gbarmwa...@alum.rpi.edu>>:

    OK, I've had a look at the log (whew!) and found what I was
    expecting - the same message Rony ran into about "No
    adjustColumnWidths function available". You must have
    missed the message I sent about it:

    "I also discovered the problem Rony found with the "No
    adjustColumnWidths function available" was also found in
    the PDF process. Luckily, the fix was as easy as changing a
    parameter in the stylesheet. The package and delta now have
    an updated xhtml-common.xsl file."

    So please replace the file xhtml-common.xsl with the
    corrected one in the delta (or the package). This should
    allow the DOC2HTML process to complete on all the books
    with missing parts. Thanks.

    Gil

    On 3/30/2020 7:37 PM, Gil Barmwater wrote:

    I'll take a look at the log in the morning, thanks!

    Gil

    On 3/30/2020 5:47 PM, P.O. Jonsson wrote:
    Dear Gil,

    I can still not build rexxextensions, it seems the
    process breaks somewhere halfway, index.html is always
    missing

    I have added the parameter --verbose to xslt and saved
    the output to a file, you can look at it in my dropbox.

    To be sure we are talking the same language here some
    info about my machine.

    Microsoft Windows 10 PRO 64 bit
    Version 1909
    OS build 1863.720
    Version 10.0.18363.720

    java version "1.8.0_241"
    Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
    Java HotSpot(TM) Client VM (build 25.241-b07, mixed mode)

    Please note that I have 64 bit and some of the tools are
    32 bit

    Please let me know what I can do further to iron this
    out. Before I have the same result as you can provide I
    will not move it to Jenkins

    I have not found a place where I can increase the Java Heap?

    Signing off for tonight.

    Hälsningar/Regards/Grüsse,
    P.O. Jonsson
    oor...@jonases.se <mailto:oor...@jonases.se>




_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater


_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

--
Gil Barmwater

_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to