Tatar (Russia) style guide¶

Characters¶

Country/region: Russia, Tatarstan.
Lower-case: а, ә, б, в, г, д, е, ё, ж, җ, з, и, й, к, л, м, н, ң, о, ө, п, р, с, т, у, ү, ф, х, һ, ц, ч, ш, щ, ъ, ы, ь, э, ю, я
Upper-case: А, Ә, Б, В, Г, Д, Е, Ё, Ж, Җ, З, И, Й, К, Л, М, Н, Ң, О, Ө, П, Р, С, Т, У, Ү, Ф, Х, Һ, Ц, Ч, Ш, Щ, Ъ, Ы, Ь, Э, Ю, Я
Caseless-script characters: n/a. Extended Latin characters: n/a.
Total number of characters: 39.
Alphabetical order is not necessarily the sorting order.
Unicode codes of Tatar letters match Russian (0410 to 044F, 0401, 0451). Tatar-specific letters: Ә (U+04D8), ә (U+04D9), Җ (U+0496), җ (U+0497), Ң (U+04A2), ң (U+04A3), Ө (U+04E8), ө (U+04E9), Ү (U+04AE), ү (U+04AF), Һ (U+04BA), һ (U+04BB).

Date¶

Calendar: Gregorian.
First day of the week: Monday (Дүшәмбе).
First week of the year: the week that contains January 1.
Separator: . (period)
Default short date format: dd.MM.yyyy. Example: 17.03.2011
Default long date format: dd MMMM yyyy ел. Example: 17 март 2011 ел
Additional short date format 1: dd.MM.yy. Example: 17.03.11
Additional short date format 2: n/a. Additional long date formats: n/a.
Leading zero in day field for short date: yes. Leading zero in month field for short date: yes.
Digits for year in short date: 4.
Leading zero in day field for long date: yes. Leading zero in month field for long date: n/a.
Digits for year in long date: 4.
Date format for correspondence: dd MMMM yyyy ел. Example: 17 март 2011 ел
Partial date format: MMMM yyyy
Format codes: d = day (d no leading zero, dd leading zero, ddd abbreviated day name, dddd full day name); M = month (M no leading zero, MM leading zero, MMM abbreviated name, MMMM full name); y = year (yy two digits, yyyy four digits).

Time¶

24 hour format: yes.
Standard time format: HH:mm:ss. Example: 21:20:12
Time separator: colon :. Example: 15:27:38
Hours leading zero: yes. Example: 07:35:20
AM designator: n/a. PM designator: n/a.
Separate milliseconds with a comma: 03:24:12,09
Short time format: H:mm and HH:mm

Days¶

First letter capitalized: no.
First day of week: Monday, дүшәмбе.
Monday: дүшәмбе, дүш., shortest Д
Tuesday: сишәмбе, сиш., shortest С
Wednesday: чәршәмбе, чәрш., shortest Ч
Thursday: пәнҗешәмбе, пәнҗ., shortest П
Friday: җомга, җом., shortest Җ
Saturday: шимбә, шим., shortest Ш
Sunday: якшәмбе, якш., shortest Я

Months¶

First letter capitalized: no. Long date form: n/a for every month.
January: гыйнвар, гыйн. Sometimes translated as январь.
February: февраль, фев.
March: март, мар.
April: апрель, апр.
May: май, май
June: июнь, июнь
July: июль, июль
August: август, авг.
September: сентябрь, сен.
October: октябрь, окт.
November: ноябрь, нояб.
December: декабрь, дек.

Phone numbers¶

