bugGNU TeXmacs - Bugs: bug #62007, images embedded in help articles...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #62007: images embedded in help articles provoke errors

Submitter:  Philippe Joyez <pjoyez>
Submitted:  Tue 08 Feb 2022 08:51:50 AM UTC
 
Category:  Help System Priority:  5 - Normal
Item Group:  Error Status:  Confirmed
Privacy:  Public Assigned to:  None
Originator Name:  Open/Closed:  Open
Release:  None Release: 
Fixed Release:  None Fixed Release: 
Keywords: 

Sat 12 Feb 2022 11:16:06 AM UTC, comment #1: 

The problem is not related to tmdoc-expand per se, you can trigger it by exporting files with embedded images to stm; Then, when reloading the stm file, the error is thrown.

And, AFAICT, it is the xOD bytes (ASCII CR) that get dropped in the image data (at least, there are maybe other).

Philippe Joyez <pjoyez>
Project Member
Tue 08 Feb 2022 08:51:50 AM UTC, original submission:  

This issue is mentionned in https://savannah.gnu.org/patch/?10164
and I confirm it.

When expanding help articles, if branches contain embedded images TeXmacs tools throw error messages saying they cannot determine the image size and, of course, images cannot be displayed correctly. In this process, the embedded images get extracted to a temporary directory, and one can observe that the images are corrupted at that point (at least png and pdf). For instance pdf files miss a few bytes here and there...

It seems the problem occurs while performing the branch inclusion in tmdoc-expand, when the included tree contains arbitrary binary image data.

Philippe Joyez <pjoyez>
Project Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by pjoyez (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

     

     

    No changes have been made to this item

    Back to the top


    Powered by Savane 3.9