Huawei Hebrew UI Style Guide for Terminal Products V5g11n.rnd.huawei.com/UIDoc/WebContent-2/Consumer/EMUI/WebContent-3... · Huawei Hebrew UI Style Guide for Terminal Products V5.0

Huawei Hebrew UI Style Guide for Terminal

Products V5.0

Prepared by Yang Ping and Xiao Li Date 2014-11-26

Reviewed by Li Xiaochun, LiuYanjun,

Wu Lei, Hua Wan Date 2015-03-04

Approved by Date

Huawei Technologies Co., Ltd.

All rights reserved.

Huawei Hebrew UI Style Guide for Terminal Products V5.0 Revision History

Issue 5.0 (2017-05-03) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

Revision History

Date Version Description Author

2011-11-9 V1.0 First release Liu Yanjun, Liu

Yu, Yang Ping,

and Hu Aihua

2013-03-18 V2.0 New UI elements added based on

Android 4.0 and Huawei Emotion UI.

Yang Ping and

Xiao Li

2014-11-26 V3.0 Updated based on EMUI 3.0. Yang Ping and

Xiao Li

2016-7-18 V4.0 Updated based on EMUI 5.0 James Brennan

2017-02-08 V5.0 Updated based on EMUI 6.0. Joong Woo Jae

Huawei Hebrew UI Style Guide for Terminal Products V5.0 Contents



ii

Contents

1 Principal Guidelines ..................................................................................................................... 1

1.1 Accuracy ....................................................................................................................................................................... 1

1.2 Conciseness .................................................................................................................................................................. 3

1.3 Consistency ................................................................................................................................................................... 6

1.4 Cohesion ....................................................................................................................................................................... 9

1.5 Friendliness ................................................................................................................................................................. 10

1.6 Translatability ............................................................................................................................................................. 12

2 UI elements................................................................................................................................... 13

2.1 UI element types ......................................................................................................................................................... 13

2.2 UI element descriptions .............................................................................................................................................. 14

2.2.1 Title .......................................................................................................................................................................... 14

2.2.2 Tab & Content filter ................................................................................................................................................. 16

2.2.3 App name ................................................................................................................................................................. 17

2.2.4 Feature name ............................................................................................................................................................ 18

2.2.5 Menu item ................................................................................................................................................................ 19

2.2.6 Button ...................................................................................................................................................................... 21

2.2.7 Message ................................................................................................................................................................... 24

2.2.8 Check box ................................................................................................................................................................ 27

2.2.9 Entry ........................................................................................................................................................................ 28

2.2.10 Secondary text ....................................................................................................................................................... 29

2.2.11 Spinner ................................................................................................................................................................... 31

2.2.12 Time line ................................................................................................................................................................ 32

2.2.13 List ......................................................................................................................................................................... 33

2.2.14 Switch .................................................................................................................................................................... 34

2.2.15 Text box ................................................................................................................................................................. 35

2.2.16 Slider ...................................................................................................................................................................... 36

2.2.17 Peek notifications ................................................................................................................................................... 37

2.2.18 Toolbar ................................................................................................................................................................... 37

2.2.19 Functional alerts ..................................................................................................................................................... 38

2.2.20 Help guide – announcements ................................................................................................................................. 39

2.2.21 Help guide – full screen ......................................................................................................................................... 40

2.2.22 Progress bar ........................................................................................................................................................... 41

Huawei Hebrew UI Style Guide for Terminal Products V5.0 Contents



iii

2.2.23 Drawer ................................................................................................................................................................... 42

2.2.24 In-app notification ................................................................................................................................................. 43

2.2.25 Chips ...................................................................................................................................................................... 44

2.2.26 Grid ........................................................................................................................................................................ 45

2.2.27 Bottom sheet .......................................................................................................................................................... 46

2.2.28 Badges ................................................................................................................................................................... 46

Huawei Hebrew UI Style Guide for Terminal Products V5.0 ‎1 Principal Guidelines



1

1 Principal Guidelines

Audience

Ideally, UI elements should be invisible to the user. They should not notice that any word or

