From 9:00 to 12:00 on opening day, 14 Arabic, 16 Spanish and 9 Portuguese requests landed simultaneously. Industry context is in "Phase Two of the 140th Canton Fair Opens — Arabic, Spanish and Portuguese Hit the Translation Desk Simultaneously". This article is only about delivery — every request below is listed with time received, client type, what was delivered, time taken and where we made the mistake. A real timeline with no polishing after the fact.
9:00–10:00: Three lines running at once, Arabic hits a branch error first
9:05 — a Saudi buyer handed over four product catalogues and asked for a formal Arabic version. Our Arabic translator defaulted to the Gulf branch — correct in principle — but the buyer shook his head on the first page. The term for "composite flooring" had been rendered as "لوحة مركبة", which is standard in central Gulf but the buyer was from northern Qatar where "لوحة لامينيه" is the household expression. This was a finer-grained version of yesterday's "Gulf vs North African Arabic" mix-up — regional variation within the Gulf itself. Our proofreading seat caught the mistake before delivery, but it cost an extra hour. Delivery moved from the agreed four hours to five.
Over the same window the Spanish line received two Brazilian quotation requests: one contained a container code error (client gave Brazilian local "20 pés padrão", translator rendered as Castilian "20 pies estándar"); the other used the European EN standard for fire ratings when the client needed Brazilian NBR 15575. Both errors were caught by proofreading, but the second one required a full standard-system rewrite, costing an extra two hours.
10:00–11:30: MTPE volume rises, hardware cross-contamination exposed
10:17 — Arabic MTPE request: client sent an Arabic conference recording captured on AI glasses, and the machine's Arabic transcript had drifted into Brazilian Portuguese "composto laminado" (for composite flooring). Our translator converted it to the North African loan-transliteration "بلوك لامينيه" instead of the Kuwait-specific term used by the speaking buyer "لوحة لامينيه". Our MTPE rule is to match terminology to the speaker's region, but here the speaker was Kuwaiti and the AI had already drifted — the error direction was the reverse of what we normally expect. Our proofreading seat spent roughly 30 minutes tracing the root cause before replacing the entire passage with the correct term.
10:45 — document translation Spanish emergency request: a Chilean building materials importer needed a Spanish quotation sheet (Chilean standard) in four hours. The timeline was so tight the translator started from her general knowledge first. Our proofreading seat insisted the client confirm Chile's container code system on the spot. The buyer flipped through his own container code manual for five minutes, found our translation was wrong — Chile uses "20 pies estándar Chile", distinct from both Brazilian "20 pés padrão" and Castilian "20 pies estándar". That insistence saved the client at least a full day of rework.
11:30–12:00: Certified stamp requests pile up, timeline starts to stretch
11:42 — Arabic certified stamp request from a Saudi client: certificate of origin + CIQ inspection form in Arabic, certified stamp required. Translation: four hours. Proofreading: one and a half. Stamp processing: ten and a half hours — because the client required a stamp from the specific authority designated by Saudi customs, and our standard in-house stamp is not valid there. This was the slowest job of the day at 16 hours total, two hours slower than yesterday's longest stamp job, because the Saudi-designated institution was closed on weekends and we had to arrange two trips to hit their operating hours.
11:57 — Portuguese certified stamp request from a Brazilian client: Portuguese-language contract with stamp. We currently have only one in-house Portuguese translator, with proofreading covered by our Spanish European branch translator. Translation: three hours. Proofreading: one. Stamp processing: eight — the Brazilian-certified institution in Guangzhou has only one point of contact, and we arranged a dedicated person to walk the process through as soon as we received it. Twelve hours total, faster than Arabic but already the absolute limit of our Portuguese capacity.
What we learnt today: regional branches need to go down to country, not region
Yesterday we split Arabic into Gulf / North African, Spanish into Latin American / European, Portuguese into Brazilian / European. Today's opening day exposed a deeper problem: even inside the Gulf, country-specific usage differs — Saudi northern and southern Arabia have accent differences; Chile and Brazil use different Spanish standard systems; the Brazilian states of Rio Grande do Sul and São Paulo use slightly different Portuguese. Our termbases need to be refined further to the country or even regional level, otherwise proofreading will always be firefighting.
Translator observations from day one are in "Phase Two Day One Translator Observation". For Phase Two's remaining three days plus Phase Three multilingual documents or stamps, contact us to reserve a slot.