Sheet 04 · Catalog twins · per-project delivery
Your catalog, in the other language Page for page
Send the catalog PDF you already print from. What comes back is the same document in the other language, KR to EN or EN to KR: the same page count, the same page geometry, the drawings, tables and charts exactly as drawn, with the text replaced in place. Nothing is re-laid out and nothing is re-drawn, so the second language stops falling behind the first.
Twins of two TPC catalogs
Per-project delivery
Translators change the words
and the page changes with them
A technical catalog is a drawing set with sentences in it. Hand it to a translator and the terms drift toward everyday language, a translated table no longer fits its cell, a chart’s labels are re-typed by hand, and someone ends up re-laying out or re-drawing pages that were finished years ago. Every revision then has to be done twice, so the second language falls behind the first and stays there.
Same pages
Other language
bringPDF treats the catalog as a document to preserve, not a text to re-set. The words are replaced inside the page’s own text objects; the vector drawings, the table rules, the charts and the fonts stay where they were. The result is a twin: open the two PDFs side by side and every page lines up with its counterpart.
The twin stays a vector PDF: the text is replaced in place and nothing is rasterized, so it prints at the original resolution and zooms without blur.
| Translation as usual | bringPDF |
|---|---|
| Text re-set in a new document | Text replaced in place, in the original file’s own objects |
| Tables and charts rebuilt by hand | Tables, charts and drawings untouched |
| Page count and pagination drift | Same page count, same page geometry, checked on every page |
| Terminology from a general dictionary | A draft from models trained on CAD and manufacturing documents |
| Quality judged by reading | Parity checks on page count and geometry gate every delivery |
Measured, not asserted
Every page pair, compared
Both versions of each catalog were rendered at 2x. The text regions of both versions were masked out, and everything that remained, logos, table rules, charts, drawings, was compared pixel for pixel. This table is what licenses the words on this page.
| Catalog | Page | Page size, pt, both versions | Text masked | Pixels differing outside text | Verdict |
|---|---|---|---|---|---|
| THR | 1 | 595.3 × 841.9 | 20.1 % | 0.097 % | match |
| THR | 2 | 595.3 × 841.9 | 22.7 % | 0.002 % | match |
| THR | 3 | 595.3 × 841.9 | 3.7 % | 0.132 % | match |
| THR | 4 | 595.3 × 841.9 | 3.5 % | 0.133 % | match |
| TLR | 1 | 595.0 × 843.7 | 14.2 % | 0.013 % | match |
| TLR | 2 | 595.0 × 843.7 | 1.5 % | 0.000 % | match |
| TLR | 3 | 595.0 × 843.7 | 1.7 % | 0.001 % | match |
| TLR | 4 | 595.0 × 843.7 | 1.5 % | 0.000 % | match |
Numbers from the diff table above, not projections
Replacement, not re-setting
A general translator produces text. bringPDF produces the same document again, in the other language, and checks that it is the same document before it leaves.
Language, trained on the domain
The draft comes from a language model trained on CAD and manufacturing documents, not from a general-purpose translator. It works from the page, so a term is seen next to the drawing and the table it belongs to.
Text replaced in place
The new text goes back into the page’s own text objects. Vector drawings, table rules, charts and fonts are never touched, which is why the non-text pixels in the table above match.
Parity, checked
Page count and page geometry are compared on every page before a twin is delivered. A twin with a different page count or a moved page does not ship.
Review at the gate
An engineer reads the twin against the source before delivery, on the pages where a wrong term would cost you something.
- KR to EN and EN to KR, from the PDF you print from.
- Your catalog PDFs never leave the project.
One catalog at a time
Ordered per project
bringPDF is delivered per project, not on a subscription. Send the PDF, name the target language, and a twin comes back with its page-pair comparison attached. Terms are agreed per catalog.
Send the source PDFThe catalog as you print it, in Korean or English, any page count.
1 × PDFReceive the twinThe same document in the other language: same page count, same geometry, drawings and tables untouched.
1 × PDFReceive the proofThe per-page comparison for your catalog, in the form shown above, so your team can see what was checked.
diff tableReview at your paceYour engineers read the twin against the source. Their sign-off is the acceptance bar.
your sign-offLet's talk
We skip the pitch decks. Bring one catalog and leave with the page count, the language pair, and a date.
First call → twin delivered: one catalog at a time
Your catalog PDFs never leave the project. The twin is checked page by page against them before it ships.
Built for manufacturers whose catalogs are drawings with sentences in them.
Every twin checked page by page against your source before it ships.
Founder & CEO · ex-robotics CEO
20 yrs Korea & US market experience