webtrees - en to en-GB translation catalogue (281 entries)

en: %s BCE
en-GB: %s B.C.

note: I18N: %s=“fifth cousin”, etc.
en: %s three times removed ascending
en-GB: %s thrice removed ascending

note: I18N: %s=“fifth cousin”, etc.
en: %s three times removed descending
en-GB: %s thrice removed descending

note: I18N: BCE=Before the Common Era, for Julian years < 0. See http://en.wikipedia.org/wiki/Common_Era
en: %s&nbsp;BCE
en-GB: %s&nbsp;BC

note: I18N: CE=Common Era, for Julian years > 0. See http://en.wikipedia.org/wiki/Common_Era
en: %s&nbsp;CE
en-GB: AD&nbsp;%s

en: A child may have more than one set of parents. The relationship between the child and the parents can be biological, legal, or based on local culture and tradition. If no pedigree is specified, then a biological relationship will be assumed.
en-GB: A child may have more than one set of parents. The relationship between the child and the parents can be biological, legal or based on local culture and tradition. If no pedigree is specified, then a biological relationship will be assumed.

note: I18N: Description of the “Pending changes” module
en: A list of changes that need to be reviewed by a moderator, and email notifications.
en-GB: A list of changes that need to be reviewed by a moderator, and e-mail notifications.

note: I18N: %1$s is a real-name, %2$s is a username, %3$s is an email address
en: A new user (%1$s) has requested an account (%2$s) and verified an email address (%3$s).
en-GB: A new user (%1$s) has requested an account (%2$s) and verified an e-mail address (%3$s).

en: A password reset link has been sent to “%s”.
en-GB: A password reset link has been sent to ‘%s’.

en: A user will not be able to sign in until both “email verified” and “approved by administrator” are selected.
en-GB: A user will not be able to sign in until both ‘e-mail verified’ and ‘approved by administrator’ are selected.

[ctx: Abbreviation for Persian month: Aban]
en: Aban
en-GB: Ābān

[ctx: GENITIVE]
note: I18N: 8th month in the Persian/Jalali calendar
en: Aban
en-GB: Ābān

[ctx: INSTRUMENTAL]
note: I18N: 8th month in the Persian/Jalali calendar
en: Aban
en-GB: Ābān

[ctx: LOCATIVE]
note: I18N: 8th month in the Persian/Jalali calendar
en: Aban
en-GB: Ābān

[ctx: NOMINATIVE]
note: I18N: 8th month in the Persian/Jalali calendar
en: Aban
en-GB: Ābān

en: Account approval and email verification
en-GB: Account approval and e-mail verification

en: Add a favorite
en-GB: Add a favourite

note: I18N: Name of a country or state
en: Aland Islands
en-GB: Åland Islands

note: I18N: Description of the “CKEditor” module. WYSIWYG = “what you see is what you get”
en: Allow other modules to edit text using a “WYSIWYG” editor, instead of using HTML codes.
en-GB: Allow other modules to edit text using a ‘WYSIWYG’ editor, instead of using HTML codes.

note: I18N: Description of the “Album” module
en: An alternative to the “media” tab, and an enhanced image viewer.
en-GB: An alternative to the ‘media’ tab, and an enhanced image viewer.

en: Are you sure you want to delete “%s”?
en-GB: Are you sure you want to delete ‘%s’?

en: Are you sure you want to remove this item from your list of favorites?
en-GB: Are you sure you want to remove this item from your list of favourites?

note: I18N: Location of an LDS church temple
en: Asuncion, Paraguay
en-GB: Asunción, Paraguay

[ctx: Abbreviation for Persian month: Azar]
en: Azar
en-GB: Āzar

[ctx: GENITIVE]
note: I18N: 9th month in the Persian/Jalali calendar
en: Azar
en-GB: Āzar

[ctx: INSTRUMENTAL]
note: I18N: 9th month in the Persian/Jalali calendar
en: Azar
en-GB: Āzar

[ctx: LOCATIVE]
note: I18N: 9th month in the Persian/Jalali calendar
en: Azar
en-GB: Āzar

[ctx: NOMINATIVE]
note: I18N: 9th month in the Persian/Jalali calendar
en: Azar
en-GB: Āzar

en: Birth places
en-GB: Birthplaces

note: I18N: Location of an LDS church temple
en: Bogota, Colombia
en-GB: Bogotá, Colombia

en: Change the “Home page” blocks
en-GB: Change the ‘Home page’ blocks

en: Change the “My page” blocks
en-GB: Change the ‘My page’ blocks

note: I18N: Location of an LDS church temple
en: Ciudad Juarez, Mexico
en-GB: Ciudad Juárez, Mexico

en: Clean up data folder
en-GB: Clean-up data folder

note: I18N: Location of an LDS church temple
en: Colonia Juarez, Mexico
en-GB: Colonia Juárez, Mexico

note: I18N: Location of an LDS church temple
en: Cordoba, Argentina
en-GB: Córdoba, Argentina

note: I18N: Description of a “Data fix” module
en: Correct NAME records of the form “John/DOE/” or “John /DOE”, as produced by older genealogy programs.
en-GB: Correct NAME records of the form ‘Joe/BLOGGS/’ or ‘Joe /BLOGGS’, as produced by older genealogy programs.

note: I18N: Name of a country or state
en: Cote d’Ivoire
en-GB: Côte d’Ivoire

en: Create, update, and delete a family tree for every GEDCOM file in the data folder.
en-GB: Create, update and delete a family tree for every GEDCOM file in the data folder.

en: Customize this page
en-GB: Customise this page

note: I18N: http://en.wikipedia.org/wiki/Daitch–Mokotoff_Soundex
en: Daitch-Mokotoff
en-GB: Daitch–Mokotoff

en: Date of naturalization
en-GB: Date of naturalisation

[ctx: GENITIVE]
note: I18N: http://en.wikipedia.org/wiki/Dhu_al-Hijjah
en: Dhu al-Hijjah
en-GB: Dhū al-Ḥijjah

[ctx: INSTRUMENTAL]
note: I18N: http://en.wikipedia.org/wiki/Dhu_al-Hijjah
en: Dhu al-Hijjah
en-GB: Dhū al-Ḥijjah

[ctx: LOCATIVE]
note: I18N: http://en.wikipedia.org/wiki/Dhu_al-Hijjah
en: Dhu al-Hijjah
en-GB: Dhū al-Ḥijjah

[ctx: NOMINATIVE]
note: I18N: http://en.wikipedia.org/wiki/Dhu_al-Hijjah
en: Dhu al-Hijjah
en-GB: Dhū al-Ḥijjah

[ctx: GENITIVE]
note: I18N: http://en.wikipedia.org/wiki/Dhu_al-Qi%27dah
en: Dhu al-Qi’dah
en-GB: Dhū al-Qiʿdah