International dialing code: 7. Area codes used: yes. Digits in area code: 2; 3; 4; 5. Separator: hyphen.
Digits, domestic: 6; 7; 8; 9; 10; 11. Digit groupings, domestic: (###) ###-##-##, (####) ##-##-##, (#####) #-##-##
Digits, local: 3; 4; 5; 6; 7. Digit groupings, local: ###-##-##, ###-####, ##-##-##, ###-###, #-##-##, ##-##, #-##
Digits, mobile: 10. Digit grouping, mobile: +7 (###) ###-####
Digits, international: 11. Digit grouping, international: +7 ###-###-##-##
Mobile numbers always have a federal format number, always +7 (###) ###-##-##. Dialed inside Russia, +7 can be replaced with 8, so such numbers are sometimes written 8 (###) ###-##-##.
A mobile number may also have an associated number in domestic format, the same format as fixed phones, with the same dialing rules.
Put the area code in brackets. Example: (843) 123-45-67, where 843 is the area code for Kazan and 123-45-67 is the telephone number.

Addresses¶

Never use real address information in examples.
Format order: [Title/Honorific] LastName-FirstName+MiddleName [or initials]; [CompanyName]; [CountryCode-] PostalCode; [Country – for letters going outside Russia]; Region; [District – for little towns and villages]; City [village etc.]; Address.
Example: Исмәгыйлев Фәнил Ринат улына 654321 Татарстан Республикасы Казан шәһәре Татарстан ур., 25-14
Local postal code format: хххххх
Items in brackets are optional. Include the country in international addresses only.
Write the name of the addressee in the Dative case.
Usually abbreviate first name and middle name: Ф.Р.Исмәгыйлевка
Write the sender's address in the same format. Put the sender's name in the Ablative case: Ф.Р. Исмәгыйлевтан
Put the address on the right side of the envelope, the return address in the upper left corner.

Currency¶

Currency name: ruble – рубль – сум. Symbol: р.
The currency always comes after the amount, always with a space between amount and currency.
Positive currency format: 123 456,15 р. / 123 456,15 сум
Negative sign symbol: - (minus). No space between minus and amount.
Negative currency format: -123 456,15 р. / -123 456,15 сум
Decimal symbol: , (comma). Digits after decimal: 2.
Digit grouping symbol: space. Digits in digit grouping: 3.
Positive example: 123 456 789,00 р. / 123 456 789,00 сум
Negative example: - 123 456 789,00 р. / 123 456 789,00 сум
ISO currency code: RUB
Subunit name: kopeck – копейка – тиен. Subunit symbol: коп. / тиен. Example: 17 коп. / 17 тиен
Рубль and копейка are the official names in Russia. Use the Tatar names in most contexts.
Do not abbreviate the currency name or the subunit name in Tatar.

Digit groups¶

Decimal separator: , (comma). Examples: Бастыру 16,78 секундта тәмамланачак., 150,67 сум акча түләргә кирәк.
Thousand separator: space. Example: 14 400
Use a period in version numbers: Windows 3.11, Internet Explorer 5.5
You may omit the thousand separator (space) for numbers with 4 digits in the integer part.
Numbers outside regular text may or may not have thousand separators. Values in Excel have none.

Measurement units¶

Metric system commonly used: yes. Temperature: Celsius.
Linear measure: Kilometer -> километр, км; Meter -> метр, м; Decimeter -> дециметр, дм; Centimeter -> сантиметр, см; Millimeter -> миллиметр, мм
Capacity: Hectoliter -> гекталитр, гл; Liter -> литр, л; Deciliter -> децилитр, дл; Centiliter -> сантилитр, сл; Milliliter -> миллилитр, мл
Mass: Ton -> тонна, т; Kilogram -> килограмм, кг; Gram -> грамм, г; Decigram -> дециграмм, дг; Centigram -> сантиграмм, сг; Milligram -> миллиграмм, мг
English units: Inch -> дюйм, "; Feet -> фут, фт; Mile -> миля, n/a; Gallon -> галлон, n/a; Pound -> фунт, n/a
Always measure temperature on the Celsius scale. Recalculate all other scales, such as Fahrenheit, into Celsius.
Display temperature as x°С: the temperature, then the degree sign, then the capital Latin letter C.
Below zero, put the minus sign - before the temperature. At or above zero the plus sign + is optional and rarely used. Examples: -27°C, 0°C, 25°C
Use the quotation mark instead of дюйм for inches only when the full variant is technically impossible (length restrictions, or a locked English source string with the " sign).

Percentages¶

Separate the percent sign % from the number with a non-breaking space in documentation, including online documents: 10 %
Do not put the percent sign before numbers in software or in references to the user interface in documentation.

Sorting¶

The upper case of a character comes before the lower case.
Non-alphabetical characters (symbols like @ ! #) sort before the letters of the alphabet.
Digits sort after non-alphabetical characters and before the letters of the alphabet.
Sort words by the first letter; if the first letters match, by the second letter, and so forth. A word that is the initial part of another word goes first: бал, балта, балтачы
The upper case of a character comes before the lower case: Алабуга (the city) goes before алабуга (the fish).
Character sorting order with code points: А 1040, а 1072, Ә 1240, ә 1241, Б 1041, б 1073, В 1042, в 1074, Г 1043, г 1075, Д 1044, д 1076, Е 1045, е 1077, Ё 1025, ё 1105, Ж 1046, ж 1078, Җ 1174, җ 1175, З 1047, з 1079, И 1048, и 1080, Й 1049, й 1081, К 1050, к 1082, Л 1051, л 1083, М 1052, м 1084, Н 1053, н 1085, Ң 1186, ң 1187, О 1054, о 1086, Ө 1256, ө 1257, П 1055, п 1087, Р 1056, р 1088, С 1057, с 1089, Т 1058, т 1090, У 1059, у 1091, Ү 1198, ү 1199, Ф 1060, ф 1092, Х 1061, х 1093, Һ 1210, һ 1211, Ц 1062, ц 1094, Ч 1063, ч 1095, Ш 1064, ш 1096, Щ 1065, щ 1097, Ъ 1066, ъ 1098, Ы 1067, ы 1099, Ь 1068, ь 1100, Э 1069, э 1101, Ю 1070, ю 1102, Я 1071, я 1103
Examples of sorted words: №, *, 7, а, абага, агач, Алабуга, алабуга, бал, балта, балтачы, бәла-каза, була, ватык, гер, давыл, дәрес, давыл, егет, жанр, җилбәзәк, зиннәтле, искиткеч, йомран, күрәк, ләззәт, мең, нигез, оя, өстәмә, папка, республика, салкын, тигез, уртача, үгет, фото, хәреф, һава, цитата, чабата, шакылдау, щит, ырым, эзләнү, юка, яңгыр

Geopolitical concerns¶

Check maps, flags, country/region, city and language names, art and graphics, and cultural content for accuracy and political restrictions.
Check country/region, city and language names regularly, even previously approved ones.
Check cultural content, clip art, religious symbols, and body and hand gestures for appropriateness in the target market.

Adjectives¶

For attributive nominal constructions, use possessive forms (изафә) rather than an adjective.
en Information unit -> Информация блогы; not Информацион блок
en Arithmetic operation -> Арифметика гамәле; not Арифметик гамәл
Adjectives often take negative meaning through a derivative marker.
en undefined -> билгеләнмәгән
en invisible -> күренми торган
en unavailable -> мөмкин түгел

Articles¶

There are no definite or indefinite articles in Tatar. Where indeterminacy matters, use other linguistic categories to express it.
en Insert a disc -> Диск куегыз (do not use the affix, instead of дискны)
Plural form can express indeterminacy.
en Remove a printer -> Принтерларны бетерү
en Send or receive a file -> Файллар җибәрү яки алу
en Install a program from the network -> Программаларны челтәрдән урнаштыру
en You cannot change part of an array. -> Массив өлешләрен үзгәртергә ярамый.
Use the word бер and its forms as an indefinite article.
en Cell must contain a value. -> Шакмакта берәр кыйммәт булырга тиеш.
en Value must be a number. -> Кыйммәт берәр сан булырга тиеш.
en There is already a macro assigned to that key. You should assign a different keyboard shortcut. -> Әлеге төймәгә бер макрос билгеләнгән инде. Башка бер төймә билгеләгез.

Capitalization¶

Use capitalization very sparingly. Capitalize only when you have to.
Source capitalization does not mean the term is capitalized in Tatar. Do not mimic source capitalization. Use Tatar spelling conventions. Over-capitalization is awkward and creates UI inconsistencies.
Capitalize names of UI elements (commands, menus, dialog box titles) and program names. Capitalize the first word only. Enclose names of UI elements in quotes when referring to them.
en On the View menu, click Filter -> “Күренеш” сайлагында “Фильтр” пунктын сайлагыз
en On the Tools menu, click Internet Options, and click the Security tab -> “Сервис” сайлагында “Интернет көйләүләре” параметрын сайлап, “Иминлек” салынмасын ачыгыз.
If a capitalized English noun becomes two Tatar words, capitalize only the first word. Apply spelling rules consistently.
Capitalize both words in country and state names (Татарстан Республикасы, Американың Кушма Штатлары) and political names (Дәүләт Советы, Министрлар Кабинеты).
Capitalize names of people: Исмәгыйлев Фәнил Ринат улы
Capitalize acronyms: OLE, BIOS
Capitalize Интернет.
Do not capitalize languages, nationalities, or adjectives derived from them: Tatar interface -> татарча интерфейс; the English -> инглизләр; Spanish -> испан теле
Do not capitalize month names or day names: гыйнвар, җомга
Do not capitalize Web: Файлны вебка нәшер итү
Capitalize the first Tatar word if the first English word is capitalized. Leave it lower-case if the English word is not capitalized.
en unknown software exception\r\n -> билгесез программа искәрмәсе\r\n
en Acquired -> Алынган
en Log off user -> Кулланучы сеансын тәмамлау
en Edit... -> Төзәтү...
Some strings are concatenated at run-time and may lack a subject or start in the middle. Do not start such strings with an upper-case letter unless Tatar spelling rules require it.
en is trying to connect to this computer. If you allow, you will be disconnected, but you can resume later. Do you want to allow this connection?\r\n -> бу санакка тоташмакчы була. Рөхсәт итсәгез, сезнең белән тоташу өзеләчәк, ләкин соңыннан аны дәвам итеп булачак. Бу тоташуны рөхсәт итәсезме?\r\n

Compounds¶

Keep compounds understandable and clear. Avoid overly long or complex compounds: express the relationship among the components verbally.
en Internet Accounts -> Интернет хисап язмалары
en Logon script processing -> Теркәлү сценарие башкарыла
en Workgroup Administrator -> Эш төркеме администраторы
en Internet News Server Name -> Интернеттагы яңалыклар серверы исеме
Transliterate components like audio, video, web. Do not localize them. If the component ends with a vowel, write it jointly. If it ends with a consonant, write it with a hyphen.
en Media player -> Медиауйнаткыч
en Audio record -> Аудиоязма
en Video card -> Видеокарта
en Web page -> Веб-бит
en Web content -> Веб-эчтәлек
en Flash drive -> Фләш-диск
Product names are trademarked and stay unchanged. Write Tatar additions to a product or component name separately, in a possessive form (изафә).
en Windows password -> Windows серсүзе
en Microsoft Word document -> Microsoft Word документы
en Microsoft SQL Server Database -> Microsoft SQL Server мәгълүмат базасы
en Microsoft BackOffice product family -> Microsoft BackOffice продуктлар төркеме
en ActiveX Control -> ActiveX идарә элементы
For an abbreviation or numeral followed by a component name:
en CD-ROM drive -> CD-ROM йөрткече
en 2-D gridlines -> 2-D сызыклары
en 24 bit color value -> 24 битлы төс сыйфаты
en 3.5 Floppy -> 3,5 дюймлы дискета
en 51/4-inch Floppy -> 51/4 дюймлы дискета
en 35mm slides -> 35 мм-лы слайдлар

Gender¶

Does not apply to Tatar.

Genitive¶

Does not apply to Tatar.

Modifiers¶

Does not apply to Tatar.

Nouns¶

Tatar does not differentiate noun classes by animacy, shape, or gender. Add the correct hard or mild case and plural affixes to English loan words.
English loan words are usually hard and take hard affixes, like сервер. Words ending in -ция (English -ion) take mild affixes, like функция (функциягә, функциянең).
en Delete it from server. -> Аны сервердан бетерү
en Enter a password to log into the server -> Серверга кереп теркәлү өчен серсүз кертегез
en DNS cannot resolve the server IP address -> DNS сервер IP-адресын ачыклый алмады
en Verify the name of the server's certificate -> Сервер сертификатының исемен тикшерү
en Clients -> Клиентлар
en Websites -> Веб-сайтлар
en Functions -> Функцияләр
en Telephones -> Телефоннар
en Administrators -> Администраторлар

Prepositions and postpositions¶

Tatar marks syntactic cases with postpositions and case affixes, not prepositions. Translate prepositions carefully, by context.
When a prepositional phrase is unfinished or contains a placeholder, avoid non-grammatical constructions with incorrect word order. Rephrase with nouns of appropriate common meaning instead of prepositions.
en migrate to (e.g., disk) -> (Дискка) күчерү, Күчерү урыны; not ...га күчерү, not Кая күчерү. Rephrasing is possible.
en Migrate from (e.g., disk) -> (Дисктан) күчерү, Шуннан күчерү:; not ...дан күчерү, not Кайдан күчерү. Rephrasing is not possible; demonstrative pronouns with a colon are usable but not better.
en import to (e.g., an application) -> (ниндидер) кушымтага импортлау, Импорт:, Импорт урыны; not Кая импортлау
en import from (e.g., an application) -> (ниндидер) кушымтадан импортлау, Импорт чыганагы; not Кайдан импортлау
en export to (e.g., an application) -> (ниндидер) кушымтага экспортлау, Экспорт:, Экспорт урыны; not Кая экспортлау
en export from (e.g., an application) -> (ниндидер) кушымтадан экспортлау, Экспорт чыганагы; not Кайдан экспортлау
en update to (e.g., version) -> (версиягә) кадәр яңарту, Яңарту:; not ...кадәр яңарту, not -га яңарту
en upgrade to (e.g., version) -> (версиягә) кадәр яңарту, Яңарту:; not ...кадәр яңарту, not -га яңарту. Translate upgrade like update.
en change to (e.g., another format) -> (башка форматка) үзгәртү, үзгәртү:; not -га үзгәртү, not ...итеп үзгәртү
en click on (e.g., link) -> (сылтамага) чирттерү, монда чирттерегез:; not -га чирттерү, not өстенә чирттерү
en connect to (e.g., network) -> (челтәргә) тоташу, Тоташу; not Кая тоташу
en welcome to ... (e.g., program) -> Рәхим итегез: Use a colon instead of periods.
en in the toolbar -> кораллар аслыгында. The locative case is the Tatar equivalent of English in/on/at.
en on the tab -> салынмада/салынмасында. Use the possessive form for particular, named objects, such as on Home tab.
en on the menu -> сайлакта/сайлагында
en on the net -> челтәрдә/челтәрендә
en on the Internet -> Интернетта. Capitalize this word.
en on the Web -> вебта, Интернетта. Do not capitalize веб. Интернет is preferred in some contexts.
en on a web site -> веб-төендә. Spell with a hyphen.
en on a web page -> веб-биттә. Spell with a hyphen.

Pronouns¶

Does not apply to Tatar.

Punctuation¶

Use lowercase after a comma, unless the following word needs capitals.
Commas separate decimals.
Commas separate the place name and the date in letters: Казан, 25 июль 2009 ел
US English uses a period as the decimal separator; Tatar uses a comma. Do not use a space: a space separates the numeral from the abbreviation.
In paper sizes keep the decimal separator and the abbreviation in for inches, because the sizes are US norms. Also show the conversion into IS measurements. Paper sizes are normally expressed in IS units (mm), so use the right conversion.
en 5.25 cm -> 5,25 см
en 5 x 7.2 inches -> 5 x 7,2 дюйм
en Letter Landscape 11 x 8.5 in -> Letter альбомча 11 x 8.5 (27,94 x 21,59 см)
Colon: include a space after it. Do not capitalize the following word, unless it is an enumeration of full sentences.
Use either a period or a colon to separate hours, minutes and seconds (18:30). Prefer the colon.
Semicolon ; is the list separator. If list items are whole sentences, use a period.
Three different dash characters are used in English and in Tatar.
Hyphen (сызыкча): divides words between syllables and links parts of a compound word. No spaces before or after. Never use a hyphen instead of a dash. Example: веб-бит
En dash (сызык): use as a minus sign, usually with spaces before and after. Omit the space when the minus marks a negative number. Example: 1 – 2 = –1
En dash: use in number ranges with no spaces. Example: 10–20 битләрне карагыз.
Em dash: use for dashes wherever technically possible. It separates words in a sentence and has a grammatical function. Never substitute a hyphen.
Ellipses: remove all spaces before the ellipsis sign, even when the source has one.
en Predefined ... -> Алдан билгеләнгән...; not Алдан билгеләнгән ...
en Browse ... -> Күзәтү...; not Күзәтү ...
Some command names appear in the menu followed by an ellipsis to indicate that a dialog window will open. The same convention applies in Tatar.
Period: do not use one in titles or headings.
Do not use a period after IS measurement units (см, кг), unless at the end of a full sentence.
Do not use a period after question or exclamation marks or after an ellipsis.
Include a space after commas and periods.
After a period, always capitalize the following word, unless the period is part of an abbreviation.
When an abbreviation ends a sentence, write only one period.
If bulleted items are complete sentences, end each with a period.
If bulleted items continue an introductory clause, do not use a period.
For items in a list (chapters, sections, products, system requirements) that are neither sentences nor continuations, do not use a period.
If the translation is longer than the US text, or split into several independent sentences, insert a period where it improves Tatar style.
Never put a period after just one word.
The same conventions apply to instruction lists, captions, and callouts.
Quotation mark types: chevrons « », curly “ ”, straight " ", simple ‘ ’. There is no strict rule on which type to use. In documentation normally use chevrons, with curly quotation marks inside: «“Әзер” төймәсе»
In software and on Web pages use straight quotation marks, as in English.
The period stands outside the chevrons.
Do not use single quotation marks, also in software strings.
Do not use angle brackets < > instead of quotation marks.
Parentheses: no space between the parentheses and the text inside, in English and in Tatar. If parentheses enclose part of a sentence, put the period outside the closing bracket; if they enclose a full sentence, put the period inside.
Дәвам итү өчен, «Алга» төймәсенә чирттерегез (продукт ачкычын кертү кирәк булырга мөмкин).
Дәвам итү өчен, «Алга» төймәсенә чирттерегез. (Продукт ачкычын кертү кирәк булырга мөмкин.)

Singular and plural¶

Does not apply to Tatar.

Split infinitive¶

Does not apply to Tatar.

Subjunctive¶

Does not apply to Tatar.

Symbols and non-breaking spaces¶

Does not apply to Tatar.

Syntax¶

Prefer synthetic constructions. They make the sentence shorter and sound more Tatar.
en When file sharing is on, files and printers that you have shared from this computer can be accessed by people on the network -> Файллар уртак кулланылганда, челтәрдәге кулланучылар сез шушы санактан уртак кулланырлык иткән файлларга һәм басакларга керә алачак.
en Change how web pages are displayed in tabs -> Веб-битләрнең салынмаларда күрсәтелү рәвешен үзгәртү.
en This document will not print until the document owner resumes the print job -> Бу документ, хуҗасы биремне дәвам иттермичә, бастырылмыйча торачак.
en Cannot find matching data to delete. -> Бетерерлек мәгълүмат табылмады.
en Microsoft Office Excel did not find anything to print. -> Microsoft Office Excel бастырырлык берни дә тапмады.
For procedural instructions of the type To do this and that, click on ..., rearrange the sentence to mention the action first and then the purpose, because the action matters most to the user. When the purpose matters more, start with the purpose. Action-first structures are not always typical in Tatar, so do not rearrange a sentence if it would sound unnatural.
en To open the shortcut menu, click View Source -> Ярлык сайлагын ачу өчен, “Чыганагын карау” пунктын сайлагыз
en To end the install, click Cancel -> “Баш тарту” төймәсенә басып, урнаштыруны тәмамлагыз
Prefer short constructions.
en Right-to-left writing languages -> Уңнан-сулга язулы телләр; not Уңнан-сулга язуны кулланучы телләр

Verbs¶

English simple forms and gerunds can become verbs, nominalized forms (исем фигыль), or nouns in Tatar. Choose the appropriate Tatar form.
en %d hour(s) %d minute(s) (%d%) remaining -> %d сәгать %d минут (%d%) калды; not %d сәгать %d минут (%d%) саклану
An English verb can be a loan word in Tatar. Such loan words follow Tatar syntactic and morphological rules and usually take the -ла/-лә verb-making affixes.
Block: nominalized блоклау, infinitive блокларга, adjective participle блоклаучы, adverbal participle блоклап, present tense блоклый
English negates with not plus the auxiliary do. Tatar uses a derivative marker.
en Is not supported/installed -> Эшләми/урнаштырылмаган
en could not be opened/found -> Ачып/табып булмый
en You will not be able to -> ...мөмкин булмаячак
en Is not available -> ...мөмкин түгел

Word order¶

The predicate stands at the end of the sentence. This is a strict rule. Avoid word order errors.
en Click Save. -> “Саклау” төймәсенә чирттерегез.; not Чирттерегез “Саклау” төймәсенә.

Audience¶

Take the target audience into account. Translation of learning materials for new users is more direct and friendly; IT Pro materials are more formal.

Style¶

Do not use colloquial, slang, local, poetic or rare words and expressions, or anything outside standard literary language.
English terms are acceptable if they are the industry standard in the country or region. Research current industry standards.
Follow Tatar spelling, grammar, and syntax rules for incorporated English terms. Usually the English word gets phonologized and integrated into the target language.
If no Tatar equivalent exists for an English loan word and you decide to use the English word, check with your translation lead and team members.
Traditionally English words are phonologized as in Russian. A newer trend follows the Tatar language system, because many English sounds exist in Tatar but not in Russian (ә). Prefer transliteration like these: tag -> тәг; flash -> фләш; stack -> стәк
Avoid direct translations with lexical mistakes.
en Open on a new tab -> Яңа салынмада ачу; not Яңа таблицада ачу
en Select media type -> Йөрткеч тибын сайлау; not Медиа тибын сайлау
en Additional characters -> Өстәмә символлар; not Өстәмә характерлар
en Unknown artist -> Билгесез башкаручы; not Билгесез артист

Tone¶

Use a formal tone. In online materials the tone can be more friendly.
Avoid ethnic or racial offensive words. Translating Russian as урыс/русча is offensive; use рус/русча.
Avoid exclamation marks following the English source. In Tatar they read as informal language.
en Welcome to the Data Connection Wizard! -> Мәгълүмати тоташулар остасына рәхим итегез; not Мәгълүмати тоташулар остасына рәхим итегез!

Voice¶

Mimic the tone of the source product, and stay respectful. Avoid word forms specific to a particular dialect.
Address the user with plural respectful verb forms and pronouns. In some cases use passive voice rather than active, even where English uses active.
en You are now connected to the Internet. -> Интернетка тоташу урнаштырылды.
en Reenter the password -> Серсүзне кабат кертегез
Keep the word сез in lower-case. Do not capitalize it.

General considerations¶

Write the localized text as if it were originally written in Tatar. Keep it accurate, correct and clear. Avoid wordiness and word-by-word translation.
Adapt translated text to the local language, customs and localization standards. Use Tatar names rather than English: Edward -> Рәшит; New York -> Яр Чаллы
Translate all English text as a rule. Omit or add text only for a specific reason, and check it with the project team. The translation must reflect product functionality correctly.
Use terminology consistently within one component and across components (software, help, documentation), and in most cases across products. Keep style and register consistent, and translate similar phrases consistently.

Abbreviations¶

Abbreviate UI words (mainly button or option names) only for lack of space or to avoid grammatically wrong structures. Do not abbreviate arbitrarily; use only the commonly accepted abbreviations below.
һәм башкалар -> һ. б.
һәм башка шундыйлар -> һ. б. ш.
сәлам белән -> с/б
галәйһиссәлам -> г. с.
рәсем -> рәс.
Бит -> б.
Use a non-breaking space (CTRL+SHIFT+SPACEBAR) in any abbreviation.
Where non-breaking spaces cannot be used, such as Help files, write these abbreviations without a space, so one letter does not move to the next line.
Never abbreviate мәсәлән, секунд, минут, сәгать.

Acronyms¶

Acronyms are words made from the initial letters of major parts of a compound term. Examples: WYSIWYG (What You See Is What You Get), OLE (Object Linking and Embedding), RAM (Random Access Memory).
In English it is incorrect to add a generic term after an acronym when one of its letters stands for that term. In Tatar this is correct when the acronym is not well known or stands for English words, because the generic term helps the user understand the meaning.
en HTML language -> HTML теле
en TCP/IP-Protocol -> TCP/IP протоколы
en PIN Number -> PIN-код
In online help or documentation, spell out the words of an acronym the first time it appears. Include the language-specific translation, the US term, and the acronym: Мәгълүматка керү объектлары (Data Access Objects, DAO), ActiveX мәгълүмат объектлары (ActiveX Data Objects, ADO)
In the user interface there is usually no space for all three terms. Only in wizards can the acronym be spelled out and localized on first mention. With space constraints or no first occurrence, judge whether to leave the acronym as is or spell it out and localize it.
Do not create a new acronym from the translated term. Do not replace an English acronym with a language-specific acronym. Leave the English acronym or abbreviation intact.
en OLE control containers -> OLE идарә элементлары контейнерлары
en DPI Scaling -> DPI масштаблау
en BIOS settings -> BIOS көйләүләре
Many abbreviations and acronyms are standardized and stay untranslated. Follow one with its full English spelling only if it needs explaining to speakers of a different language. For a common acronym the full form only confuses users, so use the acronym alone.
Do not localize or spell out: ANSI (American National Standards Institute), ISO (International Standards Organization), ISDN, DOS, DSL, CD, DVD
If you are unsure what an acronym stands for, contact the Moderator responsible for this style guide.

Applications, products, and features¶

Application and product names are often trademarked and are rarely translated. Feature names are occasionally trademarked too (IntelliSense™). Verify a name is translatable and not protected before translating it.
Product names that are very localizable, or contain a localizable part, are usually localized.
Treat unlocalized product names and non-translated feature names as proper nouns in Tatar.

Frequent errors¶

Avoid incorrect word-for-word translations. Correct contextual translations for current:
en Current folder -> Кулланылучы папка; not Агымдагы папка
en Current page -> (Хәзер) ачылган бит; not Агымдагы бит
en Current entry -> Гамәлдәге язма; not Агымдагы язма
en Current view -> Гамәлдәге күрсәтелеш; not Агымдагы күрсәтелеш
en Current location -> Хәзерге (гамәлдәге) урын; not Агымдагы урын
size has several meanings. For disc space, such as file size, use күләм: файл күләме. For any relative measurement, use үлчәм: font size -> шрифт үлчәме. Do not mix these meanings.
Usually do not translate please when it marks respect. зинһар marks a request only. Do not overuse зинһар.
en Please wait... -> Көтегез...; not Зинһар, көтегез...
Do not use мәгълүмат (data) in the plural мәгълүматлар: it already has plural meaning.
Do not translate constructions that refer to the user literally word for word.
en Do you want to…? -> ...ргамы/ргәме?; not Сез ... телисезме?
en Do you want to save the changes you made to the Personal Macro Workbook? -> Макросларның шәхси дәфтәренә ясаган үзгәрешләрегезне сакларгамы?; not Сез макросларның шәхси дәфтәренә ясаган үзгәрешләрегезне сакларга телисезме?
en There is a large amount of information on the Clipboard. Do you want to be able to paste this information into another program later? -> Алмашу буферында зур күләмдә мәгълүмат бар. Бу мәгълүматны алга таба башка программаларга өстәп булсын өчен сакларгамы?; not Алмашу буферында зур күләмдә мәгълүмат бар. Бу мәгълүматны алга таба башка программаларга өстәп булсын өчен сакларга телисезме?
en Are you sure you want to… -> Сез ... раслыйсызмы?; not Сез чыннан да ... телисезме?
en Are you sure that you want to set the current chart as the default chart type for creating new charts? -> Сез гамәлдәге диаграмманы яңа диаграммалар төзү өчен килешенгәнчә кулланылучы тип итеп билгеләүне раслыйсызмы?; not Сез чыннан да гамәлдәге диаграмманы яңа диаграммалар төзү өчен килешенгәнчә кулланылучы тип итеп билгеләргә телисезме?
A word preceded by a numeral stays singular. Do not use the plural even where English does: 5 seconds -> 5 секунд
Never add affixes directly to placeholders. It causes non-grammatical constructions at run-time.

Glossaries¶

Find translations of terms and UI elements in approved terminology.

Recurring patterns¶

Does not apply to Tatar.

Standardized translations¶

Standardized topics: the importance of standardization; standard phrases in error messages; checkboxes and radio buttons; dialog box contents and titles; menus, commands, buttons, and other interface text; copyright notice.

Unlocalized items¶

Do not translate English acronyms that have no commonly accepted Tatar translation.
Do not use MS as an abbreviation for a company name, in English or in Tatar.

User interface¶

Always use all available resources to establish the context of a UI item. Ask your Engineering Partner if you need more context for a string.

Checkboxes and radio buttons¶

Translate checkbox items in nominalized form (исем фигыль). In the negative, use an infinitive.
en Enable reminder -> Искә төшерүчене кабызу
en Don't show me this dialog again. -> Бу диалогны бүтән күрсәтмәскә.
A selected checkbox is тамгаланган or сайланган. A deselected one is тамганы алу.
Do not capitalize checkbox items that form a list. Capitalize them when they do not form a list.
As a general rule, text in checkboxes and radio buttons takes no period at the end. Keep the period if the source has one and the string is a complete sentence. A period is also advised if the target string is a complete and complex or long sentence.
en I accept the license terms. -> Лицензия шартларын кабул итәм.
en I accept this agreement. -> Бу килешүне кабул итәм.
en Confirm file format conversion on open -> Ачканда файл форматын үзгәртүне раслату

Dialog box contents and titles¶

Use consistent terminology and language style in all dialog boxes, consistent with translations in other localized applications. Applications not yet localized may be localized later and will reuse these translations.
Keep dialog box titles consistent with the menu items or commands that call them. Menus are nominalized verbs (исем фигыль), so dialog titles are nominalized verbs too. The source text format is decisive: if the source uses a headline format (Doing xyz), use the Tatar equivalent, nominalized form or present tense depending on context.
en Insert Table -> Таблица өстәү
Use parallel language for dialog box elements that are parallel in function, such as the contents of lists and tables. Make all items similar in form and the same part of speech: all infinitive verbs, or all nominalized verbs, or all imperative verbs.
Use the imperative mood only for evident address to the user, such as instruction text in dialog boxes.
en Select a data file in the list, then click Settings for more details. -> Исемлектән мәгълүмат файлын сайлап алыгыз да, “Параметрлар”ны ачып, өстәмә үзлекләрне карагыз

Menus, commands, buttons, and other interface text¶

Translate a verb as a verb unless there is a good reason not to. Establish whether a word is a noun or a verb from context. Some English words are both, such as View.
en Archive [noun] -> Архив
en Set [verb] Query [noun] -> Таләп урнаштыру
en View [verb] -> Күзәтү
Translate command and button names as nominalized verbs: Save -> Саклау. Avoid the infinitive -ырга/-ергә/-рга/-ргә. If the source command or button is a negative verb, translate it as an infinitive: Don't Save -> Сакламаска
Translate command names consistently across all localized products. The same US term gets the same translation everywhere.
Name buttons in instruction text with phrases like “Әйе” төймәсе, “Баш тарту” төймәсе. In some cases drop төймәсе and use the button name alone: “Юк” төймәсенә яки 'Әйе'гә басыгыз., Дәвам итү өчен “Әйе” төймәсенә, ә чыгу өчен “Баш тарту”га басыгыз.
Never use “Юк” without төймәсе: “Юк”ка басыгыз is stylistically incorrect. Avoid such constructions.

Tool tips and InfoTips¶

A tool tip is a short description of the icon or function the user hovers over. It shows for a short time.
Keep tool tips short, concise and helpful. Many have the same linguistic form as menus, commands, or buttons, in an impersonal style without a period. Others are short explanations addressing the user directly.
Translate tool tip text consistently and with usability in mind. Do not use multiple different translations for the same tool tip.
en Insert Microsoft Excel Worksheet -> Microsoft Excel битен өстәү
en Click here to begin -> Башлау өчен монда чирттерегез
en No feeds detected on this page (Alt+J)\nFeeds provide updated website content -> Бу биттә каналлар табылмады (Alt+J)\nКаналлар аша яңартылган веб-төен эчтәлеге җиткерелә
InfoTips appear briefly and explain a specific part of an interface. They contain short sentences or sentence fragments describing what an item does or how to use it.
For items describing what the user can do, use nominalized form (исем фигыль). This is the most common type of InfoTip. Use the non-personal form even if the English uses a personal form.
en Analyze items with a spreadsheet application -> Элементларны электрон таблица кушымтасы ярдәмендә анализлау
For items with an automatic action on opening, use nominalized form as a rule, or sometimes present tense in the third person.
en Opens the calendar -> Календарьны ачу / Календарьны ача

Status messages¶

A status bar message is informational, about the active document, a selected command, or an active or selected interface item. It shows in the status bar at the bottom of the window and refers to actions being performed or already complete.
Edit (menu): Төзәтү; en Contains editing commands -> Төзәтү командалары
Copy to Folder... (menu): Папкага күчермәләү…; en Copies the selected items to a new location -> Тамгаланган элементларны яңа урынга күчермәләү
New (command): Яңа; en Creates a new document -> Яңа документ төзү
en Make object visible -> Объектны күрсәтү
en Word is converting the document. Press Esc to stop. -> Документ үзгәртелә. Туктату өчен ESC төймәсенә басыгыз.
en Datasheet View -> Таблица режимы
en Done -> Тәмам
Messages reporting a running process use an -ing verb plus three dots. In Tatar choose a verb tense or aspect that expresses the ongoing action. The typical form is present tense and passive voice (хәзерге заман, төшем юнәлеше).
Apply the standard syntax to status bar messages wherever possible, even when the US text does not keep the convention.
en Scanning files... -> Файллар тикшерелә...
en Opening message… -> Хәбәр ачыла...
Use one standard translation where the source phrases the same meaning differently.
en Press F1 to get Help, If you want Help press F1, To get Help press F1 -> Ярдәм өчен F1 төймәсенә басыгыз
en Not enough memory, Insufficient memory, There is not enough memory -> Хәтер җитми
en Save changes to %1?, Do you want to save changes to %1? -> %1 өчен үзгәрешләрне сакларгамы?

Error messages¶

Error messages inform the user of an error that must be corrected for the program to keep running. They can prompt an action or state that a reboot is required.
Use consistent terminology and language style. Do not just translate as in the source.
Many English error messages vary in the use of articles and demonstrative and possessive pronouns. Handle such variation consistently in Tatar.
en File already exists, The file already exists, This file already exists -> Мондый файл бар инде. In complete sentences use determiners consistently even if the source does not.
en Not enough memory to complete this operation. -> Гамәлне тәмамлау өчен хәтер җитми. No need for a demonstrative construction unless context requires it.
en Windows Vista cannot start your system. If the problem persists, contact your network administrator. -> Windows Vista системаны эшләтеп җибәрә алмый. Проблема хәл ителмәсә, челтәр администраторына мөрәҗәгать итегез.. Avoid the possessive marker your unless ownership matters in context.
en Access was denied., Access denied. -> Керү тыелган; not Керү тыела. In complete sentences use verbs and the same tense as the source string.
en The file '%s' is an unknown graphics format. -> '%s' файлы билгесез график форматка ия.. Rephrase is with have where needed.
en The application may attempt to convert the graphic. -> Кушымта графиканы конвертлау омтылышы ясарга мөмкин. may + verb can be rephrased as verb + possibly.
en A problem occurred while trying to connect to the network share '%1!s!'. -> '%1!s!' уртак челтәр ресурсына тоташканда проблема чыкты.. Shorten and rephrase to A problem occurred while connecting to the network share '%1!s!'.
en The following error occurred: '%1!s!' (error #%2!lx!) -> Хата: '%1!s!' (хата #%2!lx!). Shorten to Error: '%1!s!' (error #%2!lx!).
en An unknown error has occurred./ No error occurred. -> Билгесез хата./ Хата юк.. Shorten to Unknown error. / No error.
Standardize standard phrases. The US sometimes uses different forms for the same thing.
en Cannot …, Could not … (File could not be found, File cannot be found) -> Файл табылмады
en Failed to …, Failure of … (Failed to connect, Failure to connect) -> Тоташып булмады
en Cannot find …, Could not find …, Unable to find …, Unable to locate … (Cannot find driver software, Could not find driver software, Unable to find driver software, Unable to locate driver software) -> Драйвер програм тәэминаты табылмады
en Not enough memory, Insufficient memory, There is not enough memory, There is not enough memory available -> Хәтер җитми
en ... is not available, ... is unavailable (The command is not available, The command is unavailable) -> Команданы башкару мөмкин түгел
Find out what replaces a placeholder before translating, so the sentence stays grammatical.
%d, %ld, %u, %lu show a number, such as 3 or 512.
%c shows a letter, such as f or s.
%s shows a string, such as Click here to continue.
“Checking Web %1!d! of %2!d!” shows “Checking Web <number> of <number>”.
“INI file "%1!-.200s!" section” shows “INI file "<string>" section”.
Tatar nouns outside the nominative often take affixes that differ with the vowels in the root, so the exact replacement string matters. Reword the translation as an analytic construction without affixes to avoid an ungrammatical sentence.
Avoid common words such as object (объект) after a placeholder: the text shown to the user may not be an object.
en Replace invalid %s? (user sees Replace invalid data?, Replace invalid file?) -> Ялгыш %s алмаштырылсынмы?; not Ялгыш %s-ны алмаштырыргамы?
en %s already exists (user sees File already exists, Name already exists) -> %s бар инде; not %s объекты бар инде
en %s is now set as your personal contact. (user sees Regina is now set as your personal contact, Mr. Kim is now set as your personal contact) -> %s шәхси контактыгыз буларак урнаштырылган.; not %s объекты шәхси контактыгыз буларак урнаштырылган.
en %s stopped working and was closed (user sees The application stopped working and was closed, The program stopped working and was closed) -> %s эштән туктап, ябылган булган; not %s-ның эше тукталылган һәм ул ябылган булган
en Replace existing definition of '|'? -> '|' өчен билгеләмәне алмаштырыргамы?; not '|'-ның билгеләмәсен алмаштырыргамы?. Rephrase as an analytic construction without affixes.
en Rename file %1 to %2 -> %1 файлының исемен %2 итеп үзгәртү; not %1 файлының исемен %2-гә үзгәртү
en Cannot save '|' because the volume is locked. -> Том бикләнгән булганга, '|' саклана алмый.; not Том бикләнгән булганга, '|'-ны саклап булмый.. Personified subjects are not recommended, but you can put the placeholder in nominative case if no other rephrasing works.
en Redefine '|' based on selection? -> Тамгалауга нигезләнеп, '|' башкача билгеләнсенме?; not Тамгалауга нигезләнеп, '|'-ны башкача билгеләргәме?. Use passive voice of the verb and nominative case of the placeholder.
en Microsoft Office Excel cannot find '|0' on '|1'. -> Microsoft Office Excel тарафыннан '|1' эчендә '|0' табылмады.; not Microsoft Office Excel '|1'-да '|0'-ны таба алмады.. Analytic construction and passive voice.
en Cannot access '|'. The file may be in use. -> '|' файлына кереп булмый. Ул инде кулланылышта булырга мөмкин.; not '|'-га кереп булмый. Файл инде кулланылышта булырга мөмкин.. The placeholder in the first sentence is determined in the second. To avoid the affix, move the determiner to the first Tatar sentence.
en Cannot access '|' -> '|': керү мөмкинлеге юк.; not '|'-га кереп булмый.. Use such colon constructions when nothing else works.
en from %1 to %2 -> %1 - %2; not %1-дан %2-га кадәр. This is the way to represent a range with placeholders.

Keys¶

The keyboard is the primary input device for text input. Most actions can be performed with the keyboard.
In English, references to key names like arrow keys, function keys and numeric keys appear in normal text, not in small caps. In Tatar capitalize all such references. Always use the descriptor төймәсе when referring to a key.
ESC төймәсенә басыгыз; not ESC’ка басыгыз
Translate only the key names below. Do not localize any other key name.
en Space bar -> БУШ АРА төймәсе
en Up -> ӨСКӘ УК төймәсе
en Down -> АСКА УК төймәсе
en Left -> СУЛГА УК төймәсе
en Right -> УҢГА УК төймәсе

Access keys and hot keys¶

Access keys are the underlined or highlighted letters in menu options, commands or dialog boxes that run commands and perform tasks faster.
Slim characters (I, l, t, r, f) as hot keys: n/a. There are no slim characters in the Tatar alphabet.
Characters with downstrokes (g, j, y, p, q) as hot keys: yes. The hotkey underline can be hard to see for these characters.
Extended characters as hot keys: n/a. There are no extended characters in the Tatar alphabet.
An additional letter in brackets after the item name as hot key: yes.
A number in brackets after the item name as hot key: yes.
A punctuation sign in brackets after the item name as hot key: yes.
Duplicate hot keys when no other character is available: no.
No hot key assigned when no more characters are available (minor options only): yes.
Never use ё, ж, ц, щ, ъ, ь as hot keys. These characters are not in the Tatar keyboard layout because they are rare in Tatar texts. Users can type them with the ALT key: ALT+һ=ё, ALT+ ң=ж, ALT+ө=ц, ALT+ә=щ, ALT+ү=ъ, ALT+җ=ь
Preferred hot key characters, case-sensitive false: А, Ә, Б, В, Г, Е, З, И, Й, К, Л, М, Н, О, Ө, П, С, Т, Х, Һ, Ч, Ш, Ы, Э, Ю, Я
Preferred hot key characters, case-sensitive true: Р, У, Ү, Ф
Allowed hot key characters, case-sensitive false: Д, Җ, Ң
Allowed hot key characters, case-sensitive true: Р, У, Ү, Ф
Not allowed as hot keys, case-sensitive false: Ё, Ж, Ц, Щ, Ъ, Ь
Numeric hot key characters, case-sensitive n/a: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

Arrow key names¶

Localize and capitalize all arrow key names.

Shortcut notation¶

Use төймәләренә басыгыз when instructing the reader to press shortcut keys, rather than төймәләр кушылмасына басыгыз. Separate simultaneous key names with a plus sign and no spaces.

Titles¶

English chapter titles usually begin with How to …, Working with … or Using …. Tatar uses various constructions, often a nominalized verb form (исем фигыль).
en How to create … -> … төзү тәртибе
en Working with … -> … белән эшләү
en Using … -> … кулланышы

Copyright¶

Keep copyright text consistent within the product and across Tatar versions.
en Copyright -> Авторлык хокукы