Not a translation layer
Turkish is not an afterthought bolted onto an English site. At dorenva., English and Turkish are part of the work from the beginning. That changes the first question. We do not ask how to turn an English sentence into Turkish after the sentence is finished. We ask what each language needs to say, and how it should sound to the person reading it.
Translation can carry meaning while leaving the sentence itself behind. Word order, emphasis, and rhythm do not always travel together. A phrase that feels spare in one language may feel abrupt in another; preserving its exact shape can preserve the words and lose the voice. Writing each version with care means holding on to the intention, then finding the sentence that carries it naturally.
Our line, “Useful software, made with care,” has a Turkish counterpart: “Özenle geliştirilen faydalı yazılımlar.” The words are not arranged as a piece-by-piece copy. The two lines share a thought and meet their readers in the language they are using. That is a more useful kind of consistency than identical syntax.
Type that respects both
Language has a visible shape, and the typeface has to be able to hold it. We retired our first display typeface because it could not set Turkish. Letters such as ğ, ş, and İ were missing. A font can look polished in a specimen and still leave a language incomplete on the page.
Turkish characters are not decorative variants to approximate when convenient. The dotted and dotless forms of i, for example, are distinct letters. If a typeface lacks the required glyphs, a page may show a fallback character that changes the texture of the sentence or makes the typography visibly inconsistent. Checking the full character set is a basic part of choosing type for a bilingual product.
Space matters too. Text can take a different amount of room after it is written for each language. A heading may wrap; a button label may need more width; a line break that feels balanced in English may interrupt the Turkish sentence. These are design questions, not reasons to shorten one language until it fits the other's frame. Both versions deserve layouts that read comfortably.
The long version
The same care applies beyond headlines. An interface is made of small pieces of language: labels, empty states, instructions, confirmations, and errors. Each one has a job. A label should identify a control. An error should say what happened and what can be done next. The words may be brief, but their clarity affects whether the screen feels usable.
Those pieces should be considered in both languages while the interface is being shaped. If Turkish is added only after a layout and its assumptions are settled, the work becomes a series of repairs: a label is squeezed into a narrow button, an explanation is shortened until it stops helping, or a line break lands in the wrong place. Starting with both languages makes it easier to notice these constraints before they become expensive to undo.
There is also a matter of tone. A calm, precise voice should remain calm and precise in each language, but it does not have to use the same sentence pattern to get there. We listen for whether the text sounds like a person wrote it for this reader, whether it gives the right amount of context, and whether it asks for action without adding pressure. Naturalness is part of usability.
One standard, two voices
Bilingual design does not require every sentence to match in length or structure. It asks both versions to carry the same intent, care, and useful detail. Sometimes the best Turkish sentence will be shorter; sometimes it will need another phrase to make the action clear. The measure is whether the reader can understand and use the product, not whether the two screens look like mirrors.
For a small independent studio, this is a practical commitment as much as a writing preference. It touches the words, the type, and the space around both. We make small on-device apps, and the app should feel considered whether someone opens it in English or Turkish. If one language gets the clear version and the other gets the leftover, the design is unfinished.
Özenle geliştirilen faydalı yazılımlar.