Style Guide Igbo (ig)

Introduction

This style guide is intended for translators working on Mozilla projects. It provides in-depth information about the quality standards expected by Mozilla for the translation of all product components. All translators should read this guide before commencing any translation work.

This guide addresses general translation issues and specifies certain rules of style and usage specific to your language. It should be used as a guideline to avoid common typographic errors, and to maintain consistent terminology and writing style across a project’s components and indeed a product range. The guide should be used in conjunction with the current and previous product-specific glossaries, glossaries of other products of a product range, and the industry standard platform-specific glossaries, such as those provided by Mozilla.

This document may be updated or completed in the course of translation. Where no specific instruction or recommendation is specified, translators should use the phrasing and style that comply with industry standards.

General Style Considerations

Style guidelines

Follow these basic rules:

• Original American English text tends to be rather casual. For Igbo, use a neutral style, with the informal form of address.
• Try to avoid long, nested sentence constructions. If necessary, break up the original sentence and regroup it syntactically.
• Use wording that is brief and unambiguous.
• Use a consistent style throughout all product components and across a product range, to ensure that all Mozilla products can be linguistically identified as part of a group of products.

Style guidelines specific to Mozilla products

• Please refer to the reference documentation supplied by Mozilla and any Mozilla style guides and make a note of anything significant and specific that should be noted with respect to Mozilla.
• Please ensure to use a recently published dictionary (recommended source: Pharos 5-1 CD-ROM / Pharos Online list of technical dictionaries).
• Before returning any files, please be sure to run a recent Igbo spellchecker (in case of disagreements, the HAT spelling will be followed).

Reference terminology

The following terminology sources should be used as reference in the translation:

• Product-specific glossary, to ensure consistency across all product components.
• Previous version product-specific glossary, to ensure consistency between versions.
• Glossaries of other Mozilla products, to ensure cross-product consistency.
• Microsoft glossaries, to ensure adherence to some of the industry standards. The glossaries can be found at:http://www.microsoft.com/Language.

Terminology not found in the glossary or style guide

• Please make a log of any terms not found in the glossary or style guide that are used frequently in the materials. Return this log to Rubric so that the terms can be incorporated into the glossary. This increases consistency in large projects.

Abbreviations

General Abbreviations

• Avoid the use of non-standard abbreviations. Where no appropriate abbreviation exists, rather use the whole word.
• Where there are space restrictions in the UI, abbreviations can be used. These must be entered into the glossary with the full translation, and should be approved by the customer.
• The compounds below contain either an abbreviation or a numeral followed by a component name. The abbreviation or numeral is marked in red in the English example. The Igbo example below show how such constructions should be translated.

Note the difference between the styling of “Flọpị 5¼-inchi” and “nwayọ nwayọ 35 mm”, which results from the fact that "mm" is regarded a symbol and not an abbreviation. Igbo officially uses the metric (SI) system, which requires as space between a figure and the accompanying symbol.

Measurements and Numerals

In addition to common measurements such as km, m, cm, mm, etc., the following abbreviations are used in technical documentation:

Important: The old rule that all numerals up to 12 must be spelled out is no longer valid. Use your best judgment given the at hand, especially when a combination of numbers is involved.

Filename Extensions

• Filename extensions and graphic formats referenced by filename extensions such as BMP, GIF, HTML, PNG, TIFF must not be translated.

Acronyms

Acronyms are made up of the initial letters of several words that are represented by these letters. Some well-known examples are WYSIWYG (What You See Is What You Get), OLE (Object Linking and Embedding), or RAM (Random Access Memory).

If an acronymn has an official or commonly recognised translation in Igbo (e.g. if it is present in a general dictionary), use the Igbo acronymn. Otherwise, use the English acronymn. If the acronymn is followed in English by a full form, retain the acronymn in English and translate the full form into Igbo.

IMPORTANT: Do not translate an abbreviation or acronym that is a trademark, unless it is the official translation of that trademark.

Use recognised translations of acronyms where these exist, but avoid creating new, non-standard acronyms.

Articles

Product Names

Mozilla product names are used without definite or indefinite articles. Product names and non-translated feature names are considered proper nouns and are used without definite or indefinite articles in English.

