An approved Arabic translation is not yet an approved product video. A Latin model name, a capacity figure and a price can all be correct in the source document while their relationship becomes unclear in the finished composition. A buying brief needs to specify who checks the rendered message—not just who supplies the words.
For overseas brands commissioning production through China, the useful first deliverable is a short mixed-text sample taken through the real export workflow. It reveals what translation, typography and placement work the project actually needs. This article addresses product-information delivery, not a complete cultural, language or advertising-compliance review.
Right-to-left does not mean reversing every element
W3C’s Arabic & Persian Layout Requirements explains that Arabic script runs right to left while numbers and normally left-to-right scripts retain their own direction. The document is an editor’s draft focused on Standard Arabic and Persian layout, not a video-platform acceptance specification.
Its Unicode Bidirectional Algorithm basics also explains why surrounding text and paragraph direction affect neutral characters such as spaces and punctuation. Right alignment alone is therefore not a substitute for checking the displayed relationship between a product code, a number and its surrounding words.
Adobe’s Creating and editing text layers, updated May 8, 2026, describes After Effects’ Universal Text Engine support for Arabic, right-to-left text and mixed numbers or English letters. That establishes an available capability. It does not certify the font, animation template or export used in an individual production.
ONCE proposes the following review method to turn those distinctions into a practical scope of work.
Review three layers with different owners
| Review layer | What must remain correct | Who resolves the issue |
|---|---|---|
| Source content | Model, value, unit, currency and qualifying conditions | Brand owner confirms product facts; language reviewer confirms expression |
| Rendered text | Letter shaping, mixed-script order, punctuation, wrapping and animation | Typesetter or motion designer investigates settings; language reviewer checks the export |
| Product and playback space | Callouts point to the right parts and remain readable in the agreed placement | Editor preserves physical truth; publishing owner checks the target playback environment |
The split prevents two common delegation mistakes: asking a translator to certify an unfamiliar editing workflow, or asking an editor who cannot read Arabic to approve the language by appearance.
A USB-C label may move to the other side of a composition. The physical port does not move with it. If a callout identifies a button on the filmed product, flipping the footage to make space for copy can misrepresent that product. Reposition the graphics, choose another shot or commission a new angle where necessary. Layout adaptation is not permission to alter physical relationships.
Choose a difficult sample, not the cleanest slogan
Imagine a fictional device with the model name X7-Pro, USB-C connectivity and a 256 GB capacity, accompanied by a promotional price awaiting approval. These are illustrative fields, not a real product specification. Put the model, values, complete conditions and relevant product action into the sample rather than testing only a short headline.
The brand should supply fixed fields first: spelling, capitalization, hyphens, values, units, currency and offer conditions. A reviewer familiar with the target market should approve numeral style and amount formatting. “Middle East version” is not a sufficient formatting instruction, and this article does not prescribe one regional convention for every brand.
Run the sample through normal playback, entry and exit animation, line wrapping, each requested aspect ratio and final export. A complete number on a paused frame does not establish that its animated reveal is understandable. A successful landscape layout does not establish that the model and its qualifier remain connected in a narrower frame.
Make feedback actionable: identify the file version, timecode, affected element and intended reading. “The value and unit become difficult to associate after the line break” gives the designer a solvable issue. “The Arabic looks wrong” does not. Keep product-fact approval separate from language approval, even when both reviewers inspect the same clip.
A caption file and a burned-in export need separate checks
Burned-in text is part of the video image. Selectable captions are displayed by the destination player. Approving an MP4 should not automatically approve the accompanying caption track.
ONCE recommends checking graphics in the export for readability, obstruction and animation, then checking uploaded captions for displayed order, wrapping, timing and completeness. Name the platform, player or device included in the review. A successful test in one environment is not a claim of universal compatibility.
If the supplied master already contains permanent English copy, assess the available clean footage and editable project before quoting. Removing or covering that copy may affect the product image. Rebuilding the composition is a different task from translating a sentence.
AI can help draft text, organize fields or create clean background material. For exact model names, prices and feature statements, retaining editable text layers gives the production team a controlled revision path. This is a workflow recommendation, not a claim that every generative model is incapable of rendering Arabic correctly. Generated imagery still requires an independent check of product information.
Buy a maintainable language version
Separate five work items in the estimate: source-field confirmation, translation and language review, mixed-text graphics and animation, aspect-ratio adaptation, and output checks. There is no universal percentage uplift implied here. An established template may reduce design work, but new models, prices and caption files still require review.
Agree who initiates changes when an offer or product name changes. Update the approved source, adjust affected layouts, render the relevant files and review the corresponding publishing destination. Depending on the contract, delivery can include approved copy, a fixed-field register, editable project components, font-use information, final files and a review record. Project-file and font rights must be agreed rather than presumed.
For production partners, reusable rules, review samples and categorized rendering issues could support a more repeatable localization service. Customer launch details and unpublished prices should remain within the project’s authorized access. This is a proposed service design, not a reported ONCE dataset or cost saving.
Bring the source video, target market, publishing destination and most complicated text passage to a discussion of ONCE’s video production solutions. Approve that passage through the actual delivery path before scaling the batch. The finished product is not merely an Arabic document: it is correct product information that survives the journey to the viewer.
Sources checked October 14, 2026. W3C documents are living technical resources; the layout document is an editor’s draft. No customer project or live player-compatibility test was performed for this article. The original AI-generated cover is conceptual imagery.