[ctx: INSTRUMENTAL]
note: I18N: http://en.wikipedia.org/wiki/Dhu_al-Qi%27dah
en: Dhu al-Qi’dah
en-GB: Dhū al-Qiʿdah

[ctx: LOCATIVE]
note: I18N: http://en.wikipedia.org/wiki/Dhu_al-Qi%27dah
en: Dhu al-Qi’dah
en-GB: Dhū al-Qiʿdah

[ctx: NOMINATIVE]
note: I18N: http://en.wikipedia.org/wiki/Dhu_al-Qi%27dah
en: Dhu al-Qi’dah
en-GB: Dhū al-Qiʿdah

note: I18N: Description of the “Favorites” module
en: Display and manage a family tree’s favorite pages.
en-GB: Display and manage a family tree’s favourite pages.

note: I18N: Description of the “Favorites” module
en: Display and manage a user’s favorite pages.
en-GB: Display and manage a user’s favourite pages.

note: I18N: LDS sealing status; see http://en.wikipedia.org/wiki/Sealing_(Latter_Day_Saints)
en: Do not seal, previous sealing canceled
en-GB: Do not seal, previous sealing cancelled

note: I18N: LDS sealing status; see http://en.wikipedia.org/wiki/Sealing_(Latter_Day_Saints)
en: Do not seal: unauthorized
en-GB: Do not seal: unauthorised

en: Duplicate email address. A user with that email already exists.
en-GB: Duplicate e-mail address. A user with that e-mail already exists.

en: Each source records specific events, generally for a given date range and for a place jurisdiction. For example a Census records census events and church records record birth, marriage, and death events.<br><br>Select the events that are recorded by this source from the list of events provided. The date should be specified in a range format such as <i>FROM 1900 TO 1910</i>. The place jurisdiction is the name of the lowest jurisdiction that encompasses all lower-level places named in this source. For example, “Oneida, Idaho, USA” would be used as a source jurisdiction place for events occurring in the various towns within Oneida County. “Idaho, USA” would be the source jurisdiction place if the events recorded took place not only in Oneida County but also in other counties in Idaho.
en-GB: Each source records specific events, generally for a given date range and for a place jurisdiction. For example a Census records census events and church records record birth, marriage and death events.<br><br>Select the events that are recorded by this source from the list of events provided. The date should be specified in a range format such as <i>FROM 1900 TO 1910</i>. The place jurisdiction is the name of the lowest jurisdiction that encompasses all lower-level places named in this source. For example, ‘Oneida, Idaho, USA’ would be used as a source jurisdiction place for events occurring in the various towns within Oneida County. ‘Idaho, USA’ would be the source jurisdiction place if the events recorded took place not only in Oneida County but also in other counties in Idaho.

en: Each user account has an option to “automatically accept changes”. When this is enabled, any changes made by that user are saved immediately. Many administrators enable this for their own user account.
en-GB: Each user account has an option to ‘automatically accept changes’. When this is enabled, any changes made by that user are saved immediately. Many administrators enable this for their own user account.

en: Edit the gender
en-GB: Edit the sex

en: Email
en-GB: E-mail

note: I18N: gedcom tag EMAIL I18N: gedcom tag _EMAIL
en: Email address
en-GB: E-mail address

en: Email verified
en-GB: E-mail verified

en: Enter an optional note about this favorite
en-GB: Enter an optional note about this favourite

en: Exclude individuals with “%s” as a married name
en-GB: Exclude individuals with ‘%s’ as a married name

note: I18N: gedcom tag _EYEC
en: Eye color
en-GB: Eye colour

note: I18N: FAQ = “Frequently Asked Question”
en: FAQs are lists of questions and answers, which allow you to explain the site’s rules, policies, and procedures to your visitors. Questions are typically concerned with privacy, copyright, user-accounts, unsuitable content, requirement for source-citations, etc.
en-GB: FAQs are lists of questions and answers, which allow you to explain the site’s rules, policies and procedures to your visitors. Questions are typically concerned with privacy, copyright, user-accounts, unsuitable content, requirement for source-citations, etc.

note: I18N: “rada” is an Arabic word, pronounced “ra DAH”. It is child-to-parent pedigree, established by wet-nursing.
en: Family with rada parents
en-GB: Family with radāʿ parents

note: I18N: Name of a module
en: Favorites
en-GB: Favourites

en: Filenames are not allowed to contain the character “%s”.
en-GB: Filenames are not allowed to contain the character ‘%s’.

en: Filenames are not allowed to have the extension “%s”.
en-GB: Filenames are not allowed to have the extension ‘%s’.

[ctx: GENITIVE]
note: I18N: a month in the French republican calendar
en: Floreal
en-GB: Floréal

[ctx: INSTRUMENTAL]
note: I18N: a month in the French republican calendar
en: Floreal
en-GB: Floréal

[ctx: LOCATIVE]
note: I18N: a month in the French republican calendar
en: Floreal
en-GB: Floréal

[ctx: NOMINATIVE]
note: I18N: a month in the French republican calendar
en: Floreal
en-GB: Floréal

en: Follow this link to verify your email address.
en-GB: Follow this link to verify your e-mail address.

note: I18N: gedcom tag SEX
en: Gender
en-GB: Sex

note: I18N: gedcom tag _HAIR
en: Hair color
en-GB: Hair colour

note: I18N: Help text for the “Language” configuration setting
en: If a visitor to the website has not selected a preferred language in their browser preferences, or they have selected an unsupported language, then this language will be used. Typically this applies to search engines.
en-GB: If a visitor to the website has not specified a preferred language in their browser configuration, or they have specified an unsupported language, then this language will be used. Typically, this setting applies to search engines.

en: If an administrator creates a user account, the verification email is not sent, and the email must be verified manually.
en-GB: If an administrator creates a user account, the verification e-mail is not sent, and the e-mail must be verified manually.

note: I18N: Help text for the “Age at which to assume an individual is dead” configuration setting
en: If this individual has any events other than death, burial, or cremation more recent than this number of years, they are considered to be “alive”. Children’s birth dates are considered to be such events for this purpose.
en-GB: If this individual has any events other than death, burial or cremation more recent than this number of years, they are considered to be ‘alive’. Children’s birth dates are considered to be such events for this purpose.

en: If you have a large number of media files, you can organize them into folders and subfolders.
en-GB: If you have a large number of media files, you can organise them into folders and subfolders.

en: If you have created media objects in webtrees, and have subsequently edited this GEDCOM file using genealogy software that deletes media objects, then select this option to merge the current media objects with the new GEDCOM file.
en-GB: If you have created media objects in webtrees, and have subsequently edited this GEDCOM file using software that deletes media objects, then tick this box to merge the current media objects with the new GEDCOM file.

