lsm/PdfPig
1
0
Fork 0
mirror of https://github.com/UglyToad/PdfPig.git synced 2025-11-24 08:47:01 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Clarify handling of optional content group names

Browse Source 
Updated comments to clarify handling of optional content group names in PDFs.
This commit is contained in:
Carlo Kok
2025-11-22 07:34:35 +01:00
committed by BobLd
parent 37a5dffcaa
commit ce563db133
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
src/UglyToad.PdfPig/Content/OptionalContentGroupElement.cs
View File

@@ -59,7 +59,10 @@ namespace UglyToad.PdfPig.Content
switch (Type)
{
case "OCG": // Optional content group dictionary
// Name - Required
// Name - Per spec this is required, but in practice some PDFs store layer names
// at the document catalog level in OCProperties rather than in marked content Properties.
// To avoid crashes, we make this optional and fall back to null or the tag name.
if (markedContentElement.Properties.TryGet(NameToken.Name, pdfTokenScanner, out NameToken? name))
{
Name = name.Data;
@@ -74,7 +77,9 @@ namespace UglyToad.PdfPig.Content
}
else
{
throw new ArgumentException($"Cannot parse optional content's {nameof(Name)} from {nameof(markedContentElement.Properties)}. This is a required field.", nameof(markedContentElement.Properties));
// Name not found in Properties - use tag as fallback or leave as null
// This handles PDFs where layer names are stored at document catalog level
Name = markedContentElement.Tag;
}
// Intent - Optional