Keep each preparation item separate when the language changes

A preparation list is more than a sentence containing several instructions. If staff need to complete its items independently, the information must keep those boundaries throughout translation, display and storage. A fluent paragraph can conceal a broken task when three separate requirements arrive as one.

Consider a fictional supplier preparing a meeting-room display inspection. The customer-facing page explains what information the coordinator should provide. Each preparation item has its own reference and completion state. The business has approved the meaning, and the Arabic wording is treated as approved input to this example. The investigation concerns what the application does with that input; it does not establish that any real service or translation has been approved.

Start with the three records the owner actually uses

The case, V-28, contains these requirements. They are independent tasks, not steps that must be completed in the order shown.

The commas inside P-2 belong to one instruction. They do not create three independent preparation requirements. The operating owner confirms that the reference, model and installed location form the information requested by that single item.

In the source record, P-1 is complete, P-2 is awaiting information and P-3 is complete. The coordinator must be able to see the remaining P-2 request without reopening the two completed items. Those states provide a useful test of whether the structure survived.

Locate the step that turns records into punctuation

The English and Arabic source arrays both contain the same three references with their respective text. The receiving case also supports an array of preparation records. Neither end requires a paragraph.

The fault is in an intermediate presentation adapter. It joins the localized texts into one display string, using the punctuation chosen for that language. A later function splits that string on an ordinary ASCII comma and treats each resulting segment as an item. The application has discarded its reliable boundaries and is trying to recover them from prose.

For the Arabic representation, the separator is the Arabic comma, ،. The ASCII split does not separate the string, so the downstream view receives one combined item. It offers one completion control for the combined text. P-2 can no longer remain pending independently of P-1 and P-3.

The English path is not a sound control merely because it splits something. P-2 contains commas within its sentence, so that same algorithm can divide one approved requirement into several fragments. Changing the splitter to recognize both comma characters would preserve neither language's intended structure.

Preserve the array and translate its text

The selected correction removes the join-and-split round trip. The adapter carries the three original records through to the view. Each record retains its reference, completion state and approved language-specific text. Translation affects the text associated with an item; it does not determine how many operational records exist.

For the customer page, the renderer presents a semantic list and associates each instruction with its own permitted response control. The W3C content-structure guidance explains the purposes of different list types. That guidance supports meaningful presentation, but the application must separately preserve the records and states behind the list.

Arabic direction and mixed references still require review in context. A correct list structure does not automatically settle focus order, naming, language quality or how an identifier is read aloud. Those are distinct checks with the intended users and appropriate reviewers.

Complete the task without changing the requirements

In the fictional corrected review, the coordinator opens V-28 in Arabic and sees three items. P-1 and P-3 show their existing completed states. P-2 shows the entire approved Arabic sentence, including its internal commas, and remains awaiting information.

The coordinator supplies the information required for P-2 through the supported item-specific operation. The case owner reviews that response and marks P-2 complete. The final case has three completed requirements with their original references. It does not contain a newly invented combined requirement or extra records derived from sentence fragments.

Switching the same demonstration to English displays the three English sentences with the same states. The item count and completion history do not change with the language. The English commas remain text inside P-2.

The verification also uses a two-item case and an empty preparation list. Two records remain two; the empty list uses the agreed empty-state message rather than constructing a blank requirement. A missing approved Arabic text is held for content review. It is not silently presented as a completed Arabic version or rebuilt by translating punctuation alone.

Handle records already damaged by flattening

The repair prevents the faulty transformation for new reads and updates, but it does not prove how an older combined item should be separated. If its source references and original states remain available, an authorized owner can review a correction against that evidence. If they do not, the record needs clarification. Splitting a sentence cannot recover which requirement was previously completed.

The release record should therefore distinguish the corrected adapter from any separately approved historical repair. Retain enough evidence to explain why a case was changed, and do not mark all preparation complete simply because the combined item previously had a tick.

Arabic and English experience work should follow this complete task: approved meaning, structured information, readable presentation and the result staff uses. For a first discussion, bring an invented list with one unfinished item and a sentence containing ordinary punctuation. It will reveal more than a screenshot of three translated lines.