en: If you select a different folder, you must also move all files (except config.ini.php, index.php, and .htaccess) from the existing folder to the new folder.
en-GB: If you select a different folder, you must also move all files (except config.ini.php, index.php and .htaccess) from the existing folder to the new folder.

en: In a family tree, each record has an internal reference number (called an “XREF”) such as “F123” or “R14”.
en-GB: In a family tree, each record has an internal reference number (called an ‘XREF’) such as ‘F123’ or ‘R14’.

en: In many cultures it is customary to have a traditional name spelled in the traditional characters and also a romanized version of the name as it would be spelled or pronounced in languages based on the Latin alphabet, such as English.<br><br>If you prefer to use a non-Latin alphabet such as Hebrew, Greek, Russian, Chinese, or Arabic to enter the name in the standard name fields, then you can use this field to enter the same name using the Latin alphabet. Both versions of the name will appear in lists and charts.<br><br>Although this field is labeled “Romanized”, it is not restricted to containing only characters based on the Latin alphabet. This might be of use with Japanese names, where three different alphabets may occur.
en-GB: In many cultures it is customary to have a traditional name spelled in the traditional characters and also a romanised version of the name as it would be spelled or pronounced in languages based on the Latin alphabet, such as English.<br><br>If you prefer to use a non-Latin alphabet such as Hebrew, Greek, Russian, Chinese or Arabic to enter the name in the standard name fields, then you can use this field to enter the same name using the Latin alphabet. Both versions of the name will appear in lists and charts.<br><br>Although this field is labelled ‘Romanised’, it is not restricted to containing only characters based on the Latin alphabet. This might be of use with Japanese names, where three different alphabets may occur.

en: In many cultures it is customary to have a traditional name spelled in the traditional characters and also a romanized version of the name as it would be spelled or pronounced in languages based on the Latin alphabet, such as English.<br><br>If you prefer to use the Latin alphabet to enter the name in the standard name fields, then you can use this field to enter the same name in the non-Latin alphabet such as Greek, Hebrew, Russian, Arabic, or Chinese. Both versions of the name will appear in lists and charts.<br><br>Although this field is labeled “Hebrew”, it is not restricted to containing only Hebrew characters.
en-GB: In many cultures it is customary to have a traditional name spelled in the traditional characters and also a romanised version of the name as it would be spelled or pronounced in languages based on the Latin alphabet, such as English.<br><br>If you prefer to use the Latin alphabet to enter the name in the standard name fields, then you can use this field to enter the same name in the non-Latin alphabet such as Greek, Hebrew, Russian, Arabic or Chinese. Both versions of the name will appear in lists and charts.<br><br>Although this field is labelled ‘Hebrew’, it is not restricted to containing only Hebrew characters.

note: I18N: "thumbs" is fixed text.  Do not change it.
en: In webtrees version 1, you could add custom thumbnails to media objects by creating files in the “thumbs” folders.
en-GB: In webtrees version 1, you could add custom thumbnails to media objects by creating files in the ‘thumbs’ folders.

en: Include individuals with “%s” as a married name
en-GB: Include individuals with ‘%s’ as a married name

en: Internal messaging with emails
en-GB: Internal messaging with e-mail

note: I18N: This should be a common/default/placeholder name of an individual. Put slashes around the surname.
en: John /DOE/
en-GB: Joe /BLOGGS/

[ctx: GENITIVE]
note: I18N: http://en.wikipedia.org/wiki/Jumada_al-awwal
en: Jumada al-awwal
en-GB: Jumādá al-awwal

[ctx: INSTRUMENTAL]
note: I18N: http://en.wikipedia.org/wiki/Jumada_al-awwal
en: Jumada al-awwal
en-GB: Jumādá al-awwal

[ctx: LOCATIVE]
note: I18N: http://en.wikipedia.org/wiki/Jumada_al-awwal
en: Jumada al-awwal
en-GB: Jumādá al-awwal

[ctx: NOMINATIVE]
note: I18N: http://en.wikipedia.org/wiki/Jumada_al-awwal
en: Jumada al-awwal
en-GB: Jumādá al-awwal

[ctx: GENITIVE]
note: I18N: http://en.wikipedia.org/wiki/Jumada_al-thani
en: Jumada al-thani
en-GB: Jumādá al-thānī

[ctx: INSTRUMENTAL]
note: I18N: http://en.wikipedia.org/wiki/Jumada_al-thani
en: Jumada al-thani
en-GB: Jumādá al-thānī

[ctx: LOCATIVE]
note: I18N: http://en.wikipedia.org/wiki/Jumada_al-thani
en: Jumada al-thani
en-GB: Jumādá al-thānī

[ctx: NOMINATIVE]
note: I18N: http://en.wikipedia.org/wiki/Jumada_al-thani
en: Jumada al-thani
en-GB: Jumādá al-thānī

note: I18N: A configuration setting
en: Keep the existing “last change” information
en-GB: Keep the existing ‘last change’ information

[ctx: GENITIVE]
note: I18N: 3rd month in the Persian/Jalali calendar
en: Khordad
en-GB: Khordād

[ctx: INSTRUMENTAL]
note: I18N: 3rd month in the Persian/Jalali calendar
en: Khordad
en-GB: Khordād

[ctx: LOCATIVE]
note: I18N: 3rd month in the Persian/Jalali calendar
en: Khordad
en-GB: Khordād

[ctx: NOMINATIVE]
note: I18N: 3rd month in the Persian/Jalali calendar
en: Khordad
en-GB: Khordād

en: Last email reminder was sent
en-GB: Last e-mail reminder was sent

note: I18N: Help text for the “GEDCOM errors” configuration setting
en: Many genealogy programs create GEDCOM files with custom tags, and webtrees understands most of them. When unrecognized tags are found, this option lets you choose whether to ignore them or display a warning message.
en-GB: Many genealogy programs create GEDCOM files with custom tags, and webtrees understands most of them. When unrecognised tags are found, this option lets you choose whether to ignore them or display a warning message.

note: I18N: gedcom tag MARL
en: Marriage license
en-GB: Marriage licence

note: I18N: Location of an LDS church temple
en: Merida, Mexico
en-GB: Mérida, Mexico

note: I18N: Location of an LDS church temple
en: Montreal, Quebec, Canada
en-GB: Montréal, Québec, Canada

[ctx: GENITIVE]
note: I18N: 5th month in the Persian/Jalali calendar
en: Mordad
en-GB: Mordād

[ctx: INSTRUMENTAL]
note: I18N: 5th month in the Persian/Jalali calendar
en: Mordad
en-GB: Mordād

[ctx: LOCATIVE]
note: I18N: 5th month in the Persian/Jalali calendar
en: Mordad
en-GB: Mordād

[ctx: NOMINATIVE]
note: I18N: 5th month in the Persian/Jalali calendar
en: Mordad
en-GB: Mordād

