Step-by-step explanation
Read the entire reference block before translating any one label.
Locate the document title, issuing office and the complete line, box or sentence containing tomo, libro, folio and adjacent labels such as página, foja, acta, partida, asiento, inscripción, serial or año. Decide first whether each item is a separate labeled coordinate, part of a sentence or an unrelated identifier elsewhere on the page. The same surface word can perform a different job in another issuer’s format. Translation begins with the displayed relationships, not a three-term equivalence table.
Original fictional example: “Registro Civil de Puerto Niebla / Tomo IV / Libro 12 / Folio 083 / Acta 0207” becomes “Puerto Niebla Civil Registry / Volume IV / Book 12 / Page Reference 083 / Record No. 0207” under the approved project glossary. The four fictional values remain separate; the translation does not create “Reference IV-12-083-0207.”
01
Identify the exact document, issuer and period.
Record the complete non-personal title, event type, country, registry office and visible registration or issue date before choosing terminology. A civil-registry certificate, request receipt, verification page and marginal annotation can each contain numbered labels, but they are different types of source material. Use country guidance for the issuer’s format instead of applying one jurisdiction’s terminology to every Spanish-language record.
Original fictional example: one page is headed “Certificación de Matrimonio,” while a separate payment receipt has “Folio de solicitud.” The certificate is inventoried as the source document and the receipt as an attachment; their numbered fields are not treated as one registry block.
02
Map every printed label to its own value.
Use spacing, ruling lines, punctuation, reading order and repeated headings to establish which value belongs to tomo, libro, folio and any entry number. Leave fields with no data blank rather than borrowing a nearby value. If a cropped edge or handwriting makes the pairing uncertain, request a complete image through the secure review path and mark the issue for review instead of guessing.
Original fictional example: a faded box reads “Tomo: B / Libro: 014 / Folio: [cropped].” The secure-upload review notes two legible fields and one cropped field; the quote does not reproduce the values in ordinary free text or move 014 into the folio position.
03
Keep tomo and libro distinct when the source prints both.
Tomo can often be rendered as “Volume,” and libro as “Book,” in a civil-registry reference block. Even though the words can overlap in general language, fields printed separately must remain separate and tied to their respective values. Do not omit one, reverse their values or claim a universal archive hierarchy; reproduce only the relationship visible in the supplied record.
Original fictional example: “Tomo C / Libro Segundo” becomes “Volume C / Book Two.” The alphabetic and written-number styles remain visible rather than being normalized to “Book 2, Volume 3.”
04
Resolve folio from its neighboring words and function.
Folio can support Folio, Page, Leaf or Page Reference when it points into a bound book or legacy register. Página or foja nearby may clarify the physical reference, while número de acta, asiento or serial may identify the entry itself. Choose one approved rendering that keeps those functions distinct. Retaining “Folio” can be clearer than forcing “Page” when the page relationship is not established.
Original fictional example: the sentence “inscrito al folio 67 vuelto del libro 9” is rendered “recorded on the reverse of folio 67 of Book 9.” A different standalone box labeled only “Folio: XG-884” remains “Folio: XG-884” pending issuer context.
05
Separate the locator from the entry and document identifiers.
A book or page coordinate can point to where an entry was recorded; número de acta, partida, asiento, serial, código or another field may identify the entry or issued document. Keep each printed label and its value separate. Do not rename every number as Certificate Number, Case Number or Registration Number, and do not use a receiving form’s single reference box to rewrite the source relationships.
Original fictional example: “Libro 21 / Folio 8 / Asiento 144 / Código de verificación ZR6K” remains four labeled values. The verification code is not appended to the archival coordinates and the entry number is not relabeled as Folio.
06
Preserve values, notation and visible order.
Copy Roman numerals, letters, prefixes, hyphens, slashes and leading zeros exactly enough for source comparison. Translate the label, not the identifier. The style guide may adapt the English layout for readability, but it must not calculate new coordinates, convert a Roman numeral silently or remove a zero that could be part of the displayed value.
Original fictional example: “Tomo IX-B / Libro 0007 / Folio 0042-R” remains “Volume IX-B / Book 0007 / Folio 0042-R.” It is not reformatted as “Volume 9B / Book 7 / Page 42.”
07
Run bilingual QA across every occurrence.
Compare the English translation against every page, content-bearing side, certification block and marginal note. Check that each label uses the approved context-specific term, every value remains paired correctly and each repeated reference matches its corresponding source occurrence, even when source occurrences differ from one another. Log uncertainty instead of silently harmonizing it, and keep the translator’s terminology decision separate from any conclusion about record status.
Original fictional example: page one says “Libro 11 / Folio 29,” but a later certification line visibly says “Libro 11 / Folio 92.” The translation preserves both displayed values and flags the difference for review; it does not decide which value is correct.