HotPDF는 Delphi 및 C++Builder 애플리케이션을 위한 네이티브 VCL PDF 라이브러리입니다. 외부 PDF 런타임 배포 없이 PDF 생성, 편집, 양식, 주석, 암호화, 디지털 서명, Unicode 글꼴 처리, 표준 지향 출력, 프리플라이트 보고를 지원합니다.
이 글은 developers producing multilingual invoices, certificates, labels, or reports from Delphi을 위한 글입니다. Unicode text shaping for complex scripts을 단순한 컴포넌트 호출이 아니라 운영 환경의 문서 엔지니어링으로 다룹니다.
실제 위험은 text can appear plausible in a sample PDF while ligatures, bidirectional order, fallback fonts, or copy-and-search behavior fail for real customer names입니다. 따라서 명확한 계약, 관찰 가능한 진단, 실제 고객 파일을 반영한 회귀 샘플이 필요합니다.
아키텍처 결정
Make the text pipeline locale-aware. font fallback order for Arabic, Hebrew, Indic, CJK, and mixed Latin text / normalization rules for copied text, database values, and template placeholders
- font fallback order for Arabic, Hebrew, Indic, CJK, and mixed Latin text
- normalization rules for copied text, database values, and template placeholders
- right-to-left paragraph handling and mixed-direction number policy
- whether text must remain searchable, selectable, and accessible after output
구현 흐름
Resolve fonts and shaping before pagination. The order below keeps the workflow reviewable for Delphi and C++Builder teams.
- normalize source text and record the locale used for formatting
- select fonts that contain the required glyphs before measuring layout
- shape and position text before page breaks are finalized
- embed or subset fonts according to licensing and PDF standard requirements
- verify visual output and extracted text with multilingual regression samples
검증 증거
Proof that text is readable and extractable. Keep these fields with the output or support record.
- font selected for every script range and fallback reason when it changed
- glyph coverage warnings, embedding mode, and subset identifier
- extracted Unicode text compared with the original application value
- viewer screenshots for representative right-to-left and combining-mark cases
Visual output is not enough
Complex-script support involves character normalization, shaping, glyph positioning, embedding, ToUnicode maps, and reading order. A PDF that only looks right in one viewer can still fail search, selection, accessibility, or downstream extraction.
Regression files worth keeping
Keep more than successful samples. A useful Unicode text shaping for complex scripts regression set contains normal files, boundary files, and intentional failure files so the behavior is stable across releases.
- database collation can alter composed characters before the PDF layer sees them
- font substitution on a developer machine can hide missing embedded fonts
- line breaks in bidirectional text can reorder punctuation and numbers
- search may fail when ToUnicode data is missing even if the page renders correctly
- normalize source text and record the locale used for formatting
- select fonts that contain the required glyphs before measuring layout
Engineering review notes for Unicode text shaping for complex scripts
Use these review notes to make sure the feature has moved beyond a demo and can be defended during release, support, and customer escalation.
- Decision: font fallback order for Arabic, Hebrew, Indic, CJK, and mixed Latin text. Implementation pressure point: select fonts that contain the required glyphs before measuring layout. Acceptance evidence: extracted Unicode text compared with the original application value. Regression trigger: search may fail when ToUnicode data is missing even if the page renders correctly
- Decision: normalization rules for copied text, database values, and template placeholders. Implementation pressure point: shape and position text before page breaks are finalized. Acceptance evidence: viewer screenshots for representative right-to-left and combining-mark cases. Regression trigger: database collation can alter composed characters before the PDF layer sees them
- Decision: right-to-left paragraph handling and mixed-direction number policy. Implementation pressure point: embed or subset fonts according to licensing and PDF standard requirements. Acceptance evidence: font selected for every script range and fallback reason when it changed. Regression trigger: font substitution on a developer machine can hide missing embedded fonts
- Decision: whether text must remain searchable, selectable, and accessible after output. Implementation pressure point: verify visual output and extracted text with multilingual regression samples. Acceptance evidence: glyph coverage warnings, embedding mode, and subset identifier. Regression trigger: line breaks in bidirectional text can reorder punctuation and numbers
경계 사례
- database collation can alter composed characters before the PDF layer sees them
- font substitution on a developer machine can hide missing embedded fonts
- line breaks in bidirectional text can reorder punctuation and numbers
- search may fail when ToUnicode data is missing even if the page renders correctly
Delphi / C++Builder notes
HotPDF Component should sit behind a small service boundary that receives files, streams, profiles, and credentials, then returns output paths, warnings, metrics, and validation status. Important terms include Unicode, text shaping, font embedding, ToUnicode, bidirectional text, fallback font.
Delphi 코드 예제
다음 Delphi 스케치는 이 주제에 맞는 실무형 서비스 경계를 보여 줍니다. 정책 검사, 로깅, 검증을 좁은 제품 호출 구간 밖에 두면 워크플로를 테스트하기 쉽습니다.
procedure DrawShapedRun(Pdf: THotPDF; const Text: UnicodeString; const Script: TScriptProfile);
begin
Pdf.CurrentPage.SetFont(Script.FontName, [], Script.Size, 0, Script.Vertical);
if Script.RequiresReorder then
Pdf.CurrentPage.TextOut(Script.X, Script.Y, 0, ShapeUnicodeRun(Text, Script))
else
Pdf.CurrentPage.TextOut(Script.X, Script.Y, 0, Text);
RecordGlyphCoverage(Script.FontName, Text);
end;운영 체크리스트
- Run the workflow on an empty file, a normal customer file, and a worst-case file
- Open the generated PDF with the target viewer, validator, printer, or downstream application
- Log product version, profile version, input hash, output path, elapsed time, and warning count
- Keep passwords, certificates, temporary files, and customer data under explicit retention rules
- Add regression documents when a customer file exposes a new edge case