Basque to Somali: a condition for accepting a form is not a reason it was rejected
Preserve what is established and what is only assumed
A Basque message about an application can describe an actual decision, set a condition for a later decision, or imagine what would happen in another situation. When translating into Somali, preserve that distinction. The presence of an application, a missing document, and an acceptance decision in one sentence does not establish that any particular decision has already been made.
Laka illustrates Basque conditional contrasts through sentences about Miren coming and Mikel leaving. Her examples distinguish a conditional consequence from a counterfactual consequence, and show that the unrealized aspect marker does not always simply indicate future time. Reading one recognizable future-looking element is therefore insufficient for interpreting the whole sentence.
Nilsson’s Somali grammar distinguishes conditional clauses commonly introduced by haddii from reason expressions including maxaa yeelay, sababta oo ah, and waayo. It also explains a different causal construction with maadaama. These are documented construction choices, not interchangeable labels for any connection between two events.
Keep a missing attachment separate from an official outcome
Imagine a Basque training coordinator explaining registration to a Somali-speaking applicant. A message might say that the application will be considered if the attachment arrives. Another might explain that it was returned because the attachment was missing. This original administrative scenario separates an outstanding requirement from a completed response by the coordinator.
The conditional version should not make the applicant believe that the attachment has already arrived. The explanation of a returned application should not become a new promise of acceptance. Consideration, acceptance, and return for correction are different actions; preserving a connecting word while substituting one outcome for another still changes the practical message.
A hypothetical discussion adds another distinction. A colleague may ask what would have happened if the attachment had arrived earlier. That does not establish an extension to the current deadline. Keep a discussion of an alternative past separate from instructions that the applicant can still act on today.
Identify which rule applies to the current submission
A coordinator may forward an older message setting a condition and then add a new decision. The old requirement and the new outcome belong to different points in the exchange. Retain dates or message boundaries when available so that a recipient does not mistake an earlier possibility for the latest status.
Do not turn an explanation into an accusation. If the source says that a file could not be opened, it need not establish that the applicant sent the wrong file or omitted it deliberately. A technical problem, an absent attachment, and a rejected application require separate evidence. Fluent wording should not fill those gaps with an invented chain of causes.
For this pair, check the result against the applicant’s next step. Does the message ask for an attachment, explain an action already taken, or discuss an unrealized alternative? Keep the requirement, the relevant submission, and the decision attached to their own clauses. That preserves the coordinator’s actual commitment without promising acceptance or announcing rejection that the source never stated.
Language references