Note that the product and feature names are regarded as proper nouns. They are not to be translated.

By contrast, translated feature names are used with a definite or indefinite article as they are not treated as proper names.

Copyrights and Trademarks

Product names should not be translated unless the client requests it.

Copyright protection is granted to any original work of authorship fixed in any tangible medium of expression from which it can be perceived, reproduced, or communicated.

Translation of Version Strings

• Please use the following guidelines when localizing version strings:
• Version strings that contain copyright information should always be translated.

In version strings containing feature names that are trademarked, the feature names that are trademarked should not be translated.

Gender-neutral Translation

You should always recognize your audience’s sensitivity to male and female stereotypes. Instead of stressing gender differences or reinforcing stereotypical distinctions between men and women, use language that is as neutral as possible. The neutral approach also applies to the localization of scenarios, comparisons, examples, illustrations, and metaphors.

Create a balance when assigning roles and functions to men and women (active vs. passive roles, leading vs. secondary roles, technical vs. non-technical professions, and so on). Scenarios, pictures, metaphors, and comparisons should be based on areas and attributes common to both genders.

Instead of using phrases which mention the two genders separately, use a general term that includes both genders such as “people,” “users,” or “persons.”

Avoid writing sentences that refer to a single person whose gender is unknown. You can often avoid this situation by rewriting the sentence to make the subject plural. In cases where a reference to a single person is impossible to avoid, do not use “he or she,” “him or her,” or “his or hers.” The language in Microsoft products should sound natural, as if part of a spoken conversation. Also, generally avoid the use of slashes to combine both genders (although sometimes exceptions are made - see table below).

Use the following strategies to avoid the use of overtly gender-biased expressions:

Nouns with gender bias such as nwoke, man, are generally replaced with gender neutral ones like onye, person, mmadụ, person, ndị, people etc. There is no gender distinction in Igbo pronouns. They have neutral reference. E.g. ‘Ọ dị mma.’ , can be translated as ‘it’s fine, she’s fine, he’s fine.’

Localized term vs. English term

The most common language of terminology in the computer world is English. However, it is quite unnatural in Igbo to use English words in an Igbo sentence (except for product names and acronyms). Resist the temptation to borrow an English word as-is except in pluralising which we most times leave as it is. Find out what the word means, and create a term that a reasonably intelligent Igbo reader will understand.

Gender

Many terms in circulation in the high tech industry have been adopted from English. They must follow Igbo grammar and syntax rules.

Inflections

The examples below show how English loanwords inflect for number in Igbo.

CD
CD-ROM
HTML
HTTP
SIM

Verbs and Verb Forms

Do not use an English verb as loan word in Igbo.

Headings

Headings should convey as much information as possible about the ensuing text to help readers locate information quickly. If in English the heading begins with a gerund, try to use a nominalized form in Igbo.

Capitalization

In English headings, all nouns, pronouns, adjectives, verbs, adverbs, and subordinate conjunctions (such as “that,” “until,” and “which”) are capitalized. Please do not apply the same principle to Igbo headings. Instead, follow the normal Igbo capitalization rules. The same rule applies to software strings.

In Lists and Tables

Whenever possible, headings of lists and tables should consist of one or two words, preferably active nouns. They should be concise, even if the source uses a longer phrase.

In English, lists may be headed in two ways, namely (a) an introductory phrase that is completed syntactically by every item in the list and (b) an “independent” introductory phrase followed by syntactically independent items.

In English, the syntax of the items are typically not affected by the phrasing of the introductory phrase, if it is one sentence. However, in Igbo, the word order of the introductory phrase can affect the word order of the individual items. When translating the introductory phrase, try to translate it in such a way that the items can be translated as an independent phrases.

Either way, care should be taken to ensure that every individual item is not an incorrect syntactical completion of the heading and makes sense in terms of meaning (semantics) and subject matter. Note that the position of the (main) verb may require a structure that differs significantly from the English.

Hyphenation and Compound formation

General Hyphenation Rules

In Igbo, hyphens are more common and more acceptable than in English. In fact, hyphens can be used in long compound nouns to make its meaning clearer. When faced with a highly complex compound, resolve it by clarifying the relationships among the various compound components. Ways of doing this include shifting the word order or using prepositions.

