You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Rick Hillegas <Ri...@Sun.COM> on 2006/09/22 20:05:05 UTC
errors building the JDBC4 disclaimer in the 10.2 docs
When I build the 10.2 docs, I see errors like the following when
processing the jdbc4disclaimer. Nevertheless, the documents seem to
build and the disclaimer is inserted. Is this expected behavior?
Thanks,
-Rick
rick_sun docs (1.4) > builddocs html adminguide
[echo]
*****************************************************************
[echo] * input =
C:\cygwin\home\rh161140\derby\docs\10.2\src\adminguide\derbyadmin.ditamap
[echo] * type = ${transtype}
[echo] * outputdir =
C:\cygwin\home\rh161140\derby\docs\10.2\out\adminguidetemp
[echo] * extname = .dita
[echo] * tempdir = C:\cygwin\home\rh161140\derby\docs\10.2/temp
[echo] * clean.temp = ${clean.temp}
[echo]
*****************************************************************
[pipeline] [Error] :56:13: The content of element type "ph" must match
"(ph|codeph|synph|filepath|msgph|userinput|syste
moutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|apiname|cmdname|ms
gnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
[echo] debug
[pipeline] [Error] adminconrefs.dita:56:13: The content of element type
"ph" must match "(ph|codeph|synph|filepath|msgp
h|userinput|systemoutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|a
piname|cmdname|msgnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
[echo] in conref
BUILD SUCCESSFUL
Re: still going to do doc mega-merge? (was Re: errors building the
JDBC4 disclaimer in the 10.2 docs)
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Rick Hillegas wrote:
> Hi Jean,
>
> Yes, I'm still going to mega-merge the docs. I just started this and
> then ran into the disclaimer problem when I did a sanity build.
excellent of you to notice! --and to also do the sanity build. My first
thought was you were building the docs to include in the release.
everyone is champing at the bit .... enthusiasm is nice ... but I'll
shut up and let you carry on.
thanks for all the hard work!
-jean
> Regards,
> -Rick
>
> Jean T. Anderson wrote:
>
>> Rick Hillegas wrote:
>>
>>
>>> When I build the 10.2 docs,
>>
>>
>> following up on building the 10.2 docs comment. Are you still planning
>> to mega merge the doc commits since last week?
>>
>> if you'd like help, just let me know.
>>
>> thanks,
>>
>> -jean
>>
>>
>>
>>> I see errors like the following when
>>> processing the jdbc4disclaimer. Nevertheless, the documents seem to
>>> build and the disclaimer is inserted. Is this expected behavior?
>>>
>>> Thanks,
>>> -Rick
>>>
>>> rick_sun docs (1.4) > builddocs html adminguide
>>> [echo]
>>> *****************************************************************
>>> [echo] * input =
>>> C:\cygwin\home\rh161140\derby\docs\10.2\src\adminguide\derbyadmin.ditamap
>>>
>>> [echo] * type = ${transtype}
>>> [echo] * outputdir =
>>> C:\cygwin\home\rh161140\derby\docs\10.2\out\adminguidetemp
>>> [echo] * extname = .dita
>>> [echo] * tempdir = C:\cygwin\home\rh161140\derby\docs\10.2/temp
>>> [echo] * clean.temp = ${clean.temp}
>>> [echo]
>>> *****************************************************************
>>> [pipeline] [Error] :56:13: The content of element type "ph" must match
>>> "(ph|codeph|synph|filepath|msgph|userinput|syste
>>> moutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|apiname|cmdname|ms
>>>
>>>
>>> gnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
>>>
>>>
>>> [echo] debug
>>> [pipeline] [Error] adminconrefs.dita:56:13: The content of element type
>>> "ph" must match "(ph|codeph|synph|filepath|msgp
>>> h|userinput|systemoutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|a
>>>
>>>
>>> piname|cmdname|msgnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
>>>
>>>
>>> [echo] in conref
>>>
>>> BUILD SUCCESSFUL
>>>
>>
>>
>>
>>
>
Re: still going to do doc mega-merge? (was Re: errors building the
JDBC4 disclaimer in the 10.2 docs)
Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi Jean,
Yes, I'm still going to mega-merge the docs. I just started this and
then ran into the disclaimer problem when I did a sanity build.
Regards,
-Rick
Jean T. Anderson wrote:
>Rick Hillegas wrote:
>
>
>>When I build the 10.2 docs,
>>
>>
>
>following up on building the 10.2 docs comment. Are you still planning
>to mega merge the doc commits since last week?
>
>if you'd like help, just let me know.
>
>thanks,
>
>-jean
>
>
>
>>I see errors like the following when
>>processing the jdbc4disclaimer. Nevertheless, the documents seem to
>>build and the disclaimer is inserted. Is this expected behavior?
>>
>>Thanks,
>>-Rick
>>
>>rick_sun docs (1.4) > builddocs html adminguide
>> [echo]
>>*****************************************************************
>> [echo] * input =
>>C:\cygwin\home\rh161140\derby\docs\10.2\src\adminguide\derbyadmin.ditamap
>> [echo] * type = ${transtype}
>> [echo] * outputdir =
>>C:\cygwin\home\rh161140\derby\docs\10.2\out\adminguidetemp
>> [echo] * extname = .dita
>> [echo] * tempdir = C:\cygwin\home\rh161140\derby\docs\10.2/temp
>> [echo] * clean.temp = ${clean.temp}
>> [echo]
>>*****************************************************************
>>[pipeline] [Error] :56:13: The content of element type "ph" must match
>>"(ph|codeph|synph|filepath|msgph|userinput|syste
>>moutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|apiname|cmdname|ms
>>
>>gnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
>>
>> [echo] debug
>>[pipeline] [Error] adminconrefs.dita:56:13: The content of element type
>>"ph" must match "(ph|codeph|synph|filepath|msgp
>>h|userinput|systemoutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|a
>>
>>piname|cmdname|msgnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
>>
>> [echo] in conref
>>
>>BUILD SUCCESSFUL
>>
>>
>
>
>
still going to do doc mega-merge? (was Re: errors building the JDBC4
disclaimer in the 10.2 docs)
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Rick Hillegas wrote:
> When I build the 10.2 docs,
following up on building the 10.2 docs comment. Are you still planning
to mega merge the doc commits since last week?
if you'd like help, just let me know.
thanks,
-jean
> I see errors like the following when
> processing the jdbc4disclaimer. Nevertheless, the documents seem to
> build and the disclaimer is inserted. Is this expected behavior?
>
> Thanks,
> -Rick
>
> rick_sun docs (1.4) > builddocs html adminguide
> [echo]
> *****************************************************************
> [echo] * input =
> C:\cygwin\home\rh161140\derby\docs\10.2\src\adminguide\derbyadmin.ditamap
> [echo] * type = ${transtype}
> [echo] * outputdir =
> C:\cygwin\home\rh161140\derby\docs\10.2\out\adminguidetemp
> [echo] * extname = .dita
> [echo] * tempdir = C:\cygwin\home\rh161140\derby\docs\10.2/temp
> [echo] * clean.temp = ${clean.temp}
> [echo]
> *****************************************************************
> [pipeline] [Error] :56:13: The content of element type "ph" must match
> "(ph|codeph|synph|filepath|msgph|userinput|syste
> moutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|apiname|cmdname|ms
>
> gnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
>
> [echo] debug
> [pipeline] [Error] adminconrefs.dita:56:13: The content of element type
> "ph" must match "(ph|codeph|synph|filepath|msgp
> h|userinput|systemoutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|a
>
> piname|cmdname|msgnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
>
> [echo] in conref
>
> BUILD SUCCESSFUL
Re: errors building the JDBC4 disclaimer in the 10.2 docs
Posted by Rick Hillegas <Ri...@Sun.COM>.
Thanks, Jean. This is fine and I'll just chill.
-Rick
Jean T. Anderson wrote:
>Rick Hillegas wrote:
>
>
>>When I build the 10.2 docs, I see errors like the following when
>>processing the jdbc4disclaimer. Nevertheless, the documents seem to
>>build and the disclaimer is inserted. Is this expected behavior?
>>
>>
>
>yes, I mentioned this in
>http://issues.apache.org/jira/browse/DERBY-1271#action_12435148 :
>
>
>
>>Incidently, DITA processing complains about the <note> element in the variable, but it does get processed correctly.
>>
>>
>
>So it's "legal" to include a <ph> element within the <ph>, but not legal
> to include <note>. But it worked, so I left it. I can remove that if
>you prefer, but it won't get the note formatting in the pdf and html books.
>
> -jean
>
>
>
>
>>Thanks,
>>-Rick
>>
>>rick_sun docs (1.4) > builddocs html adminguide
>> [echo]
>>*****************************************************************
>> [echo] * input =
>>C:\cygwin\home\rh161140\derby\docs\10.2\src\adminguide\derbyadmin.ditamap
>> [echo] * type = ${transtype}
>> [echo] * outputdir =
>>C:\cygwin\home\rh161140\derby\docs\10.2\out\adminguidetemp
>> [echo] * extname = .dita
>> [echo] * tempdir = C:\cygwin\home\rh161140\derby\docs\10.2/temp
>> [echo] * clean.temp = ${clean.temp}
>> [echo]
>>*****************************************************************
>>[pipeline] [Error] :56:13: The content of element type "ph" must match
>>"(ph|codeph|synph|filepath|msgph|userinput|syste
>>moutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|apiname|cmdname|ms
>>
>>gnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
>>
>> [echo] debug
>>[pipeline] [Error] adminconrefs.dita:56:13: The content of element type
>>"ph" must match "(ph|codeph|synph|filepath|msgp
>>h|userinput|systemoutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|a
>>
>>piname|cmdname|msgnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
>>
>> [echo] in conref
>>
>>BUILD SUCCESSFUL
>>
>>
>
>
>
Re: errors building the JDBC4 disclaimer in the 10.2 docs
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Rick Hillegas wrote:
> When I build the 10.2 docs, I see errors like the following when
> processing the jdbc4disclaimer. Nevertheless, the documents seem to
> build and the disclaimer is inserted. Is this expected behavior?
yes, I mentioned this in
http://issues.apache.org/jira/browse/DERBY-1271#action_12435148 :
> Incidently, DITA processing complains about the <note> element in the variable, but it does get processed correctly.
So it's "legal" to include a <ph> element within the <ph>, but not legal
to include <note>. But it worked, so I left it. I can remove that if
you prefer, but it won't get the note formatting in the pdf and html books.
-jean
> Thanks,
> -Rick
>
> rick_sun docs (1.4) > builddocs html adminguide
> [echo]
> *****************************************************************
> [echo] * input =
> C:\cygwin\home\rh161140\derby\docs\10.2\src\adminguide\derbyadmin.ditamap
> [echo] * type = ${transtype}
> [echo] * outputdir =
> C:\cygwin\home\rh161140\derby\docs\10.2\out\adminguidetemp
> [echo] * extname = .dita
> [echo] * tempdir = C:\cygwin\home\rh161140\derby\docs\10.2/temp
> [echo] * clean.temp = ${clean.temp}
> [echo]
> *****************************************************************
> [pipeline] [Error] :56:13: The content of element type "ph" must match
> "(ph|codeph|synph|filepath|msgph|userinput|syste
> moutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|apiname|cmdname|ms
>
> gnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
>
> [echo] debug
> [pipeline] [Error] adminconrefs.dita:56:13: The content of element type
> "ph" must match "(ph|codeph|synph|filepath|msgp
> h|userinput|systemoutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|xref|cite|q|boolean|state|keyword|option|parmname|a
>
> piname|cmdname|msgnum|varname|wintitle|tm|image|draft-comment|required-cleanup|fn|indextermref|indexterm)".
>
> [echo] in conref
>
> BUILD SUCCESSFUL