How to Set Up Simultaneous English Publishing
Simultaneous English publishing is a publishing architecture problem, not a translation one. Confusing the two inflates both cost and delay. Translation produces the text; the real question is whether that text can be published at the right moment, through the right channel, correctly marked up.
The simultaneity requirement taking effect on 1 October makes this distinction unavoidable. With no option to add a translation afterwards, a manual process fails on the first busy day.
This article sets out how the infrastructure is built, step by step.
What Simultaneity Requires
BU BÖLÜMÜN ÖZETİ
- Content managed in one place
- Parallel approval
- Single publishing action
- Coordinated correction
Two texts appearing together depends on three things being ready behind the scenes.
Content managed in one place
Where Turkish and English are prepared separately and held separately, synchronisation is lost. One source must produce two outputs.
Parallel approval
If the Turkish text is approved and then sent for translation, a delay is built into the process by design. Approval must cover both.
Single publishing action
Two separate upload operations mean two separate timestamps. The system must publish both in one action.
Coordinated correction
If one text contains an error, both must be corrected. A one-sided fix leaves a content gap between the languages.
How It Is Built
BU BÖLÜMÜN ÖZETİ
- 1 · Identify recurring content
- 2 · Prepare bilingual templates
- 3 · Connect the terminology list
- 4 · Define the publishing flow
Four steps, and the order matters.
1 · Identify recurring content
Group a year of disclosures by type. Usually five or six types account for the great majority; template investment goes there.
2 · Prepare bilingual templates
For each recurring type, a Turkish and English skeleton. Variable fields — dates, amounts, party names — are marked separately, so a new disclosure becomes a matter of filling in blanks.
3 · Connect the terminology list
Company-specific terms are embedded in the templates so the same concept appears identically every time, and consistency is not left to human attention.
4 · Define the publishing flow
Who prepares, who approves, who publishes? Unless these three roles are written down, simultaneity breaks on the first busy day.
How to Write a Template
BU BÖLÜMÜN ÖZETİ
- Minimise variable fields
- Keep sentence structure simple
- Fix number and date formats
- Embed the disclaimer
A good template is easy to complete and hard to get wrong.
Minimise variable fields
The more blanks to fill, the higher the error rate. Anything that can stay fixed should stay fixed in the template.
Keep sentence structure simple
Long, nested sentences produce translation errors. Short sentences are safer in both languages.
Fix number and date formats
Decimal separators, thousand separators and date order differ between languages. Unless defined in the template, this becomes a recurring error.
Embed the disclaimer
The statement that the Turkish text prevails must appear in every disclosure. Fixed in the template, it cannot be forgotten.
Common Mistakes
BU BÖLÜMÜN ÖZETİ
- Outsourcing the whole thing
- Relying fully on machine translation
- Building site and filings separately
- Not timing the process
Four errors recur in this setup, and all four cost more later.
Outsourcing the whole thing
Waiting for an external translation on every disclosure is incompatible with simultaneity. External support belongs in template preparation, not in daily flow.
Relying fully on machine translation
It fails on financial and legal terminology. Usable for fixed text inside templates, risky in free text.
Building site and filings separately
Two channels fed by different terminology produce visible inconsistency. Both should draw from one glossary.
Not timing the process
Without knowing how long a bilingual disclosure takes to prepare, the bottleneck cannot be located. That time should be measured in minutes.
How to Test It
BU BÖLÜMÜN ÖZETİ
- Use a real disclosure
- Target: minutes
- Test for absence
- Weekly checks for the first month
Whether the setup actually works is only established by trying it.
Use a real disclosure
Run the full process on an actual past disclosure rather than a synthetic one, and time it.
Target: minutes
A recurring disclosure type should be ready in both languages within minutes. If it takes hours, either the template is incomplete or the process has too many steps.
Test for absence
Does the system work when the person who knows the process is away? A setup dependent on one individual stops when they do.
Weekly checks for the first month
The first four weeks of any new process are decisive. Weekly review catches errors before habits form around them.
A Solid Digital Foundation
BU BÖLÜMÜN ÖZETİ
- Multilingual architecture comes first
- Markup determines what gets served
- Permanent structure costs less than a temporary fix
- One setup does two jobs
Publishing infrastructure cannot be separated from site infrastructure; both belong to the same architecture.
Multilingual architecture comes first
If the site was built single-language, adding English content may require rebuilding — a timeline six weeks cannot absorb.
Markup determines what gets served
Declaring which page is the counterpart of which determines what appears for whom. The criteria are published in the Search Central documentation.
Permanent structure costs less than a temporary fix
A manual arrangement built to clear a deadline demands human intervention on every disclosure and becomes a hidden staffing cost within months.
One setup does two jobs
The structure built for filings also feeds the English side of the website. Corporate English content plans the two together.
Frequently Asked Questions
Sık Sorulan Sorular
The Turkish and English versions published at the same moment. Adding a translation afterwards is not an option.
Usually five or six cover the great majority of disclosures. The inventory establishes the number.
For fixed text within templates, yes. In free text it is risky: errors appear in financial and legal terms and liability stays with the company.
Inventory takes days, templates and terminology weeks. Single-language site architecture extends the technical side considerably.
Fewer disclosures mean fewer templates. But defining the process — who prepares, who approves — is necessary at any scale.
From the time taken. If a bilingual disclosure takes hours rather than minutes, there is a bottleneck.