en: Most mail servers require a valid email address.
en-GB: Most mail servers require a valid e-mail address.

[ctx: GENITIVE]
note: I18N: http://en.wikipedia.org/wiki/Muharram
en: Muharram
en-GB: Muḥarram

[ctx: INSTRUMENTAL]
note: I18N: http://en.wikipedia.org/wiki/Muharram
en: Muharram
en-GB: Muḥarram

[ctx: LOCATIVE]
note: I18N: http://en.wikipedia.org/wiki/Muharram
en: Muharram
en-GB: Muḥarram

[ctx: NOMINATIVE]
note: I18N: http://en.wikipedia.org/wiki/Muharram
en: Muharram
en-GB: Muḥarram

note: I18N: gedcom tag NATU
en: Naturalization
en-GB: Naturalisation

en: Next email reminder will be sent after
en-GB: Next e-mail reminder will be sent after

[ctx: GENITIVE]
note: I18N: a month in the French republican calendar
en: Nivose
en-GB: Nivôse

[ctx: INSTRUMENTAL]
note: I18N: a month in the French republican calendar
en: Nivose
en-GB: Nivôse

[ctx: LOCATIVE]
note: I18N: a month in the French republican calendar
en: Nivose
en-GB: Nivôse

[ctx: NOMINATIVE]
note: I18N: a month in the French republican calendar
en: Nivose
en-GB: Nivôse

note: I18N: Location of an LDS church temple
en: Nuku’Alofa, Tonga
en-GB: Nukuʻalofa, Tonga

en: Oops! The webserver is unable to connect to the database server. It could be busy, undergoing maintenance, or simply broken. You should <a href="index.php">try again</a> in a few minutes or contact the website administrator.
en-GB: Oops! The webserver is unable to connect to the database server. It could be busy, undergoing maintenance or simply broken. You should <a href="index.php">try again</a> in a few minutes or contact the website administrator.

en: Other genealogy applications might not recognize this data.
en-GB: Other genealogy applications might not recognise this data.

en: Passwords must be at least 8 characters long and are case-sensitive, so that “secret” is different from “SECRET”.
en-GB: Passwords must be at least 8 characters long and are case-sensitive, so that ‘secret’ is different to ‘SECRET’.

en: Pending changes are only shown when your account has permission to edit. When you sign out, you will no longer be able to see them. Also, pending changes are only shown on certain pages. For example, they are not shown in lists, reports, or search results.
en-GB: Pending changes are only shown when your account has permission to edit. When you sign out, you will no longer be able to see them. Also, pending changes are only shown on certain pages. For example, they are not shown in lists, reports or search results.

en: Place names should be entered as a comma-separated list, starting with the smallest place and ending with the country. For example, “Westminster, London, England”.
en-GB: Place names should be entered as a comma-separated list, starting with the smallest place and ending with the country. For example, ‘Westminster, London, England’.

en: Place of naturalization
en-GB: Place of naturalisation

en: Please enter a valid email address.
en-GB: Please enter a valid e-mail address.

[ctx: GENITIVE]
note: I18N: a month in the French republican calendar
en: Pluviose
en-GB: Pluviôse

[ctx: INSTRUMENTAL]
note: I18N: a month in the French republican calendar
en: Pluviose
en-GB: Pluviôse

[ctx: LOCATIVE]
note: I18N: a month in the French republican calendar
en: Pluviose
en-GB: Pluviôse

[ctx: NOMINATIVE]
note: I18N: a month in the French republican calendar
en: Pluviose
en-GB: Pluviôse

note: I18N: gedcom tag POST
en: Postal code
en-GB: Post code

en: Preferences exist for the module “%s”, but this module no longer exists.
en-GB: Preferences exist for the module ‘%s’, but this module no longer exists.

note: I18N: Location of an LDS church temple
en: Provo City Center, Utah, United States
en-GB: Provo City Centre, Utah, United States

[ctx: GENITIVE]
note: I18N: http://en.wikipedia.org/wiki/Rabi%27_al-awwal
en: Rabi’ al-awwal
en-GB: Rabīʿ al-awwal

[ctx: INSTRUMENTAL]
note: I18N: http://en.wikipedia.org/wiki/Rabi%27_al-awwal
en: Rabi’ al-awwal
en-GB: Rabīʿ al-awwal

[ctx: LOCATIVE]
note: I18N: http://en.wikipedia.org/wiki/Rabi%27_al-awwal
en: Rabi’ al-awwal
en-GB: Rabīʿ al-awwal

[ctx: NOMINATIVE]
note: I18N: http://en.wikipedia.org/wiki/Rabi%27_al-awwal
en: Rabi’ al-awwal
en-GB: Rabīʿ al-awwal

[ctx: GENITIVE]
note: I18N: http://en.wikipedia.org/wiki/Rabi%27_al-thani
en: Rabi’ al-thani
en-GB: Rabīʿ al-thānī

[ctx: INSTRUMENTAL]
note: I18N: http://en.wikipedia.org/wiki/Rabi%27_al-thani
en: Rabi’ al-thani
en-GB: Rabīʿ al-thānī

[ctx: LOCATIVE]
note: I18N: http://en.wikipedia.org/wiki/Rabi%27_al-thani
en: Rabi’ al-thani
en-GB: Rabīʿ al-thānī

[ctx: NOMINATIVE]
note: I18N: http://en.wikipedia.org/wiki/Rabi%27_al-thani
en: Rabi’ al-thani
en-GB: Rabīʿ al-thānī

note: I18N: This is an Arabic word, pronounced “ra DAH”. It is child-to-parent pedigree, established by wet-nursing.
en: Rada
en-GB: Radāʿ

en: Reminder email frequency (days)
en-GB: Reminder e-mail frequency (days)

en: Research tasks are stored using the custom GEDCOM tag “_TODO”. Other genealogy applications may not recognize this tag.
en-GB: Research tasks are stored using the custom GEDCOM tag ‘_TODO’. Other genealogy applications may not recognise this tag.

note: I18N: Name of a country or state
en: Reunion
en-GB: Réunion

note: I18N: gedcom tag ROMN
en: Romanized
en-GB: Romanised

en: Romanized place
en-GB: Romanised place

en: Romanized title
en-GB: Romanised title

[ctx: GENITIVE]
note: I18N: http://en.wikipedia.org/wiki/Safar
en: Safar
en-GB: Ṣafar

[ctx: INSTRUMENTAL]
note: I18N: http://en.wikipedia.org/wiki/Safar
en: Safar
en-GB: Ṣafar

[ctx: LOCATIVE]
note: I18N: http://en.wikipedia.org/wiki/Safar
en: Safar
en-GB: Ṣafar

[ctx: NOMINATIVE]
note: I18N: http://en.wikipedia.org/wiki/Safar
en: Safar
en-GB: Ṣafar