phrase is out of the ordinary. If the user takes notice of UI, more than likely, they are noticing

because something strikes them as wrong or unprofessional. Therefore, UI language should be

neutral, tending towards positive and friendly.

Scope

This document applies to terminal products with screens. For user interface (UI) requirements

for PC software such as HiSuite (for handsets) and Mobile Partner (for data cards), refer to

Huawei GUI Style Guide.

Introduction

Smartphones, tablets, and other devices have more or less become daily household items over

the past decade or so. The user interface of a device is the primary interactive space that users

use to communicate with their device. With billions of devices, every UI string has the

potential to be replicated countless times and read by countless individuals. We must ensure

that UI elements on all Huawei devices are reasonably designed, written, organized, and

presented to help users understand and interact with the content they see.

This section covers the five principle guidelines for achieving seamless, user-friendly UI.

They are: accuracy, conciseness, consistency, cohesion, and friendliness.

1.1 Accuracy

Accuracy is the basic requirement for UI languages. To meet this requirement:

1. Use correct and clear expressions for UI elements, such as menus, buttons, and field

labels.

2. Ensure that the language of the string corresponds to the actual action it performs.

3. Ensure that the UI information, including functional description, operation guide, key

information, proper nouns, commonly used terms, country and area names, time zones,

values, symbols, and numbers, are correct and clear.

4. Eliminate any incorrect spelling and ambiguous words.




2

5. Minimize "literal" (direct) translations. The translation of an original Chinese string does

not necessarily have to match the original string word for word. Strings translation

should take into account the purpose of the feature, app, or interface.

6. In Chinese, there is no distinction between singular and plural quantities in terms of the

object (noun). In English and many other languages, such a distinction exists and must

be factored in.

Example:

In Chinese, the message "您有%1$s 位联系人。" is valid for every quantity that %1$s

may be. In English, the message should be split into two different strings. All numerical

quantities other than 1 (0, 2, 3, 4, and so on) require the message to be displayed as "You

have %1$s contacts." For the numerical quantity of 1, the string needs to be displayed as

"You have %1$s contact." Usually, when the string needs to be translated to 40 or more

languages, six strings are required with one "You have %1$s contact." and five "You

have %1$s contacts."

7. Make sure basic formatting issues are minimized. Make sure there are no extra spaces at

the end of strings or after a colon.

Example:

Incorrect:

In the case shown, there is no space after the colon. This particular string should be displayed as "Size:

63.8KB". Sometimes, "Size:" and "63.8KB" are two separate strings, which causes this issue. In this

case, we need to use a placeholder and change "Size:" to "Size: %d". The values in the placeholder can

be any value.




3

1.2 Conciseness

Because of the screen size limit, UI language style on terminals with screens should be

concise. Oftentimes, expressions that appear brief in Chinese require lengthy translations in

English and other languages. So please be mindful of this fact while designing interfaces.

1. Express a message concisely.

Examples:

Would you like to delete the message now? (Not recommended)

?האם ברצונך למחוק את ההודעה כעת

Delete message? (Recommended, especially for feature phones)

?למחוק את ההודעה

2. Extract repeated content from same-level options.

Examples:

Correct:

In the case shown, "as" is extracted from the second-level menu options. The menu option in the first

figure is "Set as" rather than "Set", and the second-level menu options are "Contact photo" and "Home

screen", rather than "As contact photo" and "As home screen".




4

3. Extract repeated content from options and add it to the title if possible.

Examples:

Correct:

Do not write the menu options as follows: "Open from recent", "Open from downloads"...

4. Use verbs or verb phrases for the buttons and options used to perform operations.

5. For longer descriptions, consider using point form notation




5

Example:

Smart screenshot offers additional ways for you to take screenshots or video clips.

− Take a screenshot: Knock twice firmly with your knuckle.

− Draw an enclosed region with your knuckle: Capture part of the screen.

− Knock twice firmly with two knuckles: Start or stop recording a video clip of your

onscreen actions.

− Knock firmly with you knuckle and draw an S: Take a scrolling screenshot.