Examples:

This applies in particular to Mozilla product and component names that appear as the proper-noun element in compounds that are either proper nouns again, or common nouns (Examples below include Microsoft/Windows product names).

English Compounds

We do not automatically hyphenate purely English compounds. Use the following steps in handling US compounds:

• If the compound consists of no more than 3 components write it as one word in Igbo, unless there is serious risk of misunderstanding.
• If the compound is more complex, resolve it by:
  • inserting a hyphen at the appropriate point in the word (try to avoid using more than one hyphen in a single word, unless one of the hyphens is required and the other is optional).
  • adjusting the word order and applying the rules of Igbo syntax,
  • using prepositions,
  • reducing complexity by writing related components as one word.

Product Names

Product names must not be hyphenated. However, in order to offset the actual product name from the word that follows in a compound, the hyphen is placed right between the product name and the following term. Please note that this rule applies even if the word that follows is a US term.

Compounds with Acronyms, Abbreviations or Numerals

The compounds below contain either an abbreviation or a numeral followed by a component name. The abbreviation or numeral is marked in red in the English example. The Igbo example below show how such constructions should be translated.

Indexes

Capitalization, Prepositions and Articles

For first level entries (main index level), always capitalize the first letter of the first word. Write the remaining words according to existing Igbo capitalization rules.

Subentries: capitalize nouns, use lowercase for other entries.

In English headings, all nouns, pronouns, adjectives, verbs, adverbs, and subordinate conjunctions (such as “that,” “until,” and “which”) are capitalized. Please do not apply the same principle to Igbo headings. Instead, follow the normal Igbo capitalization rules. The same rule applies to software strings.

Prepositional phrases in English need to be translated according to their context; anglicisms should be avoided. The table below contains frequently used verbs and the prepositions that follow them.

Prepositions

Translate English prepositions according to their context and not too literally.

Prepositional phrases in English need to be translated according to their context; anglicisms should be avoided. The table below contains frequently used verbs and the prepositions that follow them. Please use this table as a reference.

This is a particularly problematic area, because some verbs used transitively in English cannot be so used in Igbo, and then something needs to be added or changed in translation, for instance migrate cannot be used transitively in Igbo. (or a similar translational solution used). Also, Igbo phrasal verbs will change (be “split”) depending on the particular syntactical environment. This matter should be dealt with extremely carefully.

The examples below contain frequently occurring noun phrases that are preceded by a preposition. Please use this table as a reference.

Procedures and Syntax

In procedural text, which tells the user to perform certain actions in a certain number of steps, the order in which interface terms are to appear in the translation is usually top to bottom (for example, “menu,” “command,” “dialog box,” “dialog box controls”). This order reflects the sequence in which the action needs to be performed, and it should be maintained unless there are technical reasons preventing it.

This convention is less important in normal body text, which is sometimes written in a more personal tone and less formal style, thus allowing the translator to be more creative.

See also sections 4.5.5 and 4.6.2.2.

Descriptors

Use the descriptor (“menu,” “button,” “command,” and so on) only if the original text uses it or if it is needed for clarifying the position of a term in the interface.

Procedural Syntax

In procedural text, which tells the user to perform certain actions in a certain number of steps, the order in which interface terms are to appear in the translation is usually top to bottom (i.e. menu, command, dialog box, dialog box controls). Maintain this sequence unless there are technical reasons preventing it.

Example:

In the "Extras" menu, click "Settings" and then "Music files".

You may come across procedural instructions of the type "To do this and that, click on ...". In body text, you may rearrange such sentences to first mention the action the user needs to do and then the purpose.

Procedural Headings

Procedural headings are very important because they tell users exactly what they are going to do in the steps that follow. Headings should convey as much information as possible about the ensuing text to help readers locate information quickly. If in English the heading begins with a gerund, try to use a nominalized form in Igbo.

Status Bar Messages

Please make sure you adequately capture the meaning of messages when translating.

If you think a source status bar message is ambiguous, query it to make sure you provide the reader with the right information: if you cannot understand it, they are also not certain to. There is nothing more annoying than "help" that doesn't!

