Abbreviations

1. Introduction

1.1. What do we mean by abbreviations?


Abbreviations are an essential part of all languages. Although we tend to avoid using them in interfaces to ensure content is fully understandable in an international context, we sometimes use them due to character limits imposed by certain components. Of course, such usage does not mean leaving our users in confusion. Our core principle is to use abbreviations that are widely known, understood, tested with target users, and that facilitate comprehension during scanning.

1.2. Abbreviations projection in Horizon


We can generally divide them into two:

1.2.1 Abbreviations everyone thinks they know

Just writing an abbreviation might cause confusion for users because it’s not always what they think it is. On top of that, abbreviations can make the average user work a little harder to understand what’s being said. Even with all this, if something is super well-known as an abbreviation and you use it all the time in everyday speaking, then that might be okay. But, like any assumption, this one can easily be wrong. 

No matter what the topic is, test out your content. Things might not be as clear as you think. Here’s another thing to remember especially that we mostly use abbreviations to save space. We recommend you avoid using them in a paragraph, especially.

1.2.2 Abbreviations in aviation terminology 

Obviously, these are more technical and people who already know them will understand them right away. You’ll see these a lot in interfaces designed for businesses talking to other businesses (B2B). Don’t use these kinds of abbreviations in interfaces meant for regular people (B2C).

2. Usage

2.1. Amounts


Use “m” for millions, “bn” for billions, and “k” for thousands in limited spaces. Generally, do not abbreviate amounts in the hundreds to avoid confusion.

Consult with the local UX writer for appropriate abbreviations in other languages.

2.2. Addresses


Use “St.” for Street, “Ave.” for Avenue, “Bldg.” for Building, “Rd.” for Road, “Blvd.” for Boulevard, “Apt.” for Apartment, and “Ste.” for Suite in limited spaces.

Consult with the local UX writer for appropriate abbreviations in other languages.

2.3. Countries


Do not use country abbreviations in sentences unless they are from countries known by their abbreviations.

Use recognized abbreviations like “UK” and “USA” directly in text without needing to spell out the full country name.

2.4. Measurements and Dimensions


Always include a space between the number and the unit of measure, and use open punctuation (no periods). If the number and unit are used as an adjective, connect them with a hyphen.

Use the metric system for Australia, Brazil, Canada, France, and the UK.

In the USA, use the imperial system, providing metric equivalents in parentheses when appropriate.

2.4.1. Length

• Metric: meter (m), centimeter (cm), millimeter (mm)
• Imperial: foot (ft), inch (in)

2.4.2. Weight

• Metric: kilogram (kg), gram (g)
• Imperial: pound (lb), ounce (oz)

2.4.3. Volume

• Metric: liter (L), milliliter (mL)
• Imperial: gallon (gal), fluid ounce (fl oz)

2.4.4.

Please check the AP Style handbook for others.

2.5. Documents


Use the abbreviation directly when it is widely recognized and understood by your audience.

Avoid unnecessary capitalization if the abbreviation is used in the middle of a sentence; however, keep it capitalized if it starts a sentence.

In formal writing or when first introducing the abbreviation, you may want to include the full name followed by the abbreviation in parentheses.

2.6. Months and Days


When abbreviating days and months, take the first three letters.

Avoid using shortened forms of months and days in full sentences. Always spell them out to maintain clarity.

Abbreviated versions may be used in specific contexts such as forms, calendars, or when displaying dates.

Consult with the local UX writer for appropriate abbreviations in other languages.

2.7. Time


In plain text, use “hr,” “min,” and “sec” as recommended by AP Style.

In situations with limited space, single-letter abbreviations are acceptable without spacing:

1. h for hour
2. m for minute
3. s for second

Avoid using shortened forms in full sentences; use the full words for clarity when possible.

2.8. Latin Phrases


Latin abbreviations can be useful in specific contexts particularly in formal documentation, legal texts, or technical specifications.

While Latin abbreviations can provide clarity and precision, their usage should be approached with caution to ensure inclusivity. To maintain inclusivity:

2.8.1. Use sparingly

Limit the use of Latin abbreviations to contexts where they add significant value and clarity.

2.8.2. Provide explanations

If using Latin abbreviations, consider defining them at first use to ensure understanding.

2.8.3. Opt for clarity

Whenever possible, use plain language that is accessible to all users.

2.9. Addressing Titles


In Turkish Airlines we use two types of title abbreviations:


2.9.1. Gender Titles

To identify the user’s gender, we include abbreviations such as “Mr.” and “Ms.” These are typically displayed on ticketing screens and profile pages.

2.9.2. Academic Titles

Users can also add academic titles such as “Prof.” (Professor), “Assist. Prof.” (Assistant Professor), “Dr.” (Doctor), “Doc.” (Doctor), etc. These titles are used as abbreviations before the name, followed by a period.

2.10. Aviation Terms


Please avoid using these abbreviations when communicating regular users. Only adapt them if prepare a technical document.

1. ATC: Air Traffic Control
2. AOC: Air Operator Certificate
3. FAA: Federal Aviation Administration
4. FBO: Fixed Base Operator
5. ICAO: International Civil Aviation Organization
6. IATA: International Air Transport Association
7. VFR: Visual Flight Rules
8. IFR: Instrument Flight Rules
9. TSA: Transportation Security Administration
10. NAV: Navigation
11. CRM: Crew Resource Management
12. DME: Distance Measuring Equipment
13. A320: Airbus A320 (specific aircraft model)
14. B737: Boeing 737 (specific aircraft model)
15. PAX: Passengers
16. AOG: Aircraft on Ground

2.11. Frequently Asked Questions

The abbreviation “FAQ” is widely recognized by our users. Therefore, in navigation menus, we use the abbreviation form. However, when it appears as a heading under a specific topic, it should be written out in full.

To sum up, use the full phrase “Frequently asked questions” when it serves as a page heading, but use the abbreviation “FAQ” in navigational links leading to that page.