Hello,

Yes, I think at some point there is some unfortunate character (0xffff) in your 
upload being extracted for reporting, cf:

https://stackoverflow.com/questions/20735405/is-0xffff-a-valid-unicode-character

One way of tracking this down is to open the file in question and go to the 
second line at the 65535th position to understand in which context your faulty 
character is placed.

Same could be done with the RDF file  [line: 13438727, col: 264]. (Btw, It 
seems like you have generated an SPDX file with 13 mio lines?)

From, there you could find out maybe what kind of content is preventing your 
from opening the report with libre office. 

In case you do not quite get what I mean, you could also send the file to me 
and I could have a look for you.

Kind regards,
  Michael



> On 11. May 2021, at 09:34, huangt...@hotmail.com wrote:
> 
> Hello,
> 
>     I am now analyzing one software project using the Fossology tool built 
> from Version: [3.10.0.4], Branch: [master], Commit: [#d2c707].
> 
>     When uploading a tar file composed of less than 500 files, the job works 
> smoothly. I can export the Unified Report in .docx format and view it by the 
> LibreOffice tool.
> Then, I upload a tar files composed of 10,000 files to be analyzed. Although 
> it takes longer to complete the job, all of the items are scanned 
> successfully (with green bar).
> However, I get the following error message when I try to open the exported 
> unified report with the LibreOffice tool.
> 
>     "SAXException: [word/document.xml line 2]: PCDATA invalid Char value 
> 65535"
> 
>     It seems that the unified report contains some unrecognized characters. I 
> am wondering whether this error is caused by the report generating tool in 
> Fossology? Or I need to
> configure any parameters to generate the report correctly?
> 
>     I had also used the SPDX tool to convert the exported .rdf file to html 
> file. Unfortunately, I still got the similar error.
> 
> Exception in thread "main" org.apache.jena.riot.RiotException: [line: 
> 13438727, col: 264] An invalid XML character (Unicode: 0xffff) was found in 
> the CDATA section.
> 
>     Does anyone know how to fix this issue?
> 
>     Thanks.
> 
>          Todd
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#3450): https://lists.fossology.org/g/fossology/message/3450
Mute This Topic: https://lists.fossology.org/mt/82741191/21656
Group Owner: fossology+ow...@lists.fossology.org
Unsubscribe: https://lists.fossology.org/g/fossology/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to