A status bar message is information about the active document, a selected command, or any active selected interface item. The messages are shown in the status bar at the bottom of the window when the user has chosen a menu, a command or any other item, or has started a function. Some status bar messages refer to actions being performed or already completed (for example in Microsoft Internet Explorer). Refer to

Figure 1. Example of a typical status bar and status bar message.

Messages reporting that a process is executing usually use a verb in the “-ing” form plus three dots after the text. In Igbo you should choose a verb tense and/or aspect that expresses the ongoing nature of the action.

Difficulties can arise if this convention is not kept in the US text and the status or progress message is not immediately recognizable as such (although sometimes the Resource ID will tell). The standard syntax should be applied to status bar messages wherever possible.

Examples:

Usage of "Select"

Usage of "Click"

Punctuation

Commas and Other Common Punctuation Marks

Please follow the following basic rules for the use of punctuation marks in Igbo. Make sure to include a space after commas, and after periods if it is followed by another sentence. Use one space between sentences.

There are a few important punctuation conventions that need to be observed:

1. The predicates of complex sentences are separated by a comma, whether or not they occur next to each other in the sentence. After the infinitive (om te + verb) as a noun clause no comma is needed.
2. A defining adjectival clause is terminated by a comma, unless two equivalent clauses are linked by “en” or “of”, or, of course, unless it is the final clause of the complex sentence.
3. A non-defining adjectival clause is preceded by a comma before the relative pronoun and is terminated by a comma.
4. A dash (en dash) between words should be preceded and followed by a single space.

Comma vs. Period in Numerals

English uses a period as decimal separator, Igbo usually uses a comma.

Example:
English: 5.25 cm
Igbo: 5,25 cm

English: Letter Landscape 11 x 8.5 in
Igbo: Letter Querformat 11 x 8.5 in

English: 1,526
Igbo: 1 526

In bullet lists, instruction lists, captions and callouts:

• If your translation is longer than the US text, or if you split your translation into several independent sentences, use common sense and insert a period if it improves the Igbo style.

US English uses a period as the decimal separator, while many other languages use a comma. In Igbo a comma is used.

In paper sizes (the last example in the table below) the decimal separator and the abbreviation "in" for inches are kept, since the sizes are US norms and should be represented accordingly.

The “in” as abbreviation for “inch” is not acceptable in Igbo, and should be changed to “dm.” – note the full stop! – which has been the recognized abbreviation for decades. Before independence, Nigeria as part of the British Empire used the imperial measurement system in which “inch = duim” and “in = dm.”.

For thousands, English uses a comma while many other languages use a period (at Mozilla we normally do not use a space for this purpose, but we use a period instead to avoid wrapping problems).

Note that neither a full stop nor a comma may be used for thousands, because both may be interpreted as a decimal separator. A space should be used for thousands and preferably a hard space to avoid wrapping problems.

Note that there should be NO SPACE between the currency symbol and the first digit!

Version Numbers

Version numbers always contain a period (Version 4.2, for example). Please note the following punctuation examples of “Version x.x”:

Examples:

Version numbers are usually also part of version strings, but technically they are not the same. Where possible in Igbo, leave out “weergawe” because it would in most cases require a hyphen to link it to the product name, which will only complicate matters.

Typographic Conventions

Consistent use of typographic conventions in documentation helps users locate and interpret information easily. Generally speaking, the source format should be followed as closely as possible, i.e. terms with a particular formatting in the source should have the same formatting in the translation.

If menu, command, option, etc. names are highlighted by bold print in the source, use bold print for the corresponding translated terms. If menu, command, option, etc. names are put in quotes in the source, use quotes for the corresponding terms in the translation.

Note that in software strings, you must use two double quotes (""xxx"") to denote names within a string. If you only use a single double quotes ("xxx"), this will cause problems with the compilation, as strings are generally denoted by double quotes.

Wizard Names

Abbreviations: N = Noun, A = Adjective (incl. participle used as A), Nv = Verb used as Noun

Appendix

Guidelines for the Localization of Error Messages

The following guidelines do not apply to the translation of FirefoxOS because brevity is more important in FirefoxOS than using long, pleasant sounding idiomatic expressions.

Articles and Pronouns

Verbs

Negation