6. Avoid wordy, literal translations if there is a shorter and more direct alternative that will

achieve the same meaning. Even if the English fits, you must consider other languages

(e.g. Russian, Arabic, German) that tend to be longer and wordier than English.




6

Examples:

Incorrect:

Correct: The Chinese source here is "按城市查询" and "按邮编查询". While the

English makes sense (literal) and fits the context, it can be simplified so users can

understand the strings better. Here, users would only need to know the main point of

both strings, which asks them how they would like to view the available list of service

centers, either by area code or city. Revising the strings to "By area code" and "By city"

would work far better.

1.3 Consistency

Consistency is an important requirement that can invisibly improve user experience. By

remaining consistent, we can develop a "voice" for our UI. To meet this requirement:

1. Ensure that the UI style for products of the same type is consistent. For example, the

language style for all Android smartphones' UIs must be the same.

2. Use the same expressions to describe the same UI elements throughout the UI. For

example, the names and descriptions of the same buttons or applications must be the

same for the same product.

3. Use the same expressions or sentence patterns in similar UI messages. For example, the

expressions or sentence patterns for the error messages "insufficient system memory"

should be the same. Users should not see "system memory insufficient" in one place and

"not enough memory" in another. The expressions or sentence patterns for the messages

displayed after users have deleted an item should be the same every time.




7

Examples:

No. For a Delete Operation For a Save Operation

1 Contact deleted. / איש הקשר נמחק. Photo saved. / התמונה נשמרה.

2 Deleted. / נמחק. Saved. / נשמר.

3 Done. / בוצע. Done. / בוצע.

The above table contains examples of the possible messages that may be displayed after a Delete or Save

operation.

Within an individual product UI, use the same expressions or sentence patterns for the same operations

and message types. As shown in the preceding table, if the message displayed after a contact is deleted is

"Contact deleted" (noun + past tense verb) the message displayed after an image is saved must be

"Image saved" (noun + past tense verb).

4. Ensure that the style applied to all the options of the same parameter or configuration

item is consistent. For example, all the options below are nouns.

Example:

Correct:

As shown in the preceding example, all the options on the All tab are noun phrases, such as Bluetooth,

Display, and Sound.




8

5. Use the same expressions or sentence patterns to describe the current status. For example,

use the "noun + complement" structure, such as "File copied" and "Password incorrect",

to describe the current status.

6. Ensure that the style for messages of the same type (for example, alerts, confirmation,

alarms, and notifications) is consistent. For example, expressions and sentence patterns

of all the messages in the dialog box displayed when users attempt to perform a Delete

operation must be the same.

Examples:

While both the following sentences are correct when used to ask users whether they want

to delete all contacts, within a single product's UI, only one of them can be used.

Furthermore, whichever of the sentence forms is used should be applied to all similar UI

messages.

− Delete all contacts?

− Are you sure you want to delete all contacts?

7. Ensure that punctuations are used consistently throughout a UI. For details, see

Chapter ‎2 "UI elements."

8. Ensure that style remains consistent for longer strings and descriptions of the same type.

Example 1: Description of UI feature

These two descriptions should be similar in style as both of them are describing features

of the EMUI. However, if we are to use the description of Eye comfort as a model, there

are some stylistic differences in the description for Smart headset control.




9

We can perform a short analysis on these descriptions using two binaries: Descriptive

language and active language; conditional tense and indicative tense. From the example

of Eye comfort, using active language and indicative tense is best for these descriptions.

Following this analysis, we can improve the description of Smart headset as such:

(ORIGINAL: Descriptive language & conditional tense) If Smart headset control is turned on, more functions are available when songs are playing using Music. For

example, you can add a song to your favorites, and download or share a song using the headset control.

vs

(IMPROVED: Action language & imperative tense) Smart headset control allows you to

use more functions when songs are playing using Music. You can add a song to your

favorites, and download or share a song using the headset control.

9. Ensure that all units, for example, KB, MB, and bpm, are used consistently throughout a

UI.