note: I18N: Location of an LDS church temple
en: San Jose, Costa Rica
en-GB: San José, Costa Rica

note: I18N: Location of an LDS church temple
en: Sao Paulo, Brazil
en-GB: São Paulo, Brazil

note: I18N: Name of a country or state
en: Sao Tome and Principe
en-GB: São Tomé and Príncipe

note: I18N: LDS sealing status; see http://en.wikipedia.org/wiki/Sealing_(Latter_Day_Saints)
en: Sealing canceled (divorce)
en-GB: Sealing cancelled (divorce)

note: I18N: Label for a configuration option
en: Send out reminder emails
en-GB: Send out reminder e-mails

en: Sending email
en-GB: Sending e-mail

note: I18N: You need to:
en: Set the status to “approved”.
en-GB: Set the status to ‘approved’.

note: I18N: Help text for the “Allow users to see raw GEDCOM records” configuration setting
en: Setting this to <b>Yes</b> will place links on individuals, sources, and families to let users bring up another window containing the raw data taken right out of the GEDCOM file.
en-GB: Setting this to <b>Yes</b> will place links on individuals, sources and families to let users bring up another window containing the raw data taken right out of the GEDCOM file.

[ctx: GENITIVE]
note: I18N: 6th month in the Persian/Jalali calendar
en: Shahrivar
en-GB: Shahrīvar

[ctx: INSTRUMENTAL]
note: I18N: 6th month in the Persian/Jalali calendar
en: Shahrivar
en-GB: Shahrīvar

[ctx: LOCATIVE]
note: I18N: 6th month in the Persian/Jalali calendar
en: Shahrivar
en-GB: Shahrīvar

[ctx: NOMINATIVE]
note: I18N: 6th month in the Persian/Jalali calendar
en: Shahrivar
en-GB: Shahrīvar

note: I18N: A configuration setting
en: Show acceptable use agreement on “Request a new user account” page
en-GB: Show acceptable use agreement on ‘Request a new user account’ page

en: Show only individuals for whom the gender is not known.
en-GB: Show only individuals for whom the sex is not known.

en: Show only individuals, events, or all
en-GB: Show only individuals, events or all

en: Show “leaves” couples or individuals. These are individuals who are alive but have no children recorded in the database.
en-GB: Show ‘leaves’ couples or individuals. These are individuals who are alive but have no children recorded in the database.

en: Show “roots” couples or individuals. These individuals may also be called “patriarchs”. They are individuals who have no parents recorded in the database.
en-GB: Show ‘roots’ couples or individuals. These people may also be called ‘patriarchs’. They are individuals who have no parents recorded in the database.

