Tha Tha StyleGuide
Tha Tha StyleGuide
Table of Contents
1. Welcome ............................................................................................................................................... 4
1.1. Reference material ...................................................................................................................... 4
2. Microsoft voice ..................................................................................................................................... 5
2.1. Choices that reflect Microsoft voice............................................................................................ 5
2.1.1. Flexibility ............................................................................................................................. 6
2.1.2. Word choice ........................................................................................................................ 6
2.1.3. Word-to-word translation .................................................................................................. 7
2.1.4. Words and phrases to avoid ............................................................................................... 7
2.2. Sample Microsoft voice text ........................................................................................................ 8
2.2.1. Focusing on the user action ................................................................................................ 8
2.2.2. Explanatory text and providing support ............................................................................. 9
2.2.3. Promoting a feature.......................................................................................................... 11
2.2.4. Providing how-to guidelines ............................................................................................. 12
3. Inclusive language ............................................................................................................................... 12
3.1. Avoid gender bias ...................................................................................................................... 14
3.2. Accessibility ............................................................................................................................... 16
4. Language-specific standards ............................................................................................................... 17
4.1. Grammar, syntax and orthographic standards.......................................................................... 17
4.1.1. Abbreviations .................................................................................................................... 17
4.1.2. Acronyms .......................................................................................................................... 19
4.1.3. Adjectives .......................................................................................................................... 20
4.1.4. Localizing colloquialism, idioms, and metaphors ............................................................. 20
4.1.5. Numbers ........................................................................................................................... 21
4.1.6. Pronouns ........................................................................................................................... 21
4.1.7. Punctuation....................................................................................................................... 22
4.1.8. Sentence fragments .......................................................................................................... 25
4.1.9. Symbols & non-breaking spaces ....................................................................................... 25
4.1.10. Verbs ................................................................................................................................. 26
5. Localization considerations ................................................................................................................. 27
5.1. Accessibility ............................................................................................................................... 27
5.2. Applications, products, and features ........................................................................................ 27
5.3. Copilot predefined prompts ...................................................................................................... 28
5.4. Trademarks ................................................................................................................................ 30
5.5. Software considerations ............................................................................................................ 30
5.5.1. Arrow keys ........................................................................................................................ 31
5.5.2. Error messages.................................................................................................................. 31
5.5.3. Keyboard shortcuts ........................................................................................................... 33
5.5.4. Keys ................................................................................................................................... 36
5.5.5. Numeric keypad ................................................................................................................ 37
5.5.6. Shortcut keys .................................................................................................................... 37
5.6. Voice video considerations........................................................................................................ 41
5.6.1. English pronunciation ....................................................................................................... 41
5.6.2. Tone .................................................................................................................................. 43
5.6.3. Video voice checklist ......................................................................................................... 44
1. Welcome
Welcome to the Microsoft Localization Style Guide for Thai. This guide will help you
understand how to localize Thai content in a way that best reflects the Microsoft voice.
• Make sure you understand the key tenants of the Microsoft voice.
• Familiarize yourself with the recommended style references in Thai.
Normative references
Adhere to these normative references. When more than one solution is possible, consult
the other topics in this style guide for guidance.
1. พจนานุกรมฉบับราชบัณฑิตยสถาน พ.ศ.2554, ISBN9786167073804
Informative references
2. Microsoft voice
Microsoft’s brand personality comes through in our voice and tone—what we say and
how we say it. The design renaissance across Microsoft products, services, and
experiences hinges on crisp simplicity.
• Warm and relaxed: We’re natural. Less formal, more grounded in honest conversations.
Occasionally, we’re fun. (We know when to celebrate.)
• Crisp and clear: We’re to the point. We write for scanning first, reading second. We
make it simple above all.
• Ready to lend a hand: We show customers we’re on their side. We anticipate their real
needs and offer great information at just the right time.
The Microsoft voice targets a broad set of users from technology enthusiasts and casual
computer users. Although content might be different for different audiences, the
principles of Microsoft voice are the same. However, Microsoft voice also means
keeping the audience in mind. Choose the right words for the audience: use technical
terms for technical audiences, but for consumers use common words and phrases
instead.
These key elements of Microsoft voice should also extend across Microsoft content for
all language locales. For each language, the specific choices in style and tone that
produce Microsoft voice are different.
Translating Thai in a way that reflects Microsoft voice means choosing words and
grammatical structures that reflect the same style as the source text. It also means
considering the needs of the audience and the intent of the text.
The general style should be clear, friendly and concise. Use language that resembles
conversation observed in everyday settings as opposed to the formal, technical
language that is often used for technical and commercial content.
When you are localizing source text written in Microsoft voice, feel free to
choose words that aren’t standard translations if you think that’s the best way to stay
true to the intent of the source text.
Because Microsoft voice means a more conversational style, literally translating the
source text may produce target text that is not relevant to customers. To guide your
translation, consider the intent of the text and what the customer needs to know to
successfully complete the task.
2.1.1. Flexibility
It’s important for translators to modify or rewrite translated strings so that they are
more appropriate and natural to Thai customers. To do so, try to understand the whole
intention of the sentences, paragraphs, and pages, and then rewrite just like you are
writing the contents yourself. Sometimes, you may need to remove any unnecessary
content.
Terminology
Use approved terminology from Microsoft language resources, for example for key
terms, technical terms, and product names.
Meet without being there ประชุมร่ วมกันแม้อยูค่ นละที่ ประชุมโดยไม่ตอ้ งอยูท่ ี่นนั่
Encounter ประสบ พบ
Locate ค้นหา หา
Refer to อ้างอิงไปที่ ดู
Give your PC a
name—any name
you want. If you Address the user directly
want to change ใส่ชื่อพีซีตามต้องการ ถ้าคุณต้องการเปลี่ยนสี พ้นื หลัง using second person
the background ให้ปิดความคมชัดสูงในการตั้งค่าพีซี pronoun to take the
color, turn high necessary action.
contrast off in PC
settings.
US
th-TH target Explanation
English
The
The language
updates
is natural, the
are
way people tal
installed,
k. In this case
but
voice is
Windows
reassuring,
Setup ติดตั้งการปรับปรุ งแล้ว แต่ Windows Setup
letting the
needs to ต้องการให้เริ่ มระบบของคอมพิวเตอร์ใหม่เพื่อให้การติดตั้งมีผล หลังจากที่เริ่ มระบบใหม่แล้ว
user know
restart for เราจะดาเนินการต่อจากส่ วนที่คา้ งอยู่
that we’re doi
them to
ng the work.
work. After
Use of "we"
it restarts,
provides a
we’ll keep
more personal
going
feel.
from
where we
left off.
If you
restart
Informing the
now, you
user on the
and any
outcome if a
other ถ้าคุณเริ่ มระบบของคอมพิวเตอร์ใหม่เดี๋ยวนี้ งานที่ไม่ได้บนั ทึกไว้ของคุณและคนอื่นๆ specific action
people
ที่ใช้พีซีเครื่ องนี้อาจหายไป is taken. In this
using this
case the
PC could
action is a
lose
restart.
unsaved
work.
This
document
will be
automatica Voice talks to
lly moved the
to the user informati
right เอกสารนี้จะถูกย้ายไปยังไลบรารี และโฟลเดอร์ที่ถูกต้องโดยอัตโนมัติหลังจากที่คุณแก้ไขคุณสมบัติทไี่ ม่ถู vely
library and กต้องหรื อหายไปแล้ว and directly
folder after on the action
you that will be
correct taken.
invalid or
missing
properties.
Something
bad
happened!
Without
Unable to
มีบางอย่างผิดปกติ! ไม่พบแฟ้มดาวน์โหลดที่ใช้สร้าง USB แฟลชไดรฟ์ สาหรับเริ่ มระบบ complexity an
locate
d using
downloade
short sentence
d files to For Office: มีบางอย่างผิดปกติ! ไม่พบไฟล์ดาวน์โหลดที่ใช้สร้าง USB
s inform the
create แฟลชไดรฟ์ สาหรับเริ่ มระบบ user what has
your
happened.
bootable
USB flash
drive.
2.2.3. Promoting a feature
Picture
password is
a new way
to help you Promoting a
protect your specific feature
touchscreen with the use of
PC. You em-dash to
choose the emphasis the
picture— รหัสผ่านรู ปภาพเป็ นการปกป้องพีซีหน้าจอสัมผัสในรู ปแบบใหม่ที่ให้คุณสร้างรหัสผ่านได้ไม่ซ้ าใค specific
and the ร โดยให้คุณเลือกรู ปภาพและรู ปแบบการวาดตามต้องการ requirements to
gestures enable
you use the feature whic
with it—to h in this case is
create a picture
password password.
that’s
uniquely
yours.
Let apps
Promoting the
give you
use of apps.
personalize
Depending on
d content
the context of
based on
ให้แอปทาเนื้อหาแบบส่ วนบุคคลให้คุณโดยยึดตามที่ต้ งั ชื่อ รู ปภาพประจาตัว the string we can
your PC’s
add some more
location, และข้อมูลโดเมนอื่นๆ
familiarity to the
name,
text by using
account
everyday
picture, and
words for e.g.
other
PC.
domain info.
2.2.4. Providing how-to guidelines
3. Inclusive language
Microsoft technology reaches every part of the globe, so it's critical that all our
communications are inclusive and diverse. These guidelines provide examples on how to
use inclusive language and avoid habits that may unintentionally lead to
marginalization, offense, misrepresentation, or the perpetuation of stereotypes.
General guidelines
Use plain language. Use straightforward, concrete, and familiar words. Plain and
accessible language will help people of all learning levels and abilities. Some examples
include using a two-syllable word over a three-syllable word or several clear words
instead of one complicated term or concept.
Be mindful when you refer to various parts of the world. If you name cities,
countries, or regions in examples, make sure they're not politically disputed. In examples
that refer to several regions, use equivalent references—for example, don't mix
countries with states or continents.
Don't generalize or stereotype people by region, culture, age, or gender, not even if
the stereotype is positive. For example, when representing job roles, choose names that
reflect a variety of gender identities and cultural backgrounds.
Don't use terms that may carry unconscious racial bias or terms associated with
military actions, politics, or controversial historical events and eras.
colleagues; everyone; guys; ladies and เพื่อนร่ วมงาน, ทุกคน, พวกคุณ, สุ ภาพสตรี ,
all gentlemen ทั้งหมด สุ ภาพบุรุษ
Use gender-neutral alternatives for common terms. Avoid the use of compounds
containing gender-specific terms.
The table below contains examples of gender-biased words or compounds that should
be avoided in Thai and the alternative that should be used to promote gender
inclusivity.
Target examples
When presenting generalization, use plural noun forms (for example, ผู้คน, บุคคล,
นักเรียน, etc.).
Don't use gendered pronouns (เธอ, ของเธอ, เขา, ของเขา, etc.) in generic references. Instead:
A
Develope
develope
rs need
r needs
access to
access to
servers in
servers
their
in his
develop
develop นักพัฒนาจาเป็ นต้องมีสิทธิ์เข้าถึงเซิร์ฟเวอร์ในสภาพแวด นักพัฒนาจาเป็ นต้องมีสิทธิ์เข้าถึงเซิร์ฟเวอร์ในสภาพแว
ment
ment
environm ล้อมการพัฒนาของตนเอง ดล้อมการพัฒนาของเขา
environ
ents, but แต่พวกเขาไม่จาเป็ นต้องมีสิทธิ์เข้าถึงเซิร์ฟเวอร์ใน แต่เขาไม่จาเป็ นต้องมีสิทธิ์เข้าถึงเซิร์ฟเวอร์ ใน
ment,
they Azure Azure
but he
don't
doesn't
need
need
access to
access to
the
the
servers in
servers
Azure.
in Azure.
When
When the
the
author
author
opens
opens เมื่อผูเ้ ขียนเปิ ดเอกสารนั้น …. เมื่อผูเ้ ขียนเปิ ดเอกสารของเธอ ….
the
her
documen
docume
t ….
nt ….
To call To call
someone, someone
select the , select เมื่อต้องการโทรหาบุคคลอื่น เลือกชื่อของบุคคลนั้น เมื่อต้องการโทรหาบุคคลอื่น เลือกชื่อของเขา
person's his
เลือกทาการโทร จากนั้นเลือกหมายเลขที่คณ ุ ต้องการโทร เลือกทาการโทร จากนั้นเลือกหมายเลขของเขา
name, name,
select Ma select M
ke a ake a
phone phone
call, and call, and
then then
choose select his
the number.
number
you'd like
to dial.
When you're writing about a real person, use the pronouns that the person
prefers, whether it's เขา, เธอ, พวกเขา, or another pronoun. It's OK to use gendered pronouns
(like เขา, เธอ, ของเขา, and ของเธอ) when you're writing about real people who use those
pronouns themselves.
Note: Gender-neutral language should be used in new products and content going
forward, but it’s acceptable that we don’t update all existing or legacy material.
3.2. Accessibility
Microsoft devices and services empower everyone, including people with disabilities, to
do the activities they value most.
Focus on people, not disabilities. Don't use words that imply pity, such
as ไม่สมประกอบ or กลุ่มคนพิเศษ. The preferred option is not to mention a disability unless it's
relevant.
person with a disability handicapped ผูพ้ ิการ, ผูท้ ุพพลภาพ คนง่อย, คนไม่ครบ 32
person without a disability normal person; healthy person คนทัว่ ไป คนปกติ, คนครบ 32
Use generic verbs that apply to all input methods and devices. In procedures and
instructions, avoid verbs that don't make sense with alternative input methods used for
accessibility.
Use this Not this Use this Not this
Keep paragraphs short and sentence structure simple—aim for one verb per
sentence. Read text aloud and imagine it spoken by a screen reader.
Spell out words like และ, บวก, and เกี่ยวกับ. Screen readers can misread text that uses
special characters like the ampersand (&), plus sign (+), and tilde (~).
4. Language-specific standards
This part of the style guide contains information and guidelines specific to Thai.
This section includes information on how to apply the general language and syntax rules
to Microsoft products, online content, and documentation.
4.1.1. Abbreviations
Common abbreviations
You might need to abbreviate some words in the UI (mainly buttons or options
names) due to lack of space.
Some general considerations apply to software, help and documentation and web
localizations.
Do not use abbreviated forms of fictitious names that appear elsewhere in the
documentation in their full form.
List of common abbreviations:
จังหวัด จ.
ตารางเมตร ตร.ม.
ทิศเหนือ น.
น้ าหนัก น.น.
บาท บ.
In addition to common measurements such as km, m, cm, mm, etc., the following
abbreviations are commonly used in Thai technical documentation.
Note: To distinguish “byte” and “bit”, use a small letter, ‘b’ for “bit” and a larger letter, ‘B’
for “byte”.
Measurement Abbreviation
Gigabyte GB
Kilobyte KB
Megabyte MB
When full words are used, they must be spelled out in Thai.
Examples:
32 bits 32 บิต
4.1.2. Acronyms
Acronyms are words made up of the initial letters of major parts of a compound term.
Some well-known examples are WYSIWYG (What You See Is What You Get), DNS
(Domain Name Server), HTML (Hypertext Markup Language), OLE (Object Linking and
Embedding) or RAM (Random Access Memory). Most of acronyms are kept in English in
Thai localization.
Localized acronyms
Example:
English Thai
CPU ซีพียู
PC พีซี
Unlocalized acronyms
Example:
English Thai
WYSIWYG WYSIWYG
LAN LAN
ISDN ISDN
OCR OCR
TCP/IP TCP/IP
4.1.3. Adjectives
Possessive adjectives
When possessive adjectives are used in the source text, they should be handled in the
following way:
Example:
English Thai
The Microsoft voice allows for the use of culture-centric colloquialisms, idioms and
metaphors (collectively referred to "colloquialism").
Choose from the following options to express the intent of the
source text appropriately.
• Do not attempt to replace the source colloquialism with a Thai colloquialism that fits the
same meaning of the particular context unless it is a perfect and natural fit for that
context.
• Translate the intended meaning of the colloquialism in the source text (as opposed to
literally translating the original colloquialism in the source text), but only if the
colloquialism’s meaning is an integral part of the text that can’t be omitted.
• If the colloquialism can be omitted without affecting the meaning of the text, omit it.
4.1.5. Numbers
This topic includes guidelines when to use numerals (symbol that represents a number.
e.g. 1, 2, 3, 234, etc.) and when to spell out numbers (one, two, three, two hundred and
thirty-four) and other aspects for the particular language.
There is a standard guideline for Thai translations to strictly adhere to the source
number.
If the source number is a number such as "10," then the target number will be "10," too.
Conversely, the target number will be translated as "ten" in Thai language if the source
number is written as "ten."
For example:
There are 3 oranges, 4 apples and a bunch of grape on the table.—มีส้ม 3 ผล แอปเปิ้ ล 4 ผล
และองุ่นหนึ่งพวงอยูบ่ นโต๊ะ
All fifty students did not come to class.—นักเรี ยนทั้งห้าสิ บคนไม่เข้าห้องเรี ยน
4.1.6. Pronouns
"It"
Avoid using มัน when you see "it" in English documents. It is okay to repeat the same
word instead of using มัน in the text. We hardly find the word มัน in non-fictional Thai text.
มัน is normally used for animals. In some situations มัน is used when we want to refer to
something or someone that we dislike. "It" can be left out of the text without changing
its meaning. You can still use มันif it makes the sentence more complete.
Example: or let it float
Should be (+) หรื อให้ลอยอยู่
Avoid Using (-) หรื อให้มนั ลอยอยู่
"I" To translate "I", we suggest using ฉัน to portray men and women as equals. Use ฉัน in
examples and illustrations also. Thai men usually do not use ฉัน in conversations. We cannot use
ผม either because it is for men only.
4.1.7. Punctuation
The rules of using punctuation in Thai are not the same as in English. It is not
recommended to use punctuation in Thai sentences. Try to translate punctuation.
Comma
Example:
English Thai
English Thai
Blogger, WordPress, TypePad, all others (+) Blogger, WordPress, TypePad และอื่นๆ
Exception: "index keywords" are formatted with comma which separates entry level 1
from entry level 2. These commas must not be removed and order must be respect.
Colon
English Thai
Prevent others from playing files that are rated higher (+)
than: ป้องกันไม่ให้ผอู ้ ื่นเล่นไฟล์ที่มีการจัดอันดับสู งกว่า:
Hyphen
Hyphen (-), the shorter one. In Thai it is called ยัติภงั ค์. It can be used to designated the
range of numbers as the style guide said.
There are some more occasions to use hyphen in Thai language. For example:
However, en dash (–) and the em dash (—), with longer line called in Thai ยัติภาค.
Actually, Thai people don’t really separate the usage of hyphen, en/em dash strictly as in
English. That means en/em dash can be used in the above occasions as well. Except
for as math symbol, we only use hyphen.
Example:
English Thai
Period
Example:
English Thai
Quotation marks
In US source strings, you may find software references surrounded by English quotation
marks. In Thai, use quotation marks the same way as in English. However, it may be
omitted especially if the expression is not really a question such as “could you please
enter your name?”.
English Thai
Are you sure you want to delete your contact "%s"? (+) คุณแน่ใจหรื อไม่ว่าคุณต้องการลบผูต้ ิดต่อ "%s" ของคุณ
Parentheses
In English, there is no space between the parentheses and the text inside them. In Thai,
use parentheses the same way as in English.
English Thai
For the Microsoft voice, use of sentence fragments helps convey a conversational tone.
They are used whenever possible as they are short and to the point.
You can begin sentences with conjunctions (and, but, or) if it helps readability.
Source Translation
Special characters in table below should be kept in Thai translation in the same way as in
English:
For US English Microsoft voice, verb tense helps to convey the clarity of Microsoft voice.
Simple tenses are used. The easiest tense to understand is the simple present, like we
use in this guide. Avoid future tense unless you are describing something that will really
happen in the future and the simple present tense is inapplicable. Use simple past tense
when you describe events that have already happened.
Continuous operations are usually expressed in English with a gerund, which should be
translated into Thai with "กาลัง."
Example:
English Translation
(+) กาลังดาวน์โหลดแฟ้ม...
Downloading file...
(+) For Office: กาลังดาวน์โหลดไฟล์...
In English, passive forms of verbs are frequently used, whereas in Thai, passive forms
may decrease readability so should be often avoided.
Example:
English Translation
The language in Microsoft products should have the "look and feel" of a product
originally written in Thai, using idiomatic syntax and terminology, while at the same time
maintaining a high level of terminological consistency, so as to guarantee the maximum
user experience and usability for our customers.
5.1. Accessibility
Accessibility options and programs are designed to make the computer usable
by people with cognitive, hearing, physical, or visual disabilities.
Product, feature and component names are often located in the so-
called "version strings" as they appear in the software.
Example:
US English Thai target
Copilot prompts are the instructions or questions you use to tell Copilot what you want
it to do. You can ask Copilot to create or edit content, ask questions, summarize
information, and catch up on things.
Across various Microsoft products, you will find an array of predefined prompts
designed to guide users in creating, learning, and using Microsoft Copilot.
Copilot prompts are functional. It is crucial that the translations for Copilot predefined
prompts are accurate, consistent, concise, natural, and use the appropriate tone of voice.
Please remember that the quality of these translations can significantly influence Copilot
responses or outcomes.
• Be clear and specific: English prompts are generally questions or requests starting with
an action verb. Make sure the target prompts are natural questions or requests. Avoid
using vague language. Use clear and specific phrases or keywords.
• Keep it conversational: Be consistent with Microsoft Voice principles. Use simple and
natural language when translating prompts. Avoid adopting a tone that resembles a
machine. Use a formal tone of voice and form of address when translating Copilot
predefined prompts.
• Be polite and professional: Use kind and respectful language, as this helps foster
collaboration and improves the AI’s responsiveness and performance. Don’t use slang
and jargon.
• Use quotation marks: This helps Copilot know what to write, modify, or replace for the
user.
• Pay attention to punctuation, grammar, and capitalization: Clear communication
helps collaboration between Copilot and the user.
• Pay attention to the placement of entity tokens: An entity token is a placeholder that
is used to trigger a pop-up menu in the UI to let customers choose an entity, such as a
file, contact, meeting, so that the prompt uses specific data from the specified entity. As
with any other placeholder, an entity token is not localizable, and the position of the
entity token should make sense in the target text syntax.
• Entity token localization exception: Some prompts may be a display text (i.e., an
example) and, in such cases, the entity token needs to be translated. Read the Dev
comment carefully.
Exception example:
Source string: List key points from [file]
DevComment=Translate [file]
• Be consistent: Some English prompts are remarkably similar. Make sure to translate
them consistently.
Create a list of
The placeholder here can
<placeholder>color สร้างรายการ<placeholder>ชื่อสี ที่ได้รับแรงบันดาลใจจ
be translated as it is a
names inspired by the ากมหาสมุทร</placeholder>
display text example.
ocean</placeholder>
5.4. Trademarks
General guidelines
The arrow keys move input focus among the controls within a group. Pressing the right
arrow key moves input focus to the next control in tab order, whereas pressing the left
arrow moves input focus to the previous control. Home, End, Up, and Down also have
their expected behavior within a group. Users can’t navigate out of a control group
using arrow keys.
Error messages are messages sent by the system or a program, informing the user of an
error that must be corrected in order for the program to keep running. The messages
can prompt the user to take action or inform the user of an error that requires rebooting
the computer.
The phrases bellow commonly occur in error messages. When you are translating them,
try to use the provided target phrases. However, feel free to use other ways to express
the source meaning if they work better in the context.
Examples:
คุณไม่สามารถบันทึกไฟล์บนไดรฟ์ นี้
Cannot find
… English: Unable to find the user
Could not information for the file.
find … ไม่พบ...
Unable to Thai: (+) ไม่พบข้อมูลของผูใ้ ช้สาหรับแฟ้มนี้
find …
Unable to (+) For Office: ไม่พบข้อมูลของผูใ้ ช้สาหรับไฟล์น้ ี
locate …
Not enough
memory …
Insufficient
memory … English: Indexing is paused because there
There is not is not enough memory available.
enough หน่วยความจาไม่เพียงพอ
memory … Thai: (+)
There is not การทาดัชนีตอ้ งหยุดชัว่ คราวเนื่องจากหน่วยความจาไม่เพียงพอ
enough
memory
available …
This cannot be
translated as
... is not this type of
available fragment. The
n/a n/a
... is translation will
unavailable be varied
depend on
context.
Error messages containing placeholders
When localizing error messages containing placeholders, try to find out what will replace
the placeholder. This is necessary for the sentence to be grammatically correct when the
placeholder is replaced with a word or phrase. Note that the letters used in placeholders
convey a specific meaning, see examples below:
English Translation
Examples:
New
Cancel
Options
Use the following guidelines when localizing keyboard shortcuts or access keys:
Using the second typing order, placing the accelerator key under ต or า will not cause
overlapped accelerator key problem.
Usage: Is it
Keyboard shortcuts special options Notes
allowed?
Content writers usually just refer to “keyboard shortcuts” in content for a general
audience. In localization, however, we distinguish the following terms:
Term Usage
A subtype of keyboard shortcut. A letter or number that the user types to access UI
controls that have text labels. Access keys are assigned to top-level controls so that
access the user can use the keyboard to move through the UI quickly.
key Example: F in Alt+F
Example in UI localization: H&ome
In keyboard shortcuts, most access keys are used with the Alt key.
The letter or number that appears in the ribbon when the Alt key is pressed.
In UI localization, the key tip is the last character present in the strings after the
“`” character.
Example: In UI localization Home`H
key
tip
A subtype of keyboard shortcut. A key that the user types to perform a common
action without having to go through the UI. Shortcut keys are not available for every
command.
shortc
Example: Ctrl+N, Ctrl+V
ut key
In keyboard shortcuts, most shortcut keys are used with the Ctrl key.
Ctrl+letter combinations and function keys (F1 through F12) are usually the best
choices for shortcut keys.
In English, references to key names, like arrow keys, function keys and numeric keys,
appear in normal text (not in small caps).
Key names
Alt Alt
Backspace Backspace
Break Break
Ctrl Control
Delete Delete
End End
Enter Enter
Esc Esc
Home Home
Insert Insert
Page Up Page Up
Pause Pause
English key name Thai key name
Shift Shift
Spacebar สเปซบาร์
Tab Tab
Up Arrow ลูกศรขึ้น
It is recommended that you avoid distinguishing numeric keypad keys from the other
keys, unless it is required by a given application. If it is not obvious which keys need to
be pressed, provide necessary explanations.
สลับไปที่โปรแกรมประยุกต์หลักถัดไป
Access Start button in taskbar Ctrl+Esc เปิ ดปุ่ ม เริ่ ม ในแถบงาน Ctrl+Esc
File menu
แฟ้ม สร้าง
File New Ctrl+N Ctrl+N
For Office: ไฟล์ สร้าง
แฟ้ม เปิ ด
File Open Ctrl+O Ctrl+O
For Office: ไฟล์ เปิ ด
แฟ้ม ปิ ด
File Close Ctrl+F4 Ctrl+F4
For Office: ไฟล์ ปิ ด
แฟ้ม บันทึก
File Save Ctrl+S Ctrl+S
For Office: ไฟล์ บันทึก
แฟ้ม บันทึกเป็ น
File Save as F12 F12
For Office: ไฟล์ บันทึกเป็ น
แฟ้ม ตัวอย่างก่อนพิมพ์
File Print Preview Ctrl+F2 Ctrl+F2
For Office: ไฟล์ ตัวอย่างก่อนพิมพ์
แฟ้ม พิมพ์
File Print Ctrl+P Ctrl+P
US English Thai shortcut
US command Thai command
shortcut key key
แฟ้ม ออก
File Exit Alt+F4 Alt+F4
For Office: ไฟล์ ออก
Edit menu
Help menu
Help F1 วิธีใช้ F1
Font format
Paragraph format
A good Microsoft voice video addresses only one intent (one customer problem), is not
too long, has high audio quality, has visuals that add to the information, and uses the
right language variant/dialect/accent in voiceover.
• Focus on the intent. Show the best way to achieve the most common task and stick to it.
• Show empathy. Understand and acknowledge the viewer’s situation.
• Use SEO (Search Engine Optimization). Include search phrases in the title, description,
and headers so that people can easily find the topic.
• Talk to the customer as if (s)he is next to you, watching you explain the content.
• Record a scratch audio file. Check for length, pace and clarity.
Generally speaking, English terms and product names left unlocalized in target material
should be pronounced the English way. For instance, Microsoft must be pronounced the
English way. However, if your language has an established pronunciation for some
common term (such as "server") the local pronunciation should be used. Moreover,
pronunciation can be adapted to the Thai phonetic system if the original pronunciation
sounds very awkward in Thai.
Example Phonetics Comment
[sı’kjuər aı
SecurID
di:]
Thai people will not pronounce "pe" at the end of the word
Skype [skaip] "Skype"
Acronyms are pronounced like real words, adapted to the local pronunciation:
Example Phonetics
RADIUS [rédiəs]
ISA [aj ɛs e]
LAN [læn]
POP [pap]
Example Phonetics
IP [aj pi]
TCP/IP [ti si pi/aj pi]
OWA [o dəbəlju e]
URLs
"http://" should be left out; the rest of the URL should be read entirely.
The "dot" should be omitted, but can also be read out. If read out, then it must be
pronounced the Thai way, as ดอท.
Punctuation marks
Most punctuation marks are naturally implied by the sound of voice, e.g. ? ! : ; ,
The rules of using punctuation in Thai are not the same as in English. It is not
recommended to use punctuation in Thai sentences. Try to translate punctuation.
Special characters
Pronounce special characters such as / \ ˘ < > + - using the Thai translations approved
in Microsoft Terminology - Globalization | Microsoft Learn.
5.6.2. Tone
Use a tone that's appropriate for the text and target audience. For example, an informal,
playful, and inspiring tone may be used for most Microsoft products and games, while a
more formal, informative, and factual tone is appropriate in technical content.
5.6.3. Video voice checklist
Title
Visuals
Ending