The consistency requirement is posed not only for UI language, but also for UI layouts and operations.

In addition to the expressions and sentence patterns used on UIs, the control use, UI colors, and UI

layouts must also be consistent. The advantages of meeting the consistency requirement are as follows:

Users can easily build a mental model and understand the information provided on our products' UIs.

Once they have become familiar with a UI, they can easily switch to other similar UIs and predict

various functions available on these UIs.

Consistent user experience makes users feel comfortable when they use our products, which helps to

improve users' support for and loyalty to our products and brands.

UI consistency helps to reduce users' difficulty in first understanding and using our products.

1.4 Cohesion

The correlative menu elements, such as a main menu and its sub menus, or a stem sentence

and its item lists, should cohere to an internal logic. In other words, UI should invisibly teach

the user what to expect from each action. By doing this, they can form a phrase or sentence

correctly and for users to read easily. To meet this requirement:

1. Ensure the main menu and its sub menus, or a stem sentence and its item lists form a

phrase or sentence correctly.

2. Extract the repeated content from the sub menus to the main menu, or from the listed

items to its stem sentence.

Examples:




10

Correct:

In the case shown, "The device from which you want to import contacts" is the stem sentence and the

list contains "Supports Bluetooth" and "Does not support Bluetooth". By writing like this, the stem

sentence and listed items can form correct sentences, that is "The device from which you want to import

contacts supports Bluetooth" and "The device from which you want to import contacts does not support

Bluetooth".

1.5 Friendliness

Friendliness makes the users feel like they are taken care of, and being spoken to by a friend.

To determine if a phrase or string is friendly, put yourself in the user's place and consider how

you might feel if you saw each string appear on your device. Avoid UI language that is too

complex, technical, convoluted, imperative, demanding, threatening, accusatory, or indeed,

too casual.

To meet this requirement:

1. Do not use overly technical terms. Use sentences and expressions that users can easily

understand.

Example:

The PA is too hot. (Incorrect)

.חם מדי PA-ה

The phone is too hot. (Correct)

.הטלפון חם מדי




11

"PA" is a short for power amplifier. The PA is a critical electronic component in the phone's electronic

circuitry. For ordinary users PA has little meaning and could be confusing

2. Do not use words or expressions that users may be uncomfortable with (i.e. words with

political, racial, religious, or sexual connotations).

3. When providing help or tips to users to aid their use of the device, break the information

down into easily digestible paragraphs or steps.

Example:

4. Do not use non-standard acronyms and abbreviations, such as "Ip" and "Wlan".

5. Ensure that error messages are easy to understand. Do not use system codes or

system-returned values. In addition, clearly identify problems and provide possible

solutions.

6. Avoid using sentences or expressions that may cause users to feel they are blamed,

threatened, or obliged to do something. Avoid using "should" or "must" in sentences

when possible (e.g. "You must update your phone now" vs. "Please update your phone").

7. Do not use brackets in messages to provide supplementary information because doing so

may interrupt users' train of thought. Start a new sentence to give supplementary

information.

8. Ensure that warnings are obvious in both language and symbols used to remind users of

the possible results and losses that may be caused if they perform operations such as

deleting data, formatting a disk drive, or incorrectly powering off a device. Explain the

possible impacts of the operations first and then ask users whether they want to continue.

9. Do not design functions that are overly complex or confusing to use. A big part of user

friendliness is how easy and straightforward a complex function is simplified to.




12

1.6 Translatability

English is the apex language for UI at Huawei, meaning that English strings will be translated

into up to 64 other languages. Although it is impossible to create English strings with

meanings that are 100% clear in all 64 languages, best practice is to keep in mind that Russian,

Arabic, or Hindi translators may not understand some of the more idiomatic or culturally

specific terms or phrases used in English. To meet this requirement:

1. Edit strings so that meaning is conveyed more directly. For example:

"Only when charging" is clearer than "Only when plugged in"

2. Avoid idioms or slang in translation and edits.

3. If you foresee a translation issue, include an explanatory note in the comments for the

other translators that explains the context/scenario.

Example:

