The Style Guidelines That I Follow

The cover of the style guide, Read Me First! A Style Guide for the Computer Industry

For translations from German and Russian to English, the style guide that I rely on is Read Me First! A Style Guide for the Computer Industry (Sun Microsystems, 2009). If a client asks me to follow a different style guide, then I use that. Otherwise, I adhere to the recommendations of Read Me First! with the following exceptions and additions:

Contractions

I use natural, commonly-used contractions like “that’s” and “it’s” unless a very formal tone is needed in the text (and I keep some contractions such as “don’t” in any case.) This ensures that text flows naturally.

Date Formats

I never use the format “04/03/20.” While this is the abbreviated form most often used in the United States, it would be misunderstood in Britain and other European countries because the month and day would be understood in reverse order. I translate into US English, but I still assume that my translations are likely to be read by people from different countries. So I avoid the ambiguity by always including an abbreviation for the month and putting the date’s elements in order from smallest to biggest units, in the format “Fri 03-Apr-20.” When space is more limited I reduce it to “3Apr20” or similar.

In long form I usually write dates like “Friday 3 April 2020,” in the sequence consistent with what I just mentioned above. But when a more casual tone is called for, then “Friday, April 3rd, 2020.”

Headings

Read Me First! mandates capitalization of headings as follows: “Capitalize the first letter of the first word and the first letter of all other words except conjunctions, articles, prepositions of fewer than four letters, and the ‘to’ in infinitives. Capitalize the second element of a hyphenated compound word unless the first element is a prefix.” This style of capitalization is often called “title caps,” and it differs from the “sentence-cap” styles of Google and Microsoft. I make one small adjustment to the style guide, by saying “except coordinating conjunctions.” This means that I capitalize “When” but not “and”; this keeps the style more in line with what I was taught in school.

Key Name Conventions

For combinations of keys pressed simultaneously, the style guide recommends putting a hyphen between the names: “press Alt-F-N.” That’s pretty standard. For key combinations pressed in sequence, I follow the Microsoft convention of using commas: “press Alt, F, N.” (The style guide’s standard way to indicate this is with the plus sign: “press Alt+F+N,” but I think that most people would understand this to mean pressing the keys simultaneously. Commas convey it much more clearly.)

Names

I leave names in their original form from the source text: names of people, companies, songs, etc. Usually (when their meaning is relevant to the reader of the target text), I add a translation in square brackets [like this] at the first occurrence of the name in the text.

Punctuation

Regarding exclamation marks, the style guide says, “Do not use exclamation points except where they have some technical significance. For example, the ! operators in programming and scripting languages have technical meaning.” I use exclamation marks less than is common in German and Russian, but I don’t eliminate them completely from normal text.

Special Notes

I sometimes add extra text in square brackets for clarification. Some examples are:
[illegible text]
[signature here]
[text of the stamp:]
[text in the logo:]
[translator’s note: ]

Time Formats

For my own personal use, I prefer to write times using the 24-hour clock, such as “17:05.” It’s clear and brief, easier to keep track of time-zone differences, and it makes more sense to me than counting the hours up two times in one day. This is also the system that Read Me First! recommends. But I recognize that most people don’t use this format, so in my translations I only use 24-hour time if I think that it will be welcome; usually I write times formatted like “5:05 pm.”

Transliteration

When translating from Russian, I transliterate names and some other special words from the Cyrillic alphabet to the Roman alphabet. There is no regular, standard system of transliteration from Russian in common use. So I try to follow the most commonly used and logical ways, and I use the most widely accepted spellings for these words as far as practical.

Units of Measurement

Texts in German and Russian use the metric system. I keep these same measurements in metric in my translations. When I think it will be needed, I add conversions to the US system after them in parentheses.

Scope of Professional Services

To ensure the best possible outcome for your project, please note the following regarding the scope of my consulting:

Language & communication focus: My expertise is in technical localization, linguistic precision, and cultural signalling for the US market. My role is to ensure your message is communicated clearly and effectively to a Silicon Valley audience.
No substitute for other specialized counsel: While I help localize documentation for compliance (SOC 2), legal notices, and financial pitches, I am not an attorney, CPA, or licensed financial advisor. My work involves translating and adapting your existing professional content; it does not constitute legal, accounting, or investment advice.
Technical implementation: While I have familiarity with Linux and the IT industry, I do not provide engineering or IT systems architecture advice.
Marketing strategy: I provide high-impact copywriting and GTM (Go-To-Market) linguistic support based on your existing strategy. I am not a marketing agency and do not provide market research or strategic business planning.

I strongly recommend that all finalized localized documents be reviewed by your respective legal, technical, or financial experts to ensure they meet your specific corporate and regulatory requirements.