Anonymous_User Absent Member.
Absent Member.
340 views

Re: Error when building documentation


Hi Balasz,

Well, let's go through the basics first.

- Do you have OpenOffice installed?
- Do you have the OpenOffice macro installed?
- Can you open all three documents (the one in your plug-in's "doc"
directory, plus the 2 in //content/dev/sdk/<type>/static/doc) without
errors?

If the above is all OK, then you should try running the macro manually.
First run through a complete build process, and then run the following
command from a command prompt (I'll pretend you have a Collector named
MyVendor, MyProdut, but the principle is the same for all plugins):
soffice -invisible
'macro:///Standard.Collectors.External2PDF(/path/content/build/MyVendor_MyProduct_6.1r1/tmp/external.odt)'
The result should be an external.pdf file. If not, you have a problem
with your macro or a corrupted document, but should get an error message
to assist you.


--
DCorlette
------------------------------------------------------------------------
DCorlette's Profile: http://forums.novell.com/member.php?userid=4437
View this thread: http://forums.novell.com/showthread.php?t=416875

0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Error when building documentation


Hi,

- Do you have OpenOffice installed? YES
- Do you have the OpenOffice macro installed? YES
- Can you open all three documents (the one in your plug-in's "doc"
directory, plus the 2 in //content/dev/sdk/<type>/static/doc) without
errors?:

I have the external.odt file, I can open the
"c:\proj\content\build\cattest1_test1_6.1r1\plugin\docs\plugin.pdf".

I tried to open the file under
c:\proj\content\build\cattest1_test1_6.1r1\tmp\external.odt
The following error occured:
"Format error discovered in the file in sub-document styles.xml at
2,36465(row,col)"

I could open the external.odt and plugin.odt under
"c:\proj\content\dev\sdk\6.1\Report\static\docs\"

When I try to build release with eclipse, it says:
BASIC runtime error. Objective variable not set.
And stops at this line in the macro: oIndexes =
oDoc.getDocumentIndexes()

Balazs

DCorlette;2020979 Wrote:
> Hi Balasz,
>
> Well, let's go through the basics first.
>
> - Do you have OpenOffice installed?
> - Do you have the OpenOffice macro installed?
> - Can you open all three documents (the one in your plug-in's "doc"
> directory, plus the 2 in //content/dev/sdk/<type>/static/doc) without
> errors?
>
> If the above is all OK, then you should try running the macro manually.
> First run through a complete build process, and then run the following
> command from a command prompt (I'll pretend you have a Collector named
> MyVendor, MyProdut, but the principle is the same for all plugins):
> soffice -invisible
> 'macro:///Standard.Collectors.External2PDF(/path/content/build/MyVendor_MyProduct_6.1r1/tmp/external.odt)'
> The result should be an external.pdf file. If not, you have a problem
> with your macro or a corrupted document, but should get an error message
> to assist you.



--
lenbal
------------------------------------------------------------------------
lenbal's Profile: http://forums.novell.com/member.php?userid=55986
View this thread: http://forums.novell.com/showthread.php?t=416875

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Error when building documentation


We discovered that this appears to be do to character encodings; on some
systems, and for some reason fairly recently, it now appears that we
need to explicitly declare the encoding of the files in the documents to
be UTF-8. The latest SDK code should take care of this for you.


--
DCorlette
------------------------------------------------------------------------
DCorlette's Profile: http://forums.novell.com/member.php?userid=4437
View this thread: http://forums.novell.com/showthread.php?t=416875

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Error when building documentation


Hi,

unfortunatelly this won't help me, because I am using the current 6.1r5
version of the plugin sdk. Any other solution?
I've installed from every component an english version, like Windows
2003 En, Openoffice EN...only my regional settings are set to Hungarian
in windows like keyboard, money...


--
lenbal
------------------------------------------------------------------------
lenbal's Profile: http://forums.novell.com/member.php?userid=55986
View this thread: http://forums.novell.com/showthread.php?t=416875

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Error when building documentation


Hi there,

Well, the best approach would be to update your SDK. But if necessary,
you can go through the //content/dev/sdk/build/build-core.xml file, and
in the "_build-plugdoc" and "_build-externaldoc" targets, add the
encoding declaration.

E.g.:
<move file="${pkgdir}/tmp/external/styles.tmp"
tofile="${pkgdir}/tmp/external/styles.xml" *encoding="utf-8"*>
<filterset refid="buildFilter"/>
<filterset refid="typeFilter"/>
</move>
<move file="${pkgdir}/tmp/release/content.tmp"
tofile="${pkgdir}/tmp/release/content.xml" *encoding="utf-8"*>
<filterset refid="buildFilter"/>
<filterset refid="typeFilter"/>
</move>


--
DCorlette
------------------------------------------------------------------------
DCorlette's Profile: http://forums.novell.com/member.php?userid=4437
View this thread: http://forums.novell.com/showthread.php?t=416875

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.