Huawei Hebrew UI Style Guide for Terminal Products V5.0 ‎2 UI elements



13

2 UI elements

2.1 UI element types

UIs may include elements of the following types:

Title / כותרת

Tab & Content filter / לשונית ומסנן תוכן

App name / שם אפליקציה

Feature name / שם תכונה

Menu item / פריט תפריט

Button / לחצן

Message / הודעה

Check box / תיבת סימון

Entry / ערך

Secondary text / טקסט משני

Spinner / מסחרר

Time line / קו זמן

List / רשימה

Switch / מתג

Text box / תיבת טקסט

Slider / מחוון

Peek notifications / הודעות זמן שיא

Toolbar / סרגל כלים

Functional alerts / התראות פונקציונליות

Help guide – announcements / הודעות –מדריך עזרה

Help guide – full screen / מסך מלא –מדריך עזרה

Progress bar / סרגל התקדמות

Drawer / מגירה

In-app notification / הודעות באפליקציה




14

2.2 UI element descriptions

This section describes examples of each UI element.

2.2.1 Title

Figure 2-1 Screen title Figure 2-2 Dialog box title




15

Figure 2-3 Section dividers

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern For task-oriented titles, use "Verb" or "Verb + Noun."

For non-task-oriented titles, use nominal phrases.

Examples Share (task-oriented title) / שיתוף

My music / המוסיקה שלי

Tips Function descriptions within titled screens do not need to

repeat the title again. For example:

Under Device, there is no need to say "Device home screen

style, Device display, Device sound"




16

2.2.2 Tab & Content filter

Figure 2-4 Tabs Figure 2-5 Content filter

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern One word. Two if absolutely necessary

Examples General / כללי

All / הכל

Songs / שירים

Me / אני

Tips Keep it short and concise

When editing UI for strings under each tab/content filter,

think about the user's experience thus far – i.e. what have

they navigated through to get where they are.




17

2.2.3 App name

App names should meet the following requirements:

Avoid any negative implications in local culture

Conciseness - the shorter, the better

Consistency - apply the same conventions in regards to length and structure

If possible, name should describe the function comprehensively

Two apps do not share the same name.




18

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern Use nominal or verb phrases.

Examples Huawei Club/

Huaweiמועדון

2.2.4 Feature name

Feature names should meet the following requirements:




19

Avoid any negative implications in local culture

Conciseness - the shorter, the better

Consistency - apply the same conventions in regards to length and structure

If possible, name should describe the function comprehensively

Two features do not share the same name.

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern Use nominal or verb phrases.

Examples Do not disturb / נא לא להפריע

2.2.5 Menu item




20

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern Use "Verb", "Verb + Noun", or nominal phrases.

Example Edit / עריכה

Copy / העתקה

Set as / הגדרה בשם




21

2.2.6 Button

Figure 2-6 Frameless buttons




22




23

Figure 2-7 Stepper buttons




24

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern Use "Verb", "Verb + Noun", or nominal phrases.

Example Delete / מחק

Cancel / ביטול

Share contacts / שיתוף אנשי קשר

Tips Keep it short (One or two words)

2.2.7 Message

Figure 2-8 Dialog box message Figure 2-9 Toast message




25

Figure 2-10 No content message Figure 2-11 Instruction message




26

Figure 2-12 Status bar message Figure 2-13 Notification panel message

Figure 2-14 Introduction message




27

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern See examples.

Examples No contacts / אין אנשי קשר

No help document available. / זמיןאין מסמך עזרה.

Operation failed. / הפעולה נכשלה.

Failed to delete the contact. / מחיקת איש הקשר נכשלה.

Incorrect password. / סיסמה שגויה.

Memory is full. / הזיכרון מלא.

Clear the call log? / למחוק את יומן השיחות?

Delete all images? / למחוק את כל התמונות?

Loading... / טוען...

Scanning... / סורק...

2.2.8 Check box




28

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern Use "Verb + Noun" or nominal phrases.

Examples Do not remind again / לא להזכיר שוב