note: I18N: The www.sitemaps.org site is translated into many languages (e.g. http://www.sitemaps.org/fr/) - choose an appropriate URL.
en: Sitemaps are a way for webmasters to tell search engines about the pages on a website that are available for crawling. All major search engines support sitemaps. For more information, see <a href="http://www.sitemaps.org/">www.sitemaps.org</a>.
en-GB: Sitemaps are a way for webmasters to tell search engines about the pages on a website that are available for crawling. All major search engines support sitemaps. For more information, see <a href="http://www.sitemaps.org/en_GB/">www.sitemaps.org</a>.

note: I18N: Help text for the “Fact icons” configuration setting
en: Some themes can display icons on the “Facts and events” tab.
en-GB: Some themes can display icons on the ‘Facts and events’ tab.

note: I18N: In the Lithuanian surname tradition, ...
en: Surnames are inflected to indicate an individual’s gender and marital status.
en-GB: Surnames are inflected to indicate an individual’s sex and marital status.

note: I18N: In the Polish surname tradition, ...
en: Surnames are inflected to indicate an individual’s gender.
en-GB: Surnames are inflected to indicate an individual’s sex.

en: Synchronize family trees with GEDCOM files
en-GB: Synchronise family trees with GEDCOM files

en: The GEDCOM file “%s” has been imported.
en-GB: The GEDCOM file ‘%s’ has been imported.

en: The PHP extension “%s” is not installed.
en-GB: The PHP extension ‘%s’ is not installed.

en: The PHP function “%1$s” is disabled.
en-GB: The PHP function ‘%1$s’ is disabled.

en: The PHP.INI setting “%1$s” is disabled.
en-GB: The PHP.INI setting ‘%1$s’ is disabled.

en: The PHP.INI setting “%1$s” is enabled.
en-GB: The PHP.INI setting ‘%1$s’ is enabled.

note: I18N: %s is the name of a genealogy record
en: The changes to “%s” have been accepted.
en-GB: The changes to ‘%s’ have been accepted.

note: I18N: %s is the name of a genealogy record
en: The changes to “%s” have been rejected.
en-GB: The changes to ‘%s’ have been rejected.

en: The details for “%s” have been updated.
en-GB: The details for ‘%s’ have been updated.

en: The family tree “%s” already exists.
en-GB: The family tree ‘%s’ already exists.

en: The family tree “%s” has been created.
en-GB: The family tree ‘%s’ has been created.

note: I18N: %s is the name of a family tree
en: The family tree “%s” has been deleted.
en-GB: The family tree ‘%s’ has been deleted.

note: I18N: %s is the name of a family tree
en: The family tree “%s” will be shown to visitors when they first arrive at this website.
en-GB: The family tree ‘%s’ will be shown to visitors when they first arrive at this website.

note: I18N: %s is the name of a family group, e.g. “Husband name + Wife name”
en: The family “%s” has been deleted because it only has one member.
en-GB: The family ‘%s’ has been deleted, because it only has one member.

note: I18N: %s is a filename
en: The file “%s” does not exist.
en-GB: The file ‘%s’ does not exist.

en: The folder “%s” does not exist.
en-GB: The folder ‘%s’ does not exist.

note: I18N: %s are names of records, such as sources, repositories or individuals
en: The link from “%1$s” to “%2$s” has been deleted.
en-GB: The link from ‘%1$s’ to ‘%2$s’ has been deleted.

en: The link from “%1$s” to “%2$s” has been updated.
en-GB: The link from ‘%1$s’ to ‘%2$s’ has been updated.

en: The module “%s” has been disabled.
en-GB: The module ‘%s’ has been disabled.

en: The module “%s” has been enabled.
en-GB: The module ‘%s’ has been enabled.

en: The new user will be asked to confirm their email address before the account is created.
en-GB: The new user will be asked to confirm their e-mail address before the account is created.

en: The password reset link has expired.
en-GB: The password-reset link has expired.

en: The preferences for the family tree “%s” have been updated.
en-GB: The preferences for the family tree ‘%s’ have been updated.

en: The preferences for the module “%s” have been deleted.
en-GB: The preferences for the module ‘%s’ have been deleted.

en: The preferences for the module “%s” have been updated.
en-GB: The preferences for the module ‘%s’ have been updated.

en: The records “%1$s” and “%2$s” have been merged.
en-GB: The records ‘%1$s’ and ‘%2$s’ have been merged.

note: I18N: An XREF is the identification number used in GEDCOM files.
en: The two family trees have %1$s record which uses the same “XREF”. | The two family trees have %1$s records which use the same “XREF”.
en-GB[0]: The two family trees have %1$s record which uses the same ‘XREF’.
en-GB[1]: The two family trees have %1$s records which use the same ‘XREF’.

en: The user has been sent an email with the information necessary to confirm the access request.
en-GB: The user has been sent an e-mail with the information necessary to confirm the access request.

en: There is no user account with the email “%s”.
en-GB: There is no user account with the e-mail ‘%s’.

en: These cookies are “essential”, and do not require consent.
en-GB: These cookies are ‘essential’, and do not require consent.

en: This account has not been verified. Please check your email for a verification message.
en-GB: This account has not been verified. Please check your e-mail for a verification message.

en: This block will show editors a list of records with pending changes that need to be reviewed by a moderator. It also generates daily emails to moderators whenever pending changes exist.
en-GB: This block will show editors a list of records with pending changes that need to be reviewed by a moderator. It also generates daily e-mails to moderators whenever pending changes exist.

en: This email address will be used to send password reminders, website notifications, and messages from other family members who are registered on the website.
en-GB: This e-mail address will be used to send password reminders, website notifications and messages from other family members who are registered on the website.

en: This family tree has %s record which uses the same “XREF” as another family tree. | This family tree has %s records which use the same “XREF” as another family tree.
en-GB[0]: This family tree has %s record which uses the same ‘XREF’ as another family tree.
en-GB[1]: This family tree has %s records which use the same ‘XREF’ as another family tree.

note: I18N: Help text for the “Advanced name facts” configuration setting
en: This is a comma separated list of GEDCOM fact tags that will be shown on the add/edit name form. If you use non-Latin alphabets such as Hebrew, Greek, Cyrillic, or Arabic, you may want to add tags such as _HEB, ROMN, FONE, etc. to allow you to store names in several different alphabets.
en-GB: This is a comma separated list of GEDCOM fact tags that will be shown on the add/edit name form. If you use non-Latin alphabets such as Hebrew, Greek, Cyrillic or Arabic, you may want to add tags such as _HEB, ROMN, FONE, etc. to allow you to store names in several different alphabets.

note: I18N: Help text for the “Facts for new individuals” configuration setting
en: This is a comma separated list of GEDCOM fact tags that will be shown when adding a new individual. For example, if BIRT is in the list, fields for birth date and birth place will be shown on the form.
en-GB: This is a comma separated list of GEDCOM fact tags that will be shown when adding a new individual. For example, if BIRT is in the list, fields for birthdate and birthplace will be shown on the form.

note: I18N: Help text for the “Advanced place name facts” configuration setting
en: This is a comma separated list of GEDCOM fact tags that will be shown when you add or edit place names. If you use non-Latin alphabets such as Hebrew, Greek, Cyrillic, or Arabic, you may want to add tags such as _HEB, ROMN, FONE, etc. to allow you to store place names in several different alphabets.
en-GB: This is a comma separated list of GEDCOM fact tags that will be shown when you add or edit place names. If you use non-Latin alphabets such as Hebrew, Greek, Cyrillic or Arabic, you may want to add tags such as _HEB, ROMN, FONE, etc. to allow you to store place names in several different alphabets.

note: I18N: Help text for the “All family facts” configuration setting
en: This is the list of GEDCOM facts that your users can add to families. You can modify this list by removing or adding fact names, even custom ones, as necessary. Fact names that appear in this list must not also appear in the “Unique family facts” list.
en-GB: This is the list of GEDCOM facts that your users can add to families. You can modify this list by removing or adding fact names, even custom ones, as necessary. Fact names that appear in this list must not also appear in the ‘Unique family facts’ list.

note: I18N: Help text for the “All individual facts” configuration setting
en: This is the list of GEDCOM facts that your users can add to individuals. You can modify this list by removing or adding fact names, even custom ones, as necessary. Fact names that appear in this list must not also appear in the “Unique individual facts” list.
en-GB: This is the list of GEDCOM facts that your users can add to individuals. You can modify this list by removing or adding fact names, even custom ones, as necessary. Fact names that appear in this list must not also appear in the ‘Unique individual facts’ list.

note: I18N: Help text for the “All repository facts” configuration setting
en: This is the list of GEDCOM facts that your users can add to repositories. You can modify this list by removing or adding fact names, even custom ones, as necessary. Fact names that appear in this list must not also appear in the “Unique repository facts” list.
en-GB: This is the list of GEDCOM facts that your users can add to repositories. You can modify this list by removing or adding fact names, even custom ones, as necessary. Fact names that appear in this list must not also appear in the ‘Unique repository facts’ list.

note: I18N: Help text for the “All source facts” configuration setting
en: This is the list of GEDCOM facts that your users can add to sources. You can modify this list by removing or adding fact names, even custom ones, as necessary. Fact names that appear in this list must not also appear in the “Unique source facts” list.
en-GB: This is the list of GEDCOM facts that your users can add to sources. You can modify this list by removing or adding fact names, even custom ones, as necessary. Fact names that appear in this list must not also appear in the ‘Unique source facts’ list.

note: I18N: Help text for the “Unique family facts” configuration setting
en: This is the list of GEDCOM facts that your users can only add once to families. For example, if MARR is in this list, users will not be able to add more than one MARR record to a family. Fact names that appear in this list must not also appear in the “All family facts” list.
en-GB: This is the list of GEDCOM facts that your users can only add once to families. For example, if MARR is in this list, users will not be able to add more than one MARR record to a family. Fact names that appear in this list must not also appear in the ‘All family facts’ list.

note: I18N: Help text for the “Unique individual facts” configuration setting
en: This is the list of GEDCOM facts that your users can only add once to individuals. For example, if BIRT is in this list, users will not be able to add more than one BIRT record to an individual. Fact names that appear in this list must not also appear in the “All individual facts” list.
en-GB: This is the list of GEDCOM facts that your users can only add once to individuals. For example, if BIRT is in this list, users will not be able to add more than one BIRT record to an individual. Fact names that appear in this list must not also appear in the ‘All individual facts’ list.

note: I18N: Help text for the “Unique repository facts” configuration setting
en: This is the list of GEDCOM facts that your users can only add once to repositories. For example, if NAME is in this list, users will not be able to add more than one NAME record to a repository. Fact names that appear in this list must not also appear in the “All repository facts” list.
en-GB: This is the list of GEDCOM facts that your users can only add once to repositories. For example, if NAME is in this list, users will not be able to add more than one NAME record to a repository. Fact names that appear in this list must not also appear in the ‘All repository facts’ list.

note: I18N: Help text for the “Unique source facts” configuration setting
en: This is the list of GEDCOM facts that your users can only add once to sources. For example, if TITL is in this list, users will not be able to add more than one TITL record to a source. Fact names that appear in this list must not also appear in the “All source facts” list.
en-GB: This is the list of GEDCOM facts that your users can only add once to sources. For example, if TITL is in this list, users will not be able to add more than one TITL record to a source. Fact names that appear in this list must not also appear in the ‘All source facts’ list.

note: I18N: Help text for the “Server name” site configuration setting
en: This is the name of the SMTP server. “localhost” means that the mail service is running on the same computer as your web server.
en-GB: This is the name of the SMTP server. ‘localhost’ means that the mail service is running on the same computer as your web server.

note: I18N: Help text for the “Sender name” site configuration setting
en: This name is used in the “From” field, when sending automatic emails from this server.
en-GB: This name is used in the ‘From’ field, when sending automatic e-mails from this server.

note: I18N: Help text for the “Show private relationships” configuration setting
en: This option will retain family links in private records. This means that you will see empty “private” boxes on the pedigree chart and on other charts with private individuals.
en-GB: This option will retain family links in private records. This means that you will see empty ‘private’ boxes on the pedigree chart and on other charts with private individuals.

en: This research is a “legitimate interest” under article 6(f) of the EU General Data Protection Regulations.
en-GB: This research is a ‘legitimate interest’ under article 6(f) of the EU General Data Protection Regulations.

en: This role has all the permissions of the manager role in all family trees, plus permission to change the settings/configuration of the website, users, and modules.
en-GB: This role has all the permissions of the manager role in all family trees, plus permission to change the settings/configuration of the website, users and modules.

en: This role has all the permissions of the member role, plus permission to add/change/delete data. Any changes will need to be reviewed by a moderator, unless the user has the “automatically accept changes” option enabled.
en-GB: This role has all the permissions of the member role, plus permission to add/change/delete data. Any changes will need to be reviewed by a moderator, unless the user has the ‘automatically accept changes’ option enabled.

note: I18N: Help text for the “Other facts to show in charts” configuration setting
en: This should be a comma or space separated list of facts, in addition to birth and death, that you want to appear in chart boxes such as the pedigree chart. This list requires you to use fact tags as defined in the GEDCOM 5.5.1 standard. For example, if you wanted the occupation to show up in the box, you would add “OCCU” to this field.
en-GB: This should be a comma or space separated list of facts, in addition to birth and death, that you want to appear in chart boxes such as the pedigree chart. This list requires you to use fact tags as defined in the GEDCOM 5.5.1 standard. For example, if you wanted the occupation to show up in the box, you would add ‘OCCU’ to this field.

en: This website uses cookies to learn about visitor behavior.
en-GB: This website uses cookies to learn about visitor behaviour.

note: I18N: %s is the name of a family tree
en: This will delete all the genealogy data from “%s” and replace it with data from a GEDCOM file.
en-GB: This will delete all the genealogy data from ‘%s’ and replace it with data from a GEDCOM file.

[ctx: Abbreviation for Persian month: Tir]
en: Tir
en-GB: Tīr

[ctx: GENITIVE]
note: I18N: 4th month in the Persian/Jalali calendar
en: Tir
en-GB: Tīr

[ctx: INSTRUMENTAL]
note: I18N: 4th month in the Persian/Jalali calendar
en: Tir
en-GB: Tīr

[ctx: LOCATIVE]
note: I18N: 4th month in the Persian/Jalali calendar
en: Tir
en-GB: Tīr

[ctx: NOMINATIVE]
note: I18N: 4th month in the Persian/Jalali calendar
en: Tir
en-GB: Tīr

en: To create new research tasks, you must first add “research task” to the list of facts and events in the family tree’s preferences.
en-GB: To create new research tasks, you must first add ‘research task’ to the list of facts and events in the family tree’s preferences.

note: I18N: Help text for the “Format text and notes” configuration setting
en: To ensure compatibility with other genealogy applications, notes, text, and transcripts should be recorded in simple, unformatted text. However, formatting is often desirable to aid presentation, comprehension, etc.
en-GB: To ensure compatibility with other genealogy applications, notes, text and transcripts should be recorded in simple, unformatted text. However, formatting is often desirable to aid presentation, comprehension, etc.

note: I18N: Location of an LDS church temple
en: Tuxtla Gutierrez, Mexico
en-GB: Tuxtla Gutiérrez, Mexico

en: Unrecognized GEDCOM code
en-GB: Unrecognised GEDCOM Code

en: Upload one or more media files from your local computer. Media files can be pictures, video, audio, or other formats.
en-GB: Upload one or more media files from your local computer. Media files can be pictures, video, audio or other formats.

en: Use a “?” to match a single character, use “*” to match zero or more characters.
en-GB: Use a ‘?’ to match a single character, use ‘*’ to match zero or more characters.

en: Use colors
en-GB: Use colours

note: I18N: Help text for the “Use silhouettes” configuration setting
en: Use silhouette images when no highlighted image for that individual has been specified. The images used are specific to the gender of the individual in question.
en-GB: Use silhouette images when no highlighted image for that individual has been specified. The images used are specific to the sex of the individual in question.

en: Username or email address
en-GB: Username or e-mail address

en: Usernames are case-insensitive and ignore accented letters, so that “chloe”, “chloë”, and “Chloe” are considered to be the same.
en-GB: Usernames are case-insensitive and ignore accented letters, so that ‘chloe’, ‘chloë’ and ‘Chloe’ are considered to be the same.

[ctx: GENITIVE]
note: I18N: a month in the French republican calendar
en: Vendemiaire
en-GB: Vendémiaire

[ctx: INSTRUMENTAL]
note: I18N: a month in the French republican calendar
en: Vendemiaire
en-GB: Vendémiaire

[ctx: LOCATIVE]
note: I18N: a month in the French republican calendar
en: Vendemiaire
en-GB: Vendémiaire

[ctx: NOMINATIVE]
note: I18N: a month in the French republican calendar
en: Vendemiaire
en-GB: Vendémiaire

[ctx: GENITIVE]
note: I18N: a month in the French republican calendar
en: Ventose
en-GB: Ventôse

[ctx: INSTRUMENTAL]
note: I18N: a month in the French republican calendar
en: Ventose
en-GB: Ventôse

[ctx: LOCATIVE]
note: I18N: a month in the French republican calendar
en: Ventose
en-GB: Ventôse

[ctx: NOMINATIVE]
note: I18N: a month in the French republican calendar
en: Ventose
en-GB: Ventôse

en: We will now send a confirmation email to the address <b>%s</b>. You must verify your account request by following instructions in the confirmation email. If you do not confirm your account request within seven days, your application will be rejected automatically. You will have to apply again.<br><br>After you have followed the instructions in the confirmation email, the administrator still has to approve your request before your account can be used.<br><br>To sign in to this website, you will need to know your username and password.
en-GB: We will now send a confirmation e-mail to the address <b>%s</b>. You must verify your account request by following instructions in the confirmation e-mail. If you do not confirm your account request within seven days, your application will be rejected automatically. You will have to apply again.<br><br>After you have followed the instructions in the confirmation e-mail, the administrator still has to approve your request before your account can be used.<br><br>To sign in to this website, you will need to know your username and password.

note: I18N: Help text for the “Keep the existing ‘last change’ information” configuration setting
en: When a record is edited, the user and timestamp are recorded. Sometimes it is desirable to keep the existing “last change” information, for example when making minor corrections to someone else’s data. This option controls whether this feature is selected by default.
en-GB: When a record is edited, the user and timestamp are recorded. Sometimes it is desirable to keep the existing ‘last change’ information, for example when making minor corrections to someone else’s data. This option controls whether this feature is selected by default.

en: When a user registers for an account, an email is sent to their email address with a verification link. When they follow this link, we know the email address is correct, and the “email verified” option is selected automatically.
en-GB: When a user registers for an account, an e-mail is sent to their e-mail address with a verification link. When they follow this link, we know the e-mail address is correct, and the ‘e-mail verified’ option is selected automatically.

note: I18N: Help text for the “Source type” configuration setting
en: When adding new close relatives, you can add source citations to the records (individual and family) or to the facts and events (birth, marriage, and death). This option controls whether records or facts will be selected by default.
en-GB: When adding new close relatives, you can add source citations to the records (individual and family) or to the facts and events (birth, marriage and death). This option controls whether records or facts will be selected by default.

en: When you add, edit, or delete information, the changes are not saved immediately. Instead, they are kept in a “pending” area. These pending changes need to be reviewed by a moderator before they are accepted.
en-GB: When you add, edit or delete information, the changes are not saved immediately. Instead, they are kept in a ‘pending’ area. These pending changes need to be reviewed by a moderator before they are accepted.

en: Where a user is associated to an individual record in a family tree and has a role of member, editor, or moderator, you can prevent them from accessing the details of distant, living relations. You specify the number of relationship steps that the user is allowed to see.
en-GB: Where a user is associated to an individual record in a family tree and has a role of member, editor or moderator, you can prevent them from accessing the details of distant, living relations. You specify the number of relationship steps that the user is allowed to see.

note: I18N: %1$s is the site URL and %2$s is an email address
en: You (or someone claiming to be you) has requested an account at %1$s using the email address %2$s.
en-GB: You (or someone claiming to be you) has requested an account at %1$s using the e-mail address %2$s.

note: I18N: Help text for the "Default theme" site configuration setting
en: You can change the appearance of webtrees using “themes”. Each theme has a different style, layout, color scheme, etc.
en-GB: You can change the appearance of webtrees using ‘themes’. Each theme has a different style, layout, colour scheme, etc.

en: You can opt out of tracking by setting the “Do Not Track” header in your browser preferences.
en-GB: You can opt out of tracking by setting the ‘Do Not Track’ header in your browser preferences.

note: I18N: Privacy restrictions are RESN tags in GEDCOM.
en: You can set the access for a specific record, fact, or event by adding a restriction to it. If a record, fact, or event does not have a restriction, the following default restrictions will be used.
en-GB: You can set the access for a specific record, fact or event by adding a restriction to it.  If a record, fact or event does not have a restriction, the following default restrictions will be used.

en: You need to be an authorized user to access this website.
en-GB: You need to be an authorised user to access this website.

note: I18N: e.g. ‘You should delete the “http://” from “http://www.example.com” and try again.’
en: You should delete the “%1$s” from “%2$s” and try again.
en-GB: You should delete the ‘%1$s’ from ‘%2$s’ and try again.

en: You should not approve an account unless you know that the email address is correct.
en-GB: You should not approve an account unless you know that the e-mail address is correct.

en: You will be informed by email when this prospective user has confirmed the request. You can then complete the process by activating the username. The new user will not be able to sign in until you activate the account.
en-GB: You will be informed by e-mail when this prospective user has confirmed the request. You can then complete the process by activating the username. The new user will not be able to sign in until you activate the account.

en: Your user account does not have “automatically accept changes” enabled. You will only be able to change one record at a time.
en-GB: Your user account does not have ‘automatically accept changes’ enabled. You will only be able to change one record at a time.

note: I18N: Name of a theme.
en: colors
en-GB: colours

en: gender
en-GB: sex

[ctx: GENITIVE]
note: I18N: a month in the French republican calendar
en: jours complementaires
en-GB: jours complémentaires

[ctx: INSTRUMENTAL]
note: I18N: a month in the French republican calendar
en: jours complementaires
en-GB: jours complémentaires

[ctx: NOMINATIVE]
note: I18N: a month in the French republican calendar
en: jours complementaires
en-GB: jours complémentaires

note: I18N: [you should check that:] ...
en: the database connection settings in the file “/data/config.ini.php” are still correct
en-GB: the database connection settings in the file ‘/data/config.ini.php’ are still correct

note: I18N: [you should check that:] ...
en: the folder “/data” and the file “/data/config.ini.php” have access permissions that allow the webserver to read them
en-GB: the folder ‘/data’ and the file ‘/data/config.ini.php’ have access permissions that allow the webserver to read them

note: I18N: Help text for the “Messages” site configuration setting
en: webtrees needs to send emails, such as password reminders and website notifications.
en-GB: webtrees needs to send e-mails, such as password reminders and website notifications.

en: webtrees sends emails with no storage
en-GB: webtrees sends e-mail with no storage

en: webtrees uses UTF-8 encoding for accented letters, special characters and non-Latin scripts. If you want to use this GEDCOM file with genealogy software that does not support UTF-8, then you can create it using ISO-8859-1 encoding.
en-GB: webtrees uses UTF-8 encoding for accented letters, special characters and non-latin scripts. If you want to use this GEDCOM file with genealogy software that does not support UTF-8, then you can create it using ISO-8859-1 encoding.

note: I18N: %s is the name of a genealogy record
en: “%s” has been deleted.
en-GB: ‘%s’ has been deleted.

note: I18N: Description of a “Data fix” module
en: “Highlighted image” (_PRIM) tags are used by some genealogy applications to indicate the preferred image for an individual. An alternative is to re-order the images so that the preferred one is listed first.
en-GB: ‘Highlighted image’ (_PRIM) tags are used by some genealogy applications to indicate the preferred image for an individual. An alternative is to re-order the images so that the preferred one is listed first.
