CartVisualPackaging studio / FIELD GUIDE
How do you proof Arabic text mixed with Latin names and numbers?
Preserve the approved logical text, then have a qualified language reviewer read the actual mixed-direction artwork and final export. Check the exact Latin identifier, quantity and punctuation in context. Do not reverse characters or apply a single rule to every number just to repair one screenshot.
List the values the reader must recover
Start with the authorized local-language copy, Latin identifiers, values, units and punctuation. Keep the approved logical text independently of a screenshot. The layout application must handle the actual script and direction; generated lettering is not the editable text authority.
W3C’s mixed-string examples show why surrounding direction, the type of data and language context matter. A model identifier is not necessarily treated like a date or range. Those examples explain the problem; they are not a print-application setup or a universal rule to reverse digits.
Use a specific readback rather than “looks fluent”
Fictional exercise only: an approved Arabic sentence contains the unchanged model identifier “AB-12” and quantity “250 mL,” with the model in parentheses. This guide does not invent or approve an Arabic translation. Supply the actual authorized sentence to a qualified reviewer.
| Element | Ask the reviewer to identify | Reject or resolve |
|---|---|---|
| Latin identifier | The intended model AB-12 | Changed letters/digits, or association with the wrong phrase |
| Quantity and unit | 250 with its intended unit mL | A different value/unit or ambiguous association |
| Parentheses and punctuation | Which words or value they belong to | Balanced-looking marks attached to the wrong run |
| Local-language copy | Its intended wording and reading sequence | Missing words, broken shaping or altered meaning |
A reviewer should be able to recover the intended model and quantity from the rendered line without being coached by the worksheet. If they cannot, return the specific ambiguous run to the designer. Do not change the source identifier to make a visual arrangement easier.
Check source, export and panel independently
First compare the editable source and approved logical text. Then open the exact supplier-bound export and repeat the readback. Finally inspect the supplied panel view: a fold, crop or curvature can interrupt a correct line. Record which of these stages first differs.
Use the design application’s appropriate text and direction controls with a competent operator. Do not paste arbitrary invisible direction marks from a web example into every string. A change of font, line width or wording may reopen the check; a correct source screenshot does not approve a later export.
Preserve the reviewed copy and its limits
Keep the copy revision, artwork revision, exported-file identity, relevant panel and reviewer finding together. Ask the supplier to resolve its actual production requirements rather than claiming that a web demonstration or a language readback certifies the whole package.
CartVisual packaging concepts are separate from production typesetting. Use panel language hierarchy for the broader reading path and exact character handoff for source identity. No Arabic translation, layout application, PDF or physical proof was tested for this exercise.
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- CartVisual: editorial scope and evidence policy · Review date not separately recorded
- W3C Internationalization: directional context and mixed strings · Reviewed
Frequently asked questions
Should every number in an Arabic line be reversed?
No. Preserve the approved data and have its actual language, meaning and rendering reviewed; identifiers, ranges and dates are different cases.
Does fluent-looking generated script approve the copy?
No. Compare authorized editable text with the exact rendered export and obtain qualified review.
Does W3C HTML guidance configure a packaging PDF?
No. It illustrates directionality; the actual design application and supplier workflow require their own handling.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in CartVisual.
Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.
Explore asset creation tools Check pricing and credits