Use default weekend / השתמש בסוף שבוע ברירת מחדל

2.2.9 Entry

Capitalization NA

Punctuation NA

Article NA


Examples Voicemail service / שירות תא קולי

Week starts on / השבוע מתחיל ביום

Manage applications / ניהול יישומים

Running services / הפעלת שירותים




29

2.2.10 Secondary text

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern Usually use an imperative sentence or the value of the

corresponding entry.

Examples Show password as you type / הצג את הסיסמה בזמן ההקלדה

Allow applications to access secure certificates and other

credentials / אפשר ליישומים לגשת לאישורים מאובטחים ותעודות אחרות

Enabled / מופעל

Do not use personal pronoun in secondary text if possible.




30

It could be fixed in the manner below:

(ORIGINAL, personal pronoun) Remind me to clean up large files and apps that I

haven't used for a long time

(IMPROVED, no personal pronoun) Send reminders to clean up large files and apps that

have not been used for a long time




31

2.2.11 Spinner

Capitalization NA

Punctuation NA

Article NA


Examples Mobile / סלולרי

Home / בית




32

2.2.12 Time line

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern Use date or time.

Examples 12/11

14:30

PM

2:45 (AM or PM is displayed above the time)




33

2.2.13 List

Capitalization NA

Punctuation NA

Article NA


Examples Add album / הוסף אלבום

Others / אחרים




34

2.2.14 Switch

Capitalization NA

Punctuation NA

Article NA


Examples Turn on Bluetooth /

Bluetoothהפעל

Visibility / נראות




35

2.2.15 Text box

Capitalization NA

Punctuation NA

Article NA


Examples Search for contacts / חיפוש אנשי קשר

Name / שם

Enter password / הזן סיסמה




36

2.2.16 Slider

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern Use nominal phrases. It is recommended that you use only one

word.

Examples Warm / חם

Cold / קר




37

2.2.17 Peek notifications

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern See examples

Examples House to sell / בית למכירה

Investment opportunity / הזדמנות השקעה

2.2.18 Toolbar




38

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern Use "Verb + Noun" or nominal phrases

Examples Search / חיפוש

New contact / איש קשר חדש

Delete / מחק

2.2.19 Functional alerts




39

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern Use "Verb + Noun" or nominal phrases

Examples To adjust blur, drag the slider / גרור את המחוון, כדי לכוונן טשטוש

To refocus, touch here / גע כאן, כדי למקד מחדש

To edit your photo, touch here / גע כאן, כדי לערוך את התמונה

2.2.20 Help guide – announcements

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern Used to display important information that needs immediate attention.

Examples Your phone's system settings do not support this feature. / הגדרות המערכת של הטלפון לא תומכות בתכונה זו




40

2.2.21 Help guide – full screen

Capitalization NA

Punctuation NA

Article NA


Examples Start recording / התחל להקליט

Quick start / התחלה מהירה

Pause and end / השהה וסיים




41

2.2.22 Progress bar

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern See example

Examples Loading… / טוען...

Updating... / מעדכן...

Upgrading…Please‎wait. / נא להמתין ...משדרג.




42

2.2.23 Drawer




43

Capitalization NA

Punctuation NA

Article NA

Sentence Pattern NA

Examples WLAN

Dual SIM Management /

כפול SIMניהול

2.2.24 In-app notification




44

Capitalization NA

Punctuation NA

Article Use articles

Sentence Pattern See examples

Examples Contact's birthday has been synced to the Calendar /

יום הולדת של איש הקשר סונכרן עם לוח השנה

2.2.25 Chips




45

2.2.26 Grid




46

2.2.27 Bottom sheet

2.2.28 Badges

Figure 2-15 Home screen badge




47

Figure 2-16 Tool bar badge

Figure 2-17 List badge

Documents

Huawei Hebrew UI Style Guide for Terminal Products V5g11n.rnd.huawei.com/UIDoc/WebContent-2/Consumer/EMUI/WebContent-3... · Huawei Hebrew UI Style Guide for Terminal Products V5.0