Whoa there Michael. This may be the key concept that I'm missing.
> You seem to say that you merely throw away lines from a clipping path. That
> is not enough: You also have to throw away lines from there on which happen
> to not reside inside the clipping path area; until the clipping path
> operation is revoked by a matching graphic state restore operation, that
> is...
Please let me test my understanding. Excuse me for using an example not based
on iText code. This excerpt was created with another product that dumps the
content stream into a nested structure that makes it easier for novices (me) to
read.
So with this partial stream, are you saying that everything from Graphics State
Save (line 2) to Graphics State Restore (line 20) is "invisible" aka clipped
because of the W n on lines 6 and 7? I was thinking the W and n only went with
the preceding rectangle.
1. LocalGraphicsState
2. { <-- This represents q
3. Path
4. {
5. {re [12.772, 1386.203, 573, 98.797]}
6. {W}
7. {n}
8. }
9. Text
10. {
11. {scn [0, 0, 0, 1]}
12. {Tf [T1_2, 1]}
13. {Tc [0.2]}
14. {Tm [11.0513, 0, 0, 11.0513, 214.9489, 1353.1497]}
15. {Tj [(1. FI)]}
16. {Tc [0.199]}
17. {Tw [-0.199]}
18. {Tj [(LL)]}
19. }
20. } <-- This represents Q
Thanks,
Darren
On Tuesday, October 21, 2014 10:45 AM, mkl <m...@wir-sind-cool.org> wrote:
Darren,
FDnC Red wrote
> I'm already filtering on operator W and W* to find clipping paths and
> excluding those paths. Are you saying there's an another way to determine
> clipping paths that I may not be filtering out?
You seem to say that you merely throw away lines from a clipping path. That
is not enough: You also have to throw away lines from there on which happen
to not reside inside the clipping path area; until the clipping path
operation is revoked by a matching graphic state restore operation, that
is...
> What I don't understand is how I could ever tell what's on top of what.
> Ideally there would be a Z-order to the paths but I see no such thing.
> Without such a mechanism I'm not sure how I would tell what is on top and
> what is not. Did I miss the z-order operator or some such thing?
What comes first is covered by what comes later. Until you play around with
transparency groups, that is, which make the rules slightly more
complicated.
Regards, Michael
--
View this message in context:
http://itext-general.2136553.n4.nabble.com/How-to-determine-what-is-visible-tp4660471p4660476.html
Sent from the iText - General mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
iText-questions mailing list
iText-questions@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/itext-questions
iText(R) is a registered trademark of 1T3XT BVBA.
Many questions posted to this list can (and will) be answered with a reference
to the iText book: http://www.itextpdf.com/book/
Please check the keywords list before you ask for examples:
http://itextpdf.com/themes/keywords.php
------------------------------------------------------------------------------
_______________________________________________
iText-questions mailing list
iText-questions@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/itext-questions
iText(R) is a registered trademark of 1T3XT BVBA.
Many questions posted to this list can (and will) be answered with a reference
to the iText book: http://www.itextpdf.com/book/
Please check the keywords list before you ask for examples:
http://itextpdf.com/themes/keywords.php
