Thank you for this solution.
What is the risk to use the second incrementalSave with COS in param ?
Le mar. 31 oct. 2023 à 19:38, Tilman Hausherr a
écrit :
> I got it to work with the classic method by adding this code before saving:
>
>
> COSDictionary parent =
> page.getCOSObject(
>
> It's mostly in PageDrawer.java search for things line width and clip.
I attempted to make some modifications to PageDrawer, but couldn't figure
out any changed that improved the behavior.
Also convert the PDF to uncompressed and try to change the page content
> stream so that only the lines
I don't know if there is any risk. Mostly that you forget to add enough
objects. But if you do, you'll notice if you look at the file and don't
see the changes.
Tilman
On 01.11.2023 10:34, Frédéric Ravetier wrote:
Thank you for this solution.
What is the risk to use the second incrementalSav
Hi,
I was able to reduce it further:
https://drive.google.com/file/d/1la-XYjKpDKar8sb9lUI1FTuxNutq682W/view?usp=sharing
The effect with PDFDebugger still happens. Nothing at 100%, line at 150%.
The content stream is now this:
1 0 0 1 7.812 413.676 cm
0 0 m
-0.354 -0.354 l
56.693 -0.354 l
56.693
4 matches
Mail list logo
