2016-01-27 03:48:38 +00:00
|
|
|
|
#ifndef language_en_gb_h
|
2016-01-15 04:06:15 +00:00
|
|
|
|
#define language_en_gb_h
|
|
|
|
|
/*
|
|
|
|
|
* language_en_gb.h
|
|
|
|
|
* Localization support for HTML Tidy.
|
|
|
|
|
*
|
|
|
|
|
*
|
2016-01-29 03:11:53 +00:00
|
|
|
|
* This file is a localization file for HTML Tidy. It will have been machine
|
|
|
|
|
* generated or created and/or edited by hand. Both are valid options, but
|
|
|
|
|
* please help keep our localization efforts simple to maintain by maintaining
|
|
|
|
|
* the structure of this file, and changing the check box below if you make
|
|
|
|
|
* changes (so others know the file origin):
|
|
|
|
|
*
|
|
|
|
|
* [X] THIS FILE IS MACHINE GENERATED. It is a localization file for the
|
|
|
|
|
* language (and maybe region) "en_gb". The source of
|
|
|
|
|
* these strings is a gettext PO file in Tidy's source, probably called
|
|
|
|
|
* "language_en_gb.po".
|
|
|
|
|
*
|
|
|
|
|
* [ ] THIS FILE WAS HAND MODIFIED. Translators, please feel to edit this file
|
|
|
|
|
* directly (and check this box). If you prefer to edit PO files then use
|
|
|
|
|
* `poconvert.rb msgunfmt language_en_gb.h` (our own
|
|
|
|
|
* conversion tool) to generate a fresh PO from this file first!
|
2016-01-15 04:06:15 +00:00
|
|
|
|
*
|
2017-02-13 19:29:47 +00:00
|
|
|
|
* (c) 2015-2017 HTACG
|
2016-01-15 04:06:15 +00:00
|
|
|
|
* See tidy.h and access.h for the copyright notice.
|
|
|
|
|
*
|
|
|
|
|
* Template Created by Jim Derry on 01/14/2016.
|
|
|
|
|
*
|
|
|
|
|
* Orginating PO file metadata:
|
|
|
|
|
* PO_LAST_TRANSLATOR=jderry
|
2017-03-13 17:45:32 +00:00
|
|
|
|
* PO_REVISION_DATE=2017-03-11 18:31:52
|
2016-01-15 04:06:15 +00:00
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifdef _MSC_VER
|
|
|
|
|
#pragma execution_character_set("utf-8")
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* This language-specific function returns the correct pluralForm
|
|
|
|
|
* to use given n items, and is used as a member of each language
|
|
|
|
|
* definition.
|
|
|
|
|
*/
|
|
|
|
|
static uint whichPluralForm_en_gb(uint n) {
|
2016-01-29 03:11:53 +00:00
|
|
|
|
/* Plural-Forms: nplurals=2; */
|
|
|
|
|
return n != 1;
|
2016-01-15 04:06:15 +00:00
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* This structure specifies all of the strings needed by Tidy for a
|
|
|
|
|
* single language. Static definition in a header file makes it
|
|
|
|
|
* easy to include and exclude languages without tinkering with
|
|
|
|
|
* the build system.
|
|
|
|
|
*/
|
|
|
|
|
static languageDefinition language_en_gb = { whichPluralForm_en_gb, {
|
2016-01-29 03:11:53 +00:00
|
|
|
|
/***************************************
|
|
|
|
|
** This MUST be present and first.
|
|
|
|
|
** Specify the code for this language.
|
|
|
|
|
***************************************/
|
2016-01-15 04:06:15 +00:00
|
|
|
|
{/* Specify the ll or ll_cc language code here. */
|
|
|
|
|
TIDY_LANGUAGE, 0, "en_gb"
|
|
|
|
|
},
|
Add new `rebase` command to CLI.
This is intended to make it very, very easy to update the POT and all of the POs when
changes are made to `language_en.h`. Used without an sha-1 hash, untranslated strings
(i.e., the "source" strings) are updated in the POT/PO's.
However if you specify an --sha=HASH (or -c HASH) option, then the script will use git
to examine the `language_en.h` file from that specified commit, determing the strings
that have changed, and mark all of these strings as `fuzzy` in the POs. This will serve
as a flag to translators that the original has changed. In addition, this `fuzzy` flag
will appear in the headers as "(fuzzy) " in the item comments.
If a translator edits the header directly, he should remove the "(fuzzy )" in the
comment. Then when the PO is rebuilt, the fuzzy flag will be removed automatically.
The reverse is also true; if a translator is working with the PO, he or she should
clear the fuzzy flag and the comment will be adjusted accordingly in the generated
header.
2016-03-24 03:38:04 +00:00
|
|
|
|
{ TEXT_USING_FONT, 0,
|
2016-01-15 04:06:15 +00:00
|
|
|
|
"You are recommended to use CSS to specify the font and\n"
|
|
|
|
|
"properties such as its size and colour. This will reduce\n"
|
|
|
|
|
"the size of HTML files and make them easier to maintain\n"
|
|
|
|
|
"compared with using <FONT> elements.\n\n"
|
|
|
|
|
},
|
Add new `rebase` command to CLI.
This is intended to make it very, very easy to update the POT and all of the POs when
changes are made to `language_en.h`. Used without an sha-1 hash, untranslated strings
(i.e., the "source" strings) are updated in the POT/PO's.
However if you specify an --sha=HASH (or -c HASH) option, then the script will use git
to examine the `language_en.h` file from that specified commit, determing the strings
that have changed, and mark all of these strings as `fuzzy` in the POs. This will serve
as a flag to translators that the original has changed. In addition, this `fuzzy` flag
will appear in the headers as "(fuzzy) " in the item comments.
If a translator edits the header directly, he should remove the "(fuzzy )" in the
comment. Then when the PO is rebuilt, the fuzzy flag will be removed automatically.
The reverse is also true; if a translator is working with the PO, he or she should
clear the fuzzy flag and the comment will be adjusted accordingly in the generated
header.
2016-03-24 03:38:04 +00:00
|
|
|
|
{ TEXT_USING_BODY, 0, "You are recommended to use CSS to specify page and link colours\n" },
|
|
|
|
|
{ TEXT_GENERAL_INFO_PLEA, 0,
|
2016-01-15 04:06:15 +00:00
|
|
|
|
"\n"
|
|
|
|
|
"Would you like to see Tidy in proper, British English? Please consider \n"
|
|
|
|
|
"helping us to localise HTML Tidy. For details please see \n"
|
|
|
|
|
"https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md\n"
|
|
|
|
|
},
|
|
|
|
|
|
|
|
|
|
#if SUPPORT_ACCESSIBILITY_CHECKS
|
|
|
|
|
{ INFORMATION_NOT_CONVEYED_IMAGE, 0, "[2.1.1.1]: ensure information not conveyed through colour alone (image)." },
|
|
|
|
|
{ INFORMATION_NOT_CONVEYED_APPLET, 0, "[2.1.1.2]: ensure information not conveyed through colour alone (applet)." },
|
|
|
|
|
{ INFORMATION_NOT_CONVEYED_OBJECT, 0, "[2.1.1.3]: ensure information not conveyed through colour alone (object)." },
|
|
|
|
|
{ INFORMATION_NOT_CONVEYED_SCRIPT, 0, "[2.1.1.4]: ensure information not conveyed through colour alone (script)." },
|
|
|
|
|
{ INFORMATION_NOT_CONVEYED_INPUT, 0, "[2.1.1.5]: ensure information not conveyed through colour alone (input)." },
|
|
|
|
|
{ COLOR_CONTRAST_TEXT, 0, "[2.2.1.1]: poor colour contrast (text)." },
|
|
|
|
|
{ COLOR_CONTRAST_LINK, 0, "[2.2.1.2]: poor colour contrast (link)." },
|
|
|
|
|
{ COLOR_CONTRAST_ACTIVE_LINK, 0, "[2.2.1.3]: poor colour contrast (active link)." },
|
|
|
|
|
{ COLOR_CONTRAST_VISITED_LINK, 0, "[2.2.1.4]: poor colour contrast (visited link)." },
|
|
|
|
|
#endif /* SUPPORT_ACCESSIBILITY_CHECKS */
|
|
|
|
|
|
Add new `rebase` command to CLI.
This is intended to make it very, very easy to update the POT and all of the POs when
changes are made to `language_en.h`. Used without an sha-1 hash, untranslated strings
(i.e., the "source" strings) are updated in the POT/PO's.
However if you specify an --sha=HASH (or -c HASH) option, then the script will use git
to examine the `language_en.h` file from that specified commit, determing the strings
that have changed, and mark all of these strings as `fuzzy` in the POs. This will serve
as a flag to translators that the original has changed. In addition, this `fuzzy` flag
will appear in the headers as "(fuzzy) " in the item comments.
If a translator edits the header directly, he should remove the "(fuzzy )" in the
comment. Then when the PO is rebuilt, the fuzzy flag will be removed automatically.
The reverse is also true; if a translator is working with the PO, he or she should
clear the fuzzy flag and the comment will be adjusted accordingly in the generated
header.
2016-03-24 03:38:04 +00:00
|
|
|
|
{ TidyMergeDivs, 0,
|
2016-01-15 04:06:15 +00:00
|
|
|
|
"This option can be used to modify the behaviour of <code>clean</code> when "
|
|
|
|
|
"set to <code>yes</code>."
|
|
|
|
|
"<br/>"
|
|
|
|
|
"This option specifies if Tidy should merge nested <code><div></code> "
|
|
|
|
|
"such as <code><div><div>...</div></div></code>. "
|
|
|
|
|
"<br/>"
|
|
|
|
|
"If set to <code>auto</code> the attributes of the inner "
|
|
|
|
|
"<code><div></code> are moved to the outer one. Nested "
|
|
|
|
|
"<code><div></code> with <code>id</code> attributes are <em>not</em> "
|
|
|
|
|
"merged. "
|
|
|
|
|
"<br/>"
|
|
|
|
|
"If set to <code>yes</code> the attributes of the inner "
|
|
|
|
|
"<code><div></code> are discarded with the exception of "
|
|
|
|
|
"<code>class</code> and <code>style</code>. "
|
|
|
|
|
},
|
Add new `rebase` command to CLI.
This is intended to make it very, very easy to update the POT and all of the POs when
changes are made to `language_en.h`. Used without an sha-1 hash, untranslated strings
(i.e., the "source" strings) are updated in the POT/PO's.
However if you specify an --sha=HASH (or -c HASH) option, then the script will use git
to examine the `language_en.h` file from that specified commit, determing the strings
that have changed, and mark all of these strings as `fuzzy` in the POs. This will serve
as a flag to translators that the original has changed. In addition, this `fuzzy` flag
will appear in the headers as "(fuzzy) " in the item comments.
If a translator edits the header directly, he should remove the "(fuzzy )" in the
comment. Then when the PO is rebuilt, the fuzzy flag will be removed automatically.
The reverse is also true; if a translator is working with the PO, he or she should
clear the fuzzy flag and the comment will be adjusted accordingly in the generated
header.
2016-03-24 03:38:04 +00:00
|
|
|
|
{ TidyMergeSpans, 0,
|
2016-01-15 04:06:15 +00:00
|
|
|
|
"This option can be used to modify the behaviour of <code>clean</code> when "
|
|
|
|
|
"set to <code>yes</code>."
|
|
|
|
|
"<br/>"
|
|
|
|
|
"This option specifies if Tidy should merge nested <code><span></code> "
|
|
|
|
|
"such as <code><span><span>...</span></span></code>. "
|
|
|
|
|
"<br/>"
|
|
|
|
|
"The algorithm is identical to the one used by <code>merge-divs</code>. "
|
|
|
|
|
},
|
Add new `rebase` command to CLI.
This is intended to make it very, very easy to update the POT and all of the POs when
changes are made to `language_en.h`. Used without an sha-1 hash, untranslated strings
(i.e., the "source" strings) are updated in the POT/PO's.
However if you specify an --sha=HASH (or -c HASH) option, then the script will use git
to examine the `language_en.h` file from that specified commit, determing the strings
that have changed, and mark all of these strings as `fuzzy` in the POs. This will serve
as a flag to translators that the original has changed. In addition, this `fuzzy` flag
will appear in the headers as "(fuzzy) " in the item comments.
If a translator edits the header directly, he should remove the "(fuzzy )" in the
comment. Then when the PO is rebuilt, the fuzzy flag will be removed automatically.
The reverse is also true; if a translator is working with the PO, he or she should
clear the fuzzy flag and the comment will be adjusted accordingly in the generated
header.
2016-03-24 03:38:04 +00:00
|
|
|
|
{ TidyReplaceColor, 0,
|
2016-01-15 04:06:15 +00:00
|
|
|
|
"This option specifies if Tidy should replace numeric values in colour "
|
|
|
|
|
"attributes with HTML/XHTML colour names where defined, e.g. replace "
|
|
|
|
|
"<code>#ffffff</code> with <code>white</code>. "
|
|
|
|
|
},
|
|
|
|
|
|
|
|
|
|
{/* This MUST be present and last. */
|
|
|
|
|
TIDY_MESSAGE_TYPE_LAST, 0, NULL
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
}};
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#endif /* language_en_gb_h */
|