tin-man 2.6.5 - en to en_GB translation catalogue (169 entries)

note: type: Plain text
en: B<tin> is a full-screen easy to use Usenet newsreader. It can read news locally (e.g., I</var/spool/news>) or remotely (B<rtin> or B<tin -r> option) via an NNTP (Network News Transport Protocol, B<RFC\ 3977>) or NNTPS (B<RFC\ 8143>) server. It will automatically utilize NOV B<\%newsoverview>(5)  style index files if available locally or via the NNTP [X]OVER command (B<RFC\ 2980>, B<RFC\ 3977>).
en_GB: B<tin> is a full-screen easy to use Usenet newsreader. It can read news locally (e.g., I</var/spool/news>) or remotely (B<rtin> or B<tin -r> option) via an NNTP (Network News Transport Protocol, B<RFC\ 3977>) or NNTPS (B<RFC\ 8143>) server. It will automatically utilise NOV B<\%newsoverview>(5)  style index files if available locally or via the NNTP [X]OVER command (B<RFC\ 2980>, B<RFC\ 3977>).

note: type: Plain text
en: Toggle ANSI color (default is off).
en_GB: Toggle ANSI colour (default is off).

note: type: Plain text
en: Force authentication on initial connect. Only available when reading via NNTP.  See also I<${TIN_HOMEDIR:-"$HOME"}/.newsauth> in B<\%tin>(5).
en_GB: Force authentication on initial connect. Only available when reading via NNTP. See also I<${TIN_HOMEDIR:-"$HOME"}/.newsauth> in B<\%tin>(5).

note: type: Plain text
en: Enter debug-level, the levels can specified via number (should be avoided as it will be removed in the future) or name (case insensitive) as listed below. Use comma to give multiple levels, any combinations are allowed (e.g., ''B<-D> I<GNKSA,2,NNTP>''). If removal is requested it will be performed at startup and on normal termination (that is the files are only available while B<tin> is running).
en_GB: Enter debug-level, the levels can specified via number (should be avoided as it will be removed in the future) or name (case-insensitive) as listed below. Use comma to give multiple levels, any combinations are allowed (e.g., ''B<-D> I<GNKSA,2,NNTP>''). If removal is requested it will be performed at startup and on normal termination (that is the files are only available while B<tin> is running).

note: type: Plain text
en: At the Selection level the title displays (the name of the news server (with a "[T]"- or "[k]"-suffix if reading via NNTPS (insecurely)) and) the number of subscribed groups (containing new unread articles). The newsgroups are displayed in the middle of the screen usually with the number of unread articles displayed on the same line in front, but it can be customized via B<select_format>.
en_GB: At the Selection level the title displays (the name of the news server (with a "[T]"- or "[k]"-suffix if reading via NNTPS (insecurely)) and) the number of subscribed groups (containing new unread articles). The newsgroups are displayed in the middle of the screen usually with the number of unread articles displayed on the same line in front, but it can be customised via B<select_format>.

note: type: Plain text
en: If a thread has unread articles it is marked with B<art_marked_unread> in front of the total number of articles in the thread. If there are recent articles within the thread it might be marked with B<art_marked_recent> in front of the total number of articles in the thread \(em this is controlled by the B<recent_time> option. If a thread has hot articles in it (see also section "FILTERING ARTICLES") it's marked with B<art_marked_selected> in front of the total number of articles in the thread. The display can be customized via B<group_format>.
en_GB: If a thread has unread articles it is marked with B<art_marked_unread> in front of the total number of articles in the thread. If there are recent articles within the thread it might be marked with B<art_marked_recent> in front of the total number of articles in the thread \(em this is controlled by the B<recent_time> option. If a thread has hot articles in it (see also section "FILTERING ARTICLES") it's marked with B<art_marked_selected> in front of the total number of articles in the thread. The display can be customised via B<group_format>.

note: FIXME - add description of fields type: Plain text
en: At the Thread level the screen usually (depends on the threading method used) looks like this, but can be customized via B<thread_format>:
en_GB: At the Thread level the screen usually (depends on the threading method used) looks like this, but can be customised via B<thread_format>:

note: type: Plain text
en: The look of the Selection, Group and Thread level can be customized. See the section "CUSTOMIZING THE SCREEN FORMAT".
en_GB: The look of the Selection, Group and Thread level can be customised. See the section "CUSTOMISING THE SCREEN FORMAT".

note: type: Plain text
en: Toggle use of ANSI color.
en_GB: Toggle use of ANSI colour.

note: type: Plain text
en: Edit the filter file and reload it afterward.
en_GB: Edit the filter file and reload it afterwards.

note: type: Plain text
en: Search forward for specified subject.
en_GB: Search forwards for specified subject.

note: type: Plain text
en: Search backward for specified subject.
en_GB: Search backwards for specified subject.

note: type: Plain text
en: Toggle TeX to ISO decoding for current article. The default behavior is taken from the B<tex2iso_conv> variable in the tinrc file.
en_GB: Toggle TeX to ISO decoding for current article. The default behaviour is taken from the B<tex2iso_conv> variable in the tinrc file.

note: type: Plain text
en: Toggle the display data sections outside of MIME, e.g. uuencoded or yenc data. The default behavior is taken from the B<hide_inline_data> variable in the tinrc file.
en_GB: Toggle the display data sections outside of MIME, e.g. uuencoded or yenc data. The default behaviour is taken from the B<hide_inline_data> variable in the tinrc file.

note: type: Plain text
en: The variables are user configurable by editing I<${TIN_HOMEDIR:-"$HOME"}/.tin/tinrc> directly. Most of them can also be set in the GLOBAL OPTIONS MENU which is accessed by pressing B<OptionMenu> ('B<M>') at all levels. It allows the user to customize the behavior of B<tin>. The options are saved to the file I<${TIN_HOMEDIR:-"$HOME"}/.tin/tinrc> when you exit B<tin> so don't edit the file directly whilst B<tin> is running.
en_GB: The variables are user configurable by editing I<${TIN_HOMEDIR:-"$HOME"}/.tin/tinrc> directly. Most of them can also be set in the GLOBAL OPTIONS MENU which is accessed by pressing B<OptionMenu> ('B<M>') at all levels. It allows the user to customise the behaviour of B<tin>. The options are saved to the file I<${TIN_HOMEDIR:-"$HOME"}/.tin/tinrc> when you exit B<tin> so don't edit the file directly whilst B<tin> is running.

note: type: Plain text
en: Format string B<tin> uses for Attachment level representation. See the section "CUSTOMIZING THE SCREEN FORMAT".  Default is "%t%s%e%c%d".
en_GB: Format string B<tin> uses for Attachment level representation. See the section "CUSTOMISING THE SCREEN FORMAT".  Default is "%t%s%e%c%d".

note: type: TP
en: B<Standard background color (col_back)>
en_GB: B<Standard background colour (col_back)>

note: type: Plain text
en: Standard background color
en_GB: Standard background colour

note: type: TP
en: B<Color of quoted text from external sources (col_extquote)>
en_GB: B<Colour of quoted text from external sources (col_extquote)>

note: type: Plain text
en: Color of quoted text from external sources
en_GB: Colour of quoted text from external sources

note: type: TP
en: B<Color of sender (From:) (col_from)>
en_GB: B<Colour of sender (From:) (col_from)>

note: type: Plain text
en: Color of sender (From:)
en_GB: Colour of sender (From:)

note: type: TP
en: B<Color of article header lines (col_head)>
en_GB: B<Colour of article header lines (col_head)>

note: type: Plain text
en: Color of header-lines
en_GB: Colour of header-lines

note: type: TP
en: B<Color of help text (col_help)>
en_GB: B<Colour of help text (col_help)>

note: type: Plain text
en: Color of help pages
en_GB: Colour of help pages

note: type: TP
en: B<Color for inverse text (background) (col_invers_bg)>
en_GB: B<Colour for inverse text (background) (col_invers_bg)>

note: type: Plain text
en: Color of background for inverse text
en_GB: Colour of background for inverse text

note: type: TP
en: B<Color for inverse text (foreground) (col_invers_fg)>
en_GB: B<Colour for inverse text (foreground) (col_invers_fg)>

note: type: Plain text
en: Color of foreground for inverse text
en_GB: Colour of foreground for inverse text

note: type: TP
en: B<Color of status messages (col_message)>
en_GB: B<Colour of status messages (col_message)>

note: type: Plain text
en: Color of status messages in last line
en_GB: Colour of status messages in last line

note: type: TP
en: B<Color of highlighting with _dash_ (col_markdash)>
en_GB: B<Colour of highlighting with _dash_ (col_markdash)>

note: type: Plain text
en: Color of words emphasized like _this_. See also B<word_h_display_marks> and B<word_highlight>.
en_GB: Colour of words emphasised like _this_. See also B<word_h_display_marks> and B<word_highlight>.

note: type: TP
en: B<Color of highlighting with /slash/ (col_markslash)>
en_GB: B<Colour of highlighting with /slash/ (col_markslash)>

note: type: Plain text
en: Color of words emphasized like /this/. See also B<word_h_display_marks> and B<word_highlight>.
en_GB: Colour of words emphasised like /this/. See also B<word_h_display_marks> and B<word_highlight>.

note: type: TP
en: B<Color of highlighting with *stars* (col_markstar)>
en_GB: B<Colour of highlighting with *stars* (col_markstar)>

note: type: Plain text
en: Color of words emphasized like *this*. See also B<word_h_display_marks> and B<word_highlight>.
en_GB: Colour of words emphasised like *this*. See also B<word_h_display_marks> and B<word_highlight>.

note: type: TP
en: B<Color of highlighting with -stroke- (col_markstroke)>
en_GB: B<Colour of highlighting with -stroke- (col_markstroke)>

note: type: Plain text
en: Color of words emphasized like -this-. See also B<word_h_display_marks> and B<word_highlight>.
en_GB: Colour of words emphasised like -this-. See also B<word_h_display_marks> and B<word_highlight>.

note: type: TP
en: B<Color of mini help menu (col_minihelp)>
en_GB: B<Colour of mini help menu (col_minihelp)>

note: type: Plain text
en: Color of mini help menu
en_GB: Colour of mini help menu

note: type: TP
en: B<Color of actual news header fields (col_newsheaders)>
en_GB: B<Colour of actual news header fields (col_newsheaders)>

note: type: Plain text
en: Color of actual news header fields
en_GB: Colour of actual news header fields

note: type: TP
en: B<Standard foreground color (col_normal)>
en_GB: B<Standard foreground colour (col_normal)>

note: type: Plain text
en: Standard foreground color
en_GB: Standard foreground colour

note: type: TP
en: B<Color of quoted lines (col_quote)>
en_GB: B<Colour of quoted lines (col_quote)>

note: type: Plain text
en: Color of quoted lines
en_GB: Colour of quoted lines

note: type: TP
en: B<Color of twice quoted line (col_quote2)>
en_GB: B<Colour of twice quoted line (col_quote2)>

note: type: Plain text
en: Color of twice quoted lines
en_GB: Colour of twice quoted lines

note: type: TP
en: B<Color of E<gt>=3 times quoted line (col_quote3)>
en_GB: B<Colour of E<gt>=3 times quoted line (col_quote3)>

note: type: Plain text
en: Color of E<gt>=3 times quoted lines
en_GB: Colour of E<gt>=3 times quoted lines

note: type: TP
en: B<Color of response counter (col_response)>
en_GB: B<Colour of response counter (col_response)>

note: type: Plain text
en: Color of response counter. This is the text that says "Response x of y" in the article viewer.
en_GB: Colour of response counter. This is the text that says "Response x of y" in the article viewer.

note: type: TP
en: B<Color of signatures (col_signature)>
en_GB: B<Colour of signatures (col_signature)>

note: type: Plain text
en: Color of signatures
en_GB: Colour of signatures

note: type: TP
en: B<Color of negative score (col_score_neg)>
en_GB: B<Colour of negative score (col_score_neg)>

note: type: Plain text
en: Color of negative score
en_GB: Colour of negative score

note: type: TP
en: B<Color of positive score (col_score_pos)>
en_GB: B<Colour of positive score (col_score_pos)>

note: type: Plain text
en: Color of positive score
en_GB: Colour of positive score

note: type: TP
en: B<Color of urls highlight (col_urls)>
en_GB: B<Colour of urls highlight (col_urls)>

note: type: Plain text
en: Color of urls highlight
en_GB: Colour of urls highlight

note: type: TP
en: B<Color of verbatim blocks (col_verbatim)>
en_GB: B<Colour of verbatim blocks (col_verbatim)>

note: type: Plain text
en: Color of verbatim blocks
en_GB: Colour of verbatim blocks

note: type: TP
en: B<Color of article subject lines (col_subject)>
en_GB: B<Colour of article subject lines (col_subject)>

note: type: Plain text
en: Color of article subject
en_GB: Colour of article subject

note: type: TP
en: B<Color of text lines (col_text)>
en_GB: B<Colour of text lines (col_text)>

note: type: Plain text
en: Color of text-lines
en_GB: Colour of text-lines

note: type: TP
en: B<Color of help/mail sign (col_title)>
en_GB: B<Colour of help/mail sign (col_title)>

note: type: Plain text
en: Color of help/mail sign
en_GB: Colour of help/mail sign

note: most of these default_* settings are not available from the menu as they are intended for internal use only. type: Plain text
en: Format string used for date representation. A description of the different format options can be found in B<\%strftime>(3).  B<tin> uses B<\%strftime>(3)  when available and supports most format options in its fallback code.  Default is "%a, %d %b %Y %H:%M:%S".
en_GB: Format string used for date representation. A description of the different format options can be found in B<\%strftime>(3).  B<tin>  uses B<\%strftime>(3)  when available and supports most format options in its fallback code.  Default is "%a, %d %b %Y %H:%M:%S".

note: type: Plain text
en: Default for quick (1 key) kill filter case.  ON = filter case sensitive, OFF = ignore case. Default is OFF.
en_GB: Default for quick (1 key) kill filter case.  ON = filter case-sensitive, OFF = ignore case. Default is OFF.

note: type: Plain text
en: \%''Subject:'' (case sensitive)
en_GB: \%''Subject:'' (case-sensitive)

note: type: Plain text
en: \%''From:'' (case sensitive)
en_GB: \%''From:'' (case-sensitive)

note: type: Plain text
en: Default for quick (1 key) auto-selection filter case. ON=filter case sensitive, OFF=ignore case. Default is OFF.
en_GB: Default for quick (1 key) auto-selection filter case. ON=filter case-sensitive, OFF=ignore case. Default is OFF.

note: type: Plain text
en: Default for quick (1 key) auto-selection filter global.  ON=apply to all groups, OFF=apply to current group. Default is ON.
en_GB: Default for quick (1 key) auto-selection filter global. ON=apply to all groups, OFF=apply to current group. Default is ON.

note: type: Plain text
en: If B<getart_limit> is E<gt> 0 not more than the last B<getart_limit> articles/group are fetched from the server. If B<getart_limit> is E<lt> 0 B<tin> will start fetching articles from your first unread minus absolute value of B<getart_limit>. Note that setting B<getart_limit> to anything except 0 disables B<cache_overview_files>.  Default is 0, which means no limit.
en_GB: If B<getart_limit> is E<gt> 0 not more than the last B<getart_limit> articles/group are fetched from the server. If B<getart_limit> is E<lt> 0 B<tin> will start fetching articles from your first unread minus absolute value of B<getart_limit>. Note that setting B<getart_limit> to anything except 0 disables B<cache_overview_files>. Default is 0, which means no limit.

note: type: Plain text
en: Format string B<tin> uses for Group level representation. See the section "CUSTOMIZING THE SCREEN FORMAT". Default is "%n\ %m\ %R\ %L\ \ %s\ \ %F".
en_GB: Format string B<tin> uses for Group level representation. See the section "CUSTOMISING THE SCREEN FORMAT". Default is "%n\ %m\ %R\ %L\ \ %s\ \ %F".

note: type: Plain text
en: Which keys B<tin> should accept to jump to the next unread article.  Possible is any combination of B<PageDown> and B<PageNextUnread>.  When B<PageDown> is set, B<tin> jumps to the next article at the end of the current one. When B<PageNextUnread> is set, B<tin> jumps immediately to the next article when B<PageNextUnread> ('B<E<lt>TABE<gt>>')  is pressed. Default is B<PageNextUnread>.
en_GB: Which keys B<tin> should accept to jump to the next unread article. Possible is any combination of B<PageDown> and B<PageNextUnread>. When B<PageDown> is set, B<tin> jumps to the next article at the end of the current one. When B<PageNextUnread> is set, B<tin> jumps immediately to the next article when B<PageNextUnread> ('B<E<lt>TABE<gt>>') is pressed. Default is B<PageNextUnread>.

note: type: Plain text
en: B<Kill only unread arts> is the 'traditional' behavior of B<tin>. Only unread articles are killed once only by marking them read. As filtering only happens on unread articles with B<kill_level> set to 0, B<art_marked_killed> and B<art_marked_read_selected> are only shown once. When you reenter the group the mark will be gone.
en_GB: B<Kill only unread arts> is the 'traditional' behaviour of B<tin>. Only unread articles are killed once only by marking them read. As filtering only happens on unread articles with B<kill_level> set to 0, B<art_marked_killed> and B<art_marked_read_selected> are only shown once. When you reenter the group the mark will be gone.

note: type: Plain text
en: Charset used for posting and MIME headers; replaces B<mm_charset>.  Conversion between B<mm_network_charset> and local charset (determined via B<\%nl_langinfo>(3))  is done via B<\%iconv>(3)  or B<\%ucnv_*>().  If none of these functions are available on your system this option is disabled and you have to use B<mm_charset> instead. B<mm_network_charset> is limited to one of the following charsets:
en_GB: Charset used for posting and MIME headers; replaces B<mm_charset>.  Conversion between B<mm_network_charset> and local charset (determined via B<\%nl_langinfo>(3))  is done via B<\%iconv>(3)  or B<\%ucnv_*>(). If none of these functions are available on your system this option is disabled and you have to use B<mm_charset> instead. B<mm_network_charset> is limited to one of the following charsets:

note: type: Plain text
en: Character attribute of words emphasized like _this_. It depends on your terminal which attributes are usable. See also B<word_h_display_marks> and B<word_highlight>.
en_GB: Character attribute of words emphasised like _this_. It depends on your terminal which attributes are usable. See also B<word_h_display_marks> and B<word_highlight>.

note: type: Plain text
en: Character attribute of words emphasized like /this/. It depends on your terminal which attributes are usable. See also B<word_h_display_marks> and B<word_highlight>.
en_GB: Character attribute of words emphasised like /this/. It depends on your terminal which attributes are usable. See also B<word_h_display_marks> and B<word_highlight>.

note: type: Plain text
en: Character attribute of words emphasized like *this*. It depends on your terminal which attributes are usable. See also B<word_h_display_marks> and B<word_highlight>.
en_GB: Character attribute of words emphasised like *this*. It depends on your terminal which attributes are usable. See also B<word_h_display_marks> and B<word_highlight>.

note: type: Plain text
en: Character attribute of words emphasized like -this-. It depends on your terminal which attributes are usable. See also B<word_h_display_marks> and B<word_highlight>.
en_GB: Character attribute of words emphasised like -this-. It depends on your terminal which attributes are usable. See also B<word_h_display_marks> and B<word_highlight>.

note: type: TP
en: B<Unicode normalization form (normalization_form)>
en_GB: B<Unicode normalisation form (normalization_form)>

note: type: Plain text
en: The normalization form B<tin> should use to normalize Unicode input.  The possible values are:
en_GB: The normalisation form B<tin> should use to normalise Unicode input.  The possible values are:

note: type: Plain text
en: B<None>: no normalization
en_GB: B<None>: no normalisation

note: type: Plain text
en: Some normalization modes are only available if they are supported by the library B<tin> uses to do the normalization. NFC should be used if possible (B<RFC\ 5198>).
en_GB: Some normalisation modes are only available if they are supported by the library B<tin> uses to do the normalisation. NFC should be used if possible (B<RFC\ 5198>).

note: type: Plain text
en: Format string B<tin> uses for mime header at Page level. See the section "CUSTOMIZING THE SCREEN FORMAT".  Default is "[-- %T%S%*n%z%*l%!c%!d%*e --]".
en_GB: Format string B<tin> uses for mime header at Page level. See the section "CUSTOMISING THE SCREEN FORMAT".  Default is "[-- %T%S%*n%z%*l%!c%!d%*e --]".

note: type: Plain text
en: Format string B<tin> uses for uue header at Page level. See the section "CUSTOMIZING THE SCREEN FORMAT".  Default is "[-- %T%S%*n%I%!d%*e --]".
en_GB: Format string B<tin> uses for uue header at Page level. See the section "CUSTOMISING THE SCREEN FORMAT".  Default is "[-- %T%S%*n%I%!d%*e --]".

note: type: Plain text
en: Format string B<tin> uses for yenc header at Page level. See the section "CUSTOMIZING THE SCREEN FORMAT".  Default is "[-- %*N%!d%I [%F%G]%V%W%X --]".
en_GB: Format string B<tin> uses for yenc header at Page level. See the section "CUSTOMISING THE SCREEN FORMAT".  Default is "[-- %*N%!d%I [%F%G]%V%W%X --]".

note: type: Plain text
en: Allows 8-bit characters unencoded in the header of a news article, if set this also disables the generation of MIME-headers when they are usually required. Default is OFF. Only enacted if B<post_mime_encoding> is also set to 8bit. In a number of local hierarchies where 8-bit characters are used, using unencoded (raw)  8-bit characters in header is acceptable and sometimes even recommended so that you need to check the convention adopted in the local hierarchy of your interest to determine what to do with this and B<post_mime_encoding>.
en_GB: Allows 8-bit characters unencoded in the header of a news article, if set this also disables the generation of MIME-headers when they are usually required. Default is OFF. Only enacted if B<post_mime_encoding> is also set to 8bit. In a number of local hierarchies where 8-bit characters are used, using unencoded (raw) 8-bit characters in header is acceptable and sometimes even recommended so that you need to check the convention adopted in the local hierarchy of your interest to determine what to do with this and B<post_mime_encoding>.

note: type: TP
en: B<Quoting behavior (quote_style)>
en_GB: B<Quoting behaviour (quote_style)>

note: type: Plain text
en: Format string B<tin> uses for Selection level representation. See the section "CUSTOMIZING THE SCREEN FORMAT". Default is "%f\ %n\ %U\ \ %G\ \ %d".
en_GB: Format string B<tin> uses for Selection level representation. See the section "CUSTOMISING THE SCREEN FORMAT". Default is "%f\ %n\ %U\ \ %G\ \ %d".

note: type: Plain text
en: If ON, show "a as Umlaut-a, etc. Default is OFF. This behavior can also be toggled in the article viewer via B<PageToggleTex2iso> ('B<">').
en_GB: If ON, show "a as Umlaut-a, etc. Default is OFF. This behaviour can also be toggled in the article viewer via B<PageToggleTex2iso> ('B<">').

note: type: Plain text
en: Defines which threading method to use. It's possible to set the threading type on a per group basis by setting the group attribute variable B<thread_arts> to 0 \(en 4 in the file I<${TIN_HOMEDIR:-"$HOME"}/.tin/attributes>. (See also "ATTRIBUTES MENU AND GROUP ATTRIBUTES".) The default is Both Subject and References.  The choices are:
en_GB: Defines which threading method to use. It's possible to set the threading type on a per group basis by setting the group attribute variable B<thread_arts> to 0 \(en 4 in the file I<${TIN_HOMEDIR:-"$HOME"}/.tin/attributes>. (See also "ATTRIBUTES MENU AND GROUP ATTRIBUTES".)  The default is Both Subject and References.  The choices are:

note: type: Plain text
en: Format string B<tin> uses for Thread level representation. See the section "CUSTOMIZING THE SCREEN FORMAT". Default is "%n\ %m\ \ [%L]\ \ %T\ \ %F".
en_GB: Format string B<tin> uses for Thread level representation. See the section "CUSTOMISING THE SCREEN FORMAT". Default is "%n\ %m\ \ [%L]\ \ %T\ \ %F".

note: type: Plain text
en: The program that will be run when launching URLs in the article viewer using B<PageViewUrl> ('B<U>'). The actual URL will be appended.  Default is B<url_handler.pl>.
en_GB: The program that will be run when launching URLs in the article viewer using B<PageViewUrl> ('B<U>'). The actual URL will be appended. Default is B<url_handler.pl>.

note: type: TP
en: B<Use ANSI color (use_color)>
en_GB: B<Use ANSI colour (use_color)>

note: type: Plain text
en: If enabled B<tin> uses ANSI-colors. Default is OFF.
en_GB: If enabled B<tin> uses ANSI-colours. Default is OFF.

note: type: Plain text
en: A regular expression that B<tin> will use to find the begin of a verbatim block.
en_GB: A regular expression that  B<tin> will use to find the begin of a verbatim block.

note: type: Plain text
en: Enable word highlighting. See B<word_h_display_marks> for the options available. If B<use_color> is enabled the colors specified in B<col_markdash>, B<col_markslash>, B<col_markstar> and B<col_markstroke> are used for word highlighting else the character attributes specified in B<mono_markdash>, B<mono_markslash>, B<mono_markstar> and B<mono_markstroke> are used. Default is ON.
en_GB: Enable word highlighting. See B<word_h_display_marks> for the options available. If B<use_color> is enabled the colours specified in B<col_markdash>, B<col_markslash>, B<col_markstar> and B<col_markstroke> are used for word highlighting else the character attributes specified in B<mono_markdash>, B<mono_markslash>, B<mono_markstar> and B<mono_markstroke> are used. Default is ON.

note: type: Plain text
en: The scopes menu (accessible from the options menu with B<ConfigScopeMenu> ('B<S>')) shows all scopes read from the global and local attributes file.  Scopes from the global attributes file are marked with B<scope_marked_global> ('B<!\&>') to the left of the scope number, scopes from the local attributes file are marked with B<scope_marked_local> ('B< >').  When the scopes menu is accessed from the group, thread, or article level, scopes where the current group matches are marked with B<scope_marked_global_match > ('B<:>') for scopes from the global attributes file and with B<scope_marked_local_match> ('B<*>')  for scopes from the local attributes file.
en_GB: The scopes menu (accessible from the options menu with B<ConfigScopeMenu> ('B<S>')) shows all scopes read from the global and local attributes file. Scopes from the global attributes file are marked with B<scope_marked_global> ('B<!\&>') to the left of the scope number, scopes from the local attributes file are marked with B<scope_marked_local> ('B< >'). When the scopes menu is accessed from the group, thread, or article level, scopes where the current group matches are marked with B<scope_marked_global_match > ('B<:>') for scopes from the global attributes file and with B<scope_marked_local_match> ('B<*>') for scopes from the local attributes file.

note: type: Plain text
en: In addition to the common moving keys the following commands are available: B<ScopeSelect> ('B<^J>' or 'B<E<lt>CRE<gt>>') enter the attributes menu for the current scope, B<ScopeEditAttributesFile> ('B<E>') edit the local attributes file, B<ScopeAdd> ('B<a>') add a new scope, B<ScopeDelete> ('B<d>') delete the current scope, B<ScopeMove> ('B<m>') move the current scope to a new position, B<ScopeRename> ('B<r>') rename the current scope.  Note that delete (B<ScopeDelete>), rename (B<ScopeRename>) and move (B<ScopeMove>) are not available for global scopes.  B<ToggleHelpDisplay> ('B<H>') toggles the help mini menu at the bottom of the screen and posting etiquette after composing an article (B<beginner_level>).
en_GB: In addition to the common moving keys the following commands are available: B<ScopeSelect> ('B<^J>' or 'B<E<lt>CRE<gt>>') enter the attributes menu for the current scope, B<ScopeEditAttributesFile> ('B<E>') edit the local attributes file, B<ScopeAdd> ('B<a>') add a new scope, B<ScopeDelete> ('B<d>') delete the current scope, B<ScopeMove> ('B<m>') move the current scope to a new position, B<ScopeRename> ('B<r>') rename the current scope. Note that delete (B<ScopeDelete>), rename (B<ScopeRename>) and move (B<ScopeMove>) are not available for global scopes. B<ToggleHelpDisplay> ('B<H>') toggles the help mini menu at the bottom of the screen and posting etiquette after composing an article (B<beginner_level>).

note: type: SS
en: CUSTOMIZING THE ARTICLE QUOTE STRING
en_GB: CUSTOMISING THE ARTICLE QUOTE STRING

note: type: Plain text
en: When posting a followup to an article or replying direct to the author of an article via email the text of the article can be quoted. The beginning of the quoted text can contain information about the quoted article (e.g., Name and the Message-ID of the article). If the article has multiple addresses, only the first is evaluated. To allow for different situations, certain information from the article can be used in the quoted string. The following variables are expanded if found in the tinrc variables B<mail_quote_format>, B<news_quote_format> or B<xpost_quote_format>:
en_GB: When posting a followup to an article or replying direct to the author of an article via e-mail the text of the article can be quoted. The beginning of the quoted text can contain information about the quoted article (e.g., Name and the Message-ID of the article). If the article has multiple addresses, only the first is evaluated. To allow for different situations, certain information from the article can be used in the quoted string. The following variables are expanded if found in the tinrc variables B<mail_quote_format>, B<news_quote_format> or B<xpost_quote_format>:

note: type: Plain text
en: B<%A>	Address (Email)
    B<%D>	Date (uses B<date_format>)
    B<%F>	Full address (%N E<lt>%AE<gt>)
    B<%G>	Groupname
    B<%M>	Message-ID
    B<%N>	Fullname of author
    B<%C>	Firstname of author
    B<%I>	Initials of author
en_GB: B<%A>	Address (E-mail)
    B<%D>	Date (uses B<date_format>)
    B<%F>	Full address (%N E<lt>%AE<gt>)
    B<%G>	Groupname
    B<%M>	Message-ID
    B<%N>	Fullname of author
    B<%C>	Firstname of author
    B<%I>	Initials of author

note: type: Plain text
en: Various expansion characters are recognized when entering the directory and file to save to. Environment variables (prefixed with '$') and user home directories (prefixed by '~' or '~username') can be specified.  Environment variables can themselves contain other special characters.
en_GB: Various expansion characters are recognised when entering the directory and file to save to. Environment variables (prefixed with '$') and user home directories (prefixed by '~' or '~username') can be specified.  Environment variables can themselves contain other special characters.

note: type: Plain text
en: If saving multiple files at once the filename (if not referring to a mailbox)  will be extended by ".num" where "num" is at least a 3-digit number counting up from 1. Environment variables are allowed within a filename (e.g., I<$SOURCES/dir/filename>).
en_GB: If saving multiple files at once the filename (if not referring to a mailbox)  will be extended by ".num" where "num" is at least 3-digit number counting up from 1. Environment variables are allowed within a filename (e.g., I<$SOURCES/dir/filename>).

note: type: Plain text
en: B<tin> allows new/unread news articles to be mailed (''B<-M>'' and \&''B<-N>'' option) or saved (''B<-S>'' option) in batch mode for later reading. Useful when going on holiday and you don't want to return and find that expire has removed a whole load of unread articles. Best to run via B<\%cron>(8)  everyday while away, after which you will be mailed a report of which articles were mailed/saved from which newsgroups and the total number of articles mailed/saved. Articles are saved in a private news structure under your B<savedir> directory (default is I<${TIN_HOMEDIR:-"$HOME"}/News>).  Be careful of using this option if you read a lot of groups because you could overflow your file system.
en_GB: B<tin> allows new/unread news articles to be mailed (''B<-M>'' and \&''B<-N>'' option) or saved (''B<-S>'' option) in batch mode for later reading. Useful when going on holiday and you don't want to return and find that expire has removed a whole load of unread articles. Best to run via B<\%cron>(8)  everyday while away, after which you will be mailed a report of which articles were mailed/saved from which newsgroups and the total number of articles mailed/saved. Articles are saved in a private news structure under your B<savedir> directory (default is I<${TIN_HOMEDIR:-"$HOME"}/News>). Be careful of using this option if you read a lot of groups because you could overflow your file system.

note: type: Plain text
en: Wildmat searches automatically enclose the search string in asterisks ('*'), simulating substring searches. This behavior is fixed and cannot be altered.
en_GB: Wildmat searches automatically enclose the search string in asterisks ('*'), simulating substring searches. This behaviour is fixed and cannot be altered.

note: type: Plain text
en: Regex searches automatically replace spaces ('\ ') and/or tabs ('\et') in the search string with the '\es' meta-character, which matches any whitespace character. This behavior cannot be prevented. Also regex searches are case insensitive by default. To enforce case sensitivity, prefix the search pattern by one of the following: 'B<(?^)>' or 'B<(?-i)>'.
en_GB: Regex searches automatically replace spaces ('\ ') and/or tabs ('\et') in the search string with the '\es' meta-character, which matches any whitespace character. This behaviour cannot be prevented. Also regex searches are case insensitive by default. To enforce case sensitivity, prefix the search pattern by one of the following: 'B<(?^)>' or 'B<(?-i)>'.

note: type: Plain text
en: If Unicode normalization is available, search patterns are normalized according to the B<normalization_form> tinrc variable.
en_GB: If Unicode normalisation is available, search patterns are normalised according to the B<normalization_form> tinrc variable.

note: type: Plain text
en: B<tin> will recognize a signature in either I<${TIN_HOMEDIR:-"$HOME"}/.signature> or I<${TIN_HOMEDIR:-"$HOME"}/.Sig>.  If I<${TIN_HOMEDIR:-"$HOME"}/.signature> exists, then the signature will be pulled into the editor for mail commands only. A signature in I<${TIN_HOMEDIR:-"$HOME"}/.signature> will not be pulled into the editor for posting commands since B<\%inews>(1)  will append the signature itself.
en_GB: B<tin> will recognise a signature in either I<${TIN_HOMEDIR:-"$HOME"}/.signature> or I<${TIN_HOMEDIR:-"$HOME"}/.Sig>.  If I<${TIN_HOMEDIR:-"$HOME"}/.signature> exists, then the signature will be pulled into the editor for mail commands only. A signature in I<${TIN_HOMEDIR:-"$HOME"}/.signature> will not be pulled into the editor for posting commands since B<\%inews>(1)  will append the signature itself.

note: type: Plain text
en: B<tin> also has the capability to generate random signatures on a per-newsgroup basis if so desired.  The way to accomplish this is to specify the default signature or the group attribute sigfile as a directory.  If for example the sigfile path is I</usr/iain/.sigs> and I<.sigs> is a directory then B<tin> will select a random signature from any file that is in the directory I<.sigs> (note: one signature per numbered file).  A random signature can also consist of a fixed part signature that can contain your name, address etc. followed by the random sig.  The fixed part of the random sig is read from the file I<$HOME/.sigfixed>.
en_GB: B<tin> also has the capability to generate random signatures on a per-newsgroup basis if so desired. The way to accomplish this is to specify the default signature or the group attribute sigfile as a directory. If for example the sigfile path is I</usr/iain/.sigs> and I<.sigs> is a directory then B<tin> will select a random signature from any file that is in the directory I<.sigs> (note: one signature per numbered file). A random signature can also consist of a fixed part signature that can contain your name, address etc. followed by the random sig. The fixed part of the random sig is read from the file I<$HOME/.sigfixed>.

note: type: SS
en: CUSTOMIZING THE SCREEN FORMAT
en_GB: CUSTOMISING THE SCREEN FORMAT

note: type: Plain text
en: The look of the Selection, Group and Thread level can be customized via format strings. These format strings define the content and the position of each element on the screen. Variables are used within the format strings as placeholders. If the article has multiple addresses, only the first is evaluated. The following variables are available:
en_GB: The look of the Selection, Group and Thread level can be customised via format strings. These format strings define the content and the position of each element on the screen. Variables are used within the format strings as placeholders. If the article has multiple addresses, only the first is evaluated. The following variables are available:

note: type: Plain text
en: In addition, a minimum or a maximum screen width can be defined for each item (except 'B<%%>'). In this case, the item will only be displayed when the screen is wider resp. smaller than specified. This comes in handy to not overload a small screen but have maximum information on a large screen. The minimum screen width has to be specified by a positive number preceded by an 'B<E<gt>>', the maximum screen width has to be specified by a positive number preceded by an 'B<E<lt>>'. In the following example B<tin> will display the score only if the screen is wider than 100 characters: 'B<%E<gt>100S>'.
en_GB: In addition, a minimum or a maximum screen width can be defined for each item (except 'B<%%>'). In this case, the item will only be displayed when the screen is wider resp. smaller than specified. This comes in handy to not overload a small screen but have maximum information on a large screen.  The minimum screen width has to be specified by a positive number preceded by an 'B<E<gt>>', the maximum screen width has to be specified by a positive number preceded by an 'B<E<lt>>'. In the following example B<tin> will display the score only if the screen is wider than 100 characters: 'B<%E<gt>100S>'.

note: type: Plain text
en: If both the length and the minimum or maximum screen width should be specified for an item, the length must be the first parameter and the minimum or maximum screen width must be the second one. The following example displays the score with a length of 10 characters only if the screen is wider than 100 characters: 'B<%10E<gt>100S>'. A second length can be specified for 'B<%F>' and 'B<%s>' resp. 'B<%T>', separated by a colon, which is used if the minimum or maximum screen width is not reached.  If no length is specified after the colon, the item is displayed even if the minimum screen width is not reached and the length is calculated as if no minimum (or maximum) screen width had been specified. In the following example B<tin> will display the subject with a length of 60 characters if the screen is wider than 100 characters, otherwise a length of 40 characters is used: 'B<%60E<gt>100:40s>'.
en_GB: If both the length and the minimum or maximum screen width should be specified for an item, the length must be the first parameter and the minimum or maximum screen width must be the second one. The following example displays the score with a length of 10 characters only if the screen is wider than 100 characters: 'B<%10E<gt>100S>'. A second length can be specified for 'B<%F>' and 'B<%s>' resp.  'B<%T>', separated by a colon, which is used if the minimum or maximum screen width is not reached. If no length is specified after the colon, the item is displayed even if the minimum screen width is not reached and the length is calculated as if no minimum (or maximum) screen width had been specified. In the following example B<tin> will display the subject with a length of 60 characters if the screen is wider than 100 characters, otherwise a length of 40 characters is used: 'B<%60E<gt>100:40s>'.

note: type: Plain text
en: The look of the Attachment level and the mime, uue and yenc header at Page level can be customized too via format strings.  The following variables are available:
en_GB: The look of the Attachment level and the mime, uue and yenc header at Page level can be customised too via format strings.  The following variables are available:

note: type: TP
en: Button2 (center)
en_GB: Button2 (centre)

note: type: TP
en: center button
en_GB: centre button

note: type: Plain text
en: If your news server doesn't support NOV index files or you have a very slow connection to your news server then B<tin> can cache the index for each newsgroup if B<cache_overview_files> is set to ON.  Note that this cache can use up large amounts of disk space if you read a lot of groups and/or high traffic groups. To reduce the amount of disk space used, B<compress_overview_files> can be set to ON.  Be aware that the use of B<getart_limit> will disable B<cache_overview_files>.
en_GB: If your news server doesn't support NOV index files or you have a very slow connection to your news server then B<tin> can cache the index for each newsgroup if B<cache_overview_files> is set to ON.  Note that this cache can use up large amounts of disk space if you read a lot of groups and/or high traffic groups. To reduce the amount of disk space used, B<compress_overview_files> can be set to ON. Be aware that the use of B<getart_limit> will disable B<cache_overview_files>.

note: type: Plain text
en: If you are low on local disk space you should consider to manually purge cached data for groups you are not reading anymore with something like:
en_GB: If you are low on local disk space you should consider to manually purge cached data for groups you are not reading any more with something like:

note: type: Plain text
en: If the server does not initially require authentication but supports compression and compression is requested, B<tin> will exit when authentication is required later on. Using the ''B<-A>'' command line option in conjunction with ''B<-C>'' circumvents this behavior.
en_GB: If the server does not initially require authentication but supports compression and compression is requested, B<tin> will exit when authentication is required later on. Using the ''B<-A>'' command line option in conjunction with ''B<-C>'' circumvents this behaviour.

note: type: Plain text
en: B<CNews\ NNTPd,> B<\%noffle>(1)  (E<lt>= V1.0-pre5) and B<NewsCache> (E<lt>= V1.1.91) can't handle pipelined GROUP commands (B<RFC\ 3977>).  If you run into trouble with any of the mentioned historical servers set B<nntp_pipeline_limit> in I<${TIN_HOMEDIR:-"$HOME"}/.tin/$NNTPSERVER/serverrc> to 1.
en_GB: B<CNews\ NNTPd>, B<\%noffle>(1)  (E<lt>= V1.0-pre5) and B<NewsCache> (E<lt>= V1.1.91) can't handle pipelined GROUP commands (B<RFC\ 3977>).  If you run into trouble with any of the mentioned historical servers set B<nntp_pipeline_limit> in I<${TIN_HOMEDIR:-"$HOME"}/.tin/$NNTPSERVER/serverrc> to 1.

note: type: Plain text
en: This man page describes the various (config) files and their formats used by the B<\%tin>(1)  newsreader.  All files are expected to have unix style ('\(rsn' aka LF) line endings.
en_GB: This man page describes the various (config) files and their formats used by the B<\%tin>(1)  newsreader. All files are expected to have unix style ('\(rsn' aka LF) line endings.

note: type: Plain text
en: B<\%mailcap>(5)  files as defined in B<RFC\ 1524>.  The mailcap files are read by B<\%tin>(1)  to determine how to display non-text messages at the local site.  Any line that starts with "#" is a comment.  Blank lines are ignored. Otherwise, each line defines a single mailcap entry for a single content type.  Long lines may be continued by ending them with a backslash character, "\(rs".
en_GB: B<\%mailcap>(5)  files as defined in B<RFC\ 1524>. The mailcap files are read by B<\%tin>(1)  to determine how to display non-text messages at the local site. Any line that starts with "#" is a comment. Blank lines are ignored. Otherwise, each line defines a single mailcap entry for a single content type. Long lines may be continued by ending them with a backslash character, "\(rs".

note: type: Plain text
en: The "type" field is simply any valid content type name.  It is the string that will be matched against the ''Content-Type:'' header to decide if this is the mailcap entry that matches the current message.  Additionally, the type field may specify a subtype or a wildcard to match all subtypes.
en_GB: The "type" field is simply any valid content type name. It is the string that will be matched against the ''Content-Type:'' header to decide if this is the mailcap entry that matches the current message. Additionally, the type field may specify a subtype or a wildcard to match all subtypes.

note: type: Plain text
en: The "command" field is any UNIX command and is used to specify the interpreter for the given type of message.  It will be passed to the shell via the B<\%system>(3)  facility.
en_GB: The "command" field is any UNIX command and is used to specify the interpreter for the given type of message. It will be passed to the shell via the B<\%system>(3)  facility.

note: Two special codes can appear in the viewing command for objects of type multipart (any subtype). These are "%n" and "%F". %n will be replaced by the number of parts within the multipart object. %F will be replaced by a series of arguments, two for each part, giving first the content-type and then th
en: Semicolons and backslashes within the command or any flag field must be quoted with backslashes.  If the field contains "%s", those two characters will be replaced by the name of a file that contains the body of the message.  If it contains "%t", those two characters will be replaced by the content-type field, including the subtype, if any.  If it contains "%{" followed by a parameter name and a closing "}", then all those characters will be replaced by the value of the named parameter, if any, from the \&''Content-Type:'' header.  Finally, if the field contains "\(rs%", those two characters will be replaced by a single "%" character.
en_GB: Semicolons and backslashes within the command or any flag field must be quoted with backslashes. If the field contains "%s", those two characters will be replaced by the name of a file that contains the body of the message. If it contains "%t", those two characters will be replaced by the content-type field, including the subtype, if any. If it contains "%{" followed by a parameter name and a closing "}", then all those characters will be replaced by the value of the named parameter, if any, from the \&''Content-Type:'' header. Finally, if the field contains "\(rs%", those two characters will be replaced by a single "%" character.

note: type: Plain text
en: The "compose" field may be used to specify a program that can be used to compose a new body or body part in the given format.  Its intended use is to support mail composing agents that support the composition of multiple types of mail using external composing agents.  As with the view-command, the semantics of program execution are operating system dependent.  The result of the composing program may be data that is not yet suitable for mail transport \(em that is, a Content-Transfer-Encoding may need to be applied to the data.
en_GB: The "compose" field may be used to specify a program that can be used to compose a new body or body part in the given format. Its intended use is to support mail composing agents that support the composition of multiple types of mail using external composing agents. As with the view-command, the semantics of program execution are operating system dependent. The result of the composing program may be data that is not yet suitable for mail transport \(em that is, a Content-Transfer-Encoding may need to be applied to the data.

note: type: Plain text
en: The "composetyped" field is similar to the "compose" field, but is to be used when the composing program needs to specify the ''Content-Type:'' header field to be applied to the composed data.  The "compose" field is simpler, and is preferred for use with existing (non-mail-oriented) programs for composing data in a given format.  The "composetyped" field is necessary when the Content-Type information must include auxiliary parameters, and the composition program must then know enough about mail formats to produce output that includes the mail type information.
en_GB: The "composetyped" field is similar to the "compose" field, but is to be used when the composing program needs to specify the ''Content-Type:'' header field to be applied to the composed data. The "compose" field is simpler, and is preferred for use with existing (non-mail-oriented) programs for composing data in a given format. The "composetyped" field is necessary when the Content-Type information must include auxiliary parameters, and the composition program must then know enough about mail formats to produce output that includes the mail type information.

note: type: Plain text
en: The "edit" field may be used to specify a program that can be used to edit a body or body part in the given format.  In many cases, it may be identical in content to the "compose" field, and shares the operating-system dependent semantics for program execution.
en_GB: The "edit" field may be used to specify a program that can be used to edit a body or body part in the given format. In many cases, it may be identical in content to the "compose" field, and shares the operating-system dependent semantics for program execution.

note: type: Plain text
en: The "print" field may be used to specify a program that can be used to print a message or body part in the given format.  As with the view-command, the semantics of program execution are operating system dependent.
en_GB: The "print" field may be used to specify a program that can be used to print a message or body part in the given format. As with the view-command, the semantics of program execution are operating system dependent.

note: type: Plain text
en: The "needsterminal" field indicates that the view-command must be run on an interactive terminal.  This is needed to inform window-oriented user agents that an interactive terminal is needed.  (The decision is not left exclusively to the view-command because in some circumstances it may not be possible for such programs to tell whether or not they are on interactive terminals.)  The needsterminal command should be assumed to apply to the compose and edit commands, too, if they exist.  Note that this is NOT a test \(en it is a requirement for the environment in which the program will be executed, and should typically cause the creation of a terminal window when not executed on either a real terminal or a terminal window.
en_GB: The "needsterminal" field indicates that the view-command must be run on an interactive terminal. This is needed to inform window-oriented user agents that an interactive terminal is needed. (The decision is not left exclusively to the view-command because in some circumstances it may not be possible for such programs to tell whether or not they are on interactive terminals.) The needsterminal command should be assumed to apply to the compose and edit commands, too, if they exist. Note that this is NOT a test \(en it is a requirement for the environment in which the program will be executed, and should typically cause the creation of a terminal window when not executed on either a real terminal or a terminal window.

note: type: Plain text
en: The "copiousoutput" field indicates that the output from the view-command will be an extended stream of output and is to be interpreted as advice to the UA (User Agent mail-reading program) that the output should be either paged or made scroll-able.  Note that it is probably a mistake if needsterminal and copiousoutput are both specified.
en_GB: The "copiousoutput" field indicates that the output from the view-command will be an extended stream of output and is to be interpreted as advice to the UA (User Agent mail-reading program) that the output should be either paged or made scroll-able. Note that it is probably a mistake if needsterminal and copiousoutput are both specified.

note: type: Plain text
en: The "nametemplate" field gives a filename format, in which %s will be replaced by a short unique string to give the name of the temporary file to be passed to the viewing command.  This is only expected to be relevant in environments where filename extensions are meaningful, e.g., one could specify that a GIF file being passed to a gif viewer should have a name ending in ".gif" by using "nametemplate=%s.gif".
en_GB: The "nametemplate" field gives a filename format, in which %s will be replaced by a short unique string to give the name of the temporary file to be passed to the viewing command. This is only expected to be relevant in environments where filename extensions are meaningful, e.g., one could specify that a GIF file being passed to a gif viewer should have a name ending in ".gif" by using "nametemplate=%s.gif".

note: type: Plain text
en: B<\%tin>(1)  currently only respects the "test", "description", "nametemplate" and partly the "needsterminal" flags, all other flags are internally ignored.  It also can't handle the "%F" and "%n" expansions yet.
en_GB: B<\%tin>(1)  currently only respects the "test", "description", "nametemplate" and partly the "needsterminal" flags, all other flags are internally ignored. It also can't handle the "%F" and "%n" expansions yet.

note: type: Plain text
en: "I<nntpserver[:port]> I<password> [I<user>]" pairs for NNTP servers that require authorization. If the password contains a space or a tab it must be enclosed in double quotes ("). Usernames must not be enclosed in double quotes and thus can't contain spaces or tabs. Any line that starts with "#" is a comment. Blank lines are ignored. This file should be readable only for the user as it contains the user's unencrypted password for reading news!
en_GB: "I<nntpserver[:port]> I<password> [I<user>]" pairs for NNTP servers that require authorisation. If the password contains a space or a tab it must be enclosed in double quotes ("). Usernames must not be enclosed in double quotes and thus can't contain spaces or tabs. Any line that starts with "#" is a comment. Blank lines are ignored. This file should be readable only for the user as it contains the user's unencrypted password for reading news!

note: type: Plain text
en: Used when a group is a mailing list. All responses to the group will be directed to this email address instead
en_GB: Used when a group is a mailing list. All responses to the group will be directed to this e-mail address instead

note: type: Plain text
en: Match against ''From:'' address parser return codes. E<lt>num matches less than, E<gt>num matches more than the returned numeric value. GNKSA_LOCAL_DOMAIN_LITERAL or GNKSA_INVALID_DOMAIN are only returned if B<disable_gnksa_domain_check> in I</etc/tin/tin.defaults> is set to OFF. As the built-in domain list may be outdated this should be considered carefully. GNKSA_ILLEGAL_LABEL_BEGNUM is only returned if B<\%tin>(1)  was compiled with ENFORCE_RFC1034 defined which is usually not the case.
en_GB: Match against ''From:'' address parser return codes. E<lt>num matches less than, E<gt>num matches more than the returned numeric value. GNKSA_LOCAL_DOMAIN_LITERAL or GNKSA_INVALID_DOMAIN are only returned if B<disable_gnksa_domain_check> in I</etc/tin/tin.defaults> is set to OFF. As the built-in domain list may be outdated this should be considered carefully. GNKSA_ILLEGAL_LABEL_BEGNUM is only returned if B<\%tin>(1) was compiled with ENFORCE_RFC1034 defined which is usually not the case.

note: type: Plain text
en: Keymap-file, containing "I<keyname> I<value> I<[value]>" pairs separated by spaces or tabs. If the keymap-file named with full specified B<\%locale>(5)  is not found, less specific ones are looked for. Various parts will be stripped off the name, in the following order codeset, normalized codeset, territory and modifier when looking for the keymap-file.  Below is a list of all rebindable keynames and their defaults. If a keyname is bound to NULL it is unassigned.
en_GB: Keymap-file, containing "I<keyname> I<value> I<[value]>" pairs separated by spaces or tabs. If the keymap-file named with full specified B<\%locale>(5)  is not found, less specific ones are looked for. Various parts will be stripped off the name, in the following order codeset, normalised codeset, territory and modifier when looking for the keymap-file.  Below is a list of all rebindable keynames and their defaults. If a keyname is bound to NULL it is unassigned.

note: type: Plain text
en: Format string B<\%tin>(1)  uses for Attachment level representation.  Default is "%t%s%e%c%d".
en_GB: Format string B<\%tin>(1) uses for Attachment level representation. Default is "%t%s%e%c%d".

note: type: tbl table
en: ''Subject:'' (case sensitive)
en_GB: ''Subject:'' (case-sensitive)

note: type: tbl table
en: ''From:'' (case sensitive)
en_GB: ''From:'' (case-sensitive)

note: type: Plain text
en: A regular expression that will be applied when reading articles. All matching lines are shown in B<col_extquote>. If B<extquote_regex> is blank, then B<\%tin>(1)  uses a built-in default.
en_GB: A regular expression that will be applied when reading articles. All matching lines are shown in B<col_extquote>. If B<extquote_regex> is blank, then B<\%tin>(1) uses a built-in default.

note: type: Plain text
en: If B<getart_limit> is E<gt> 0 not more than the last B<getart_limit> articles/group are fetched from the server. If B<getart_limit> is E<lt> 0 B<\%tin>(1)  will start fetching articles from your first unread minus absolute value of B<getart_limit>. Note that setting B<getart_limit> to anything except 0 disables B<cache_overview_files>. Default is 0, which means no limit.
en_GB: If B<getart_limit> is E<gt> 0 not more than the last B<getart_limit> articles/group are fetched from the server. If B<getart_limit> is E<lt> 0 B<\%tin>(1) will start fetching articles from your first unread minus absolute value of B<getart_limit>. Note that setting B<getart_limit> to anything except 0 disables B<cache_overview_files>. Default is 0, which means no limit.

note: type: Plain text
en: Which keys B<\%tin>(1)  should accept to jump to the next unread article.  Possible is any combination of B<PageDown> and B<PageNextUnread>.  When B<PageDown> is set B<\%tin>(1)  jumps to the next article at the end of the current one. When B<PageNextUnread> is set B<\%tin>(1)  jumps immediately to the next article when B<PageNextUnread> ('B<E<lt>TABE<gt>>')  is pressed. Default is B<PageNextUnread>.
en_GB: Which keys B<\%tin>(1) should accept to jump to the next unread article.  Possible is any combination of B<PageDown> and B<PageNextUnread>. When B<PageDown> is set B<\%tin>(1) jumps to the next article at the end of the current one. When B<PageNextUnread> is set B<\%tin>(1) jumps immediately to the next article when B<PageNextUnread> ('B<E<lt>TABE<gt>>') is pressed. Default is B<PageNextUnread>.

note: type: Plain text
en: B<Kill only unread arts> is the 'traditional' behavior of B<\%tin>(1).  Only unread articles are killed once only by marking them read. As filtering only happens on unread articles with B<kill_level> set to 0, B<art_marked_killed> and B<art_marked_read_selected> are only shown once. When you reenter the group the mark will be gone.
en_GB: B<Kill only unread arts> is the 'traditional' behaviour of B<\%tin>(1).  Only unread articles are killed once only by marking them read. As filtering only happens on unread articles with B<kill_level> set to 0, B<art_marked_killed> and B<art_marked_read_selected> are only shown once. When you reenter the group the mark will be gone.

note: type: Plain text
en: The normalization form which should be used to normalize Unicode input.  The possible values are:
en_GB: The normalisation form which should be used to normalise Unicode input.  The possible values are:

note: type: Plain text
en: Some normalization modes are only available if they are supported by the library B<\%tin>(1)  uses to do the normalization. NFC should be used if possible (B<RFC\ 5198>).
en_GB: Some normalisation modes are only available if they are supported by the library B<\%tin>(1)  uses to do the normalisation. NFC should be used if possible (B<RFC\ 5198>).

note: type: Plain text
en: Format string B<\%tin>(1)  uses for mime header at Page level.  Default is "[-- %T%S%*n%z%*l%!c%!d%*e --]".
en_GB: Format string B<\%tin>(1) uses for mime header at Page level.  Default is "[-- %T%S%*n%z%*l%!c%!d%*e --]".

note: type: Plain text
en: Format string B<\%tin>(1)  uses for uue header at Page level.  Default is "[-- %T%S%*n%I%!d%*e --]".
en_GB: Format string B<\%tin>(1) uses for uue header at Page level.  Default is "[-- %T%S%*n%I%!d%*e --]".

note: type: Plain text
en: If ON B<\%tin>(1)  does the rendering of bi-directional text. If OFF B<\%tin>(1)  leaves the rendering of bi-directional text to the terminal. Default is OFF.
en_GB: If ON B<\%tin>(1) does the rendering of bi-directional text. If OFF B<\%tin>(1) leaves the rendering of bi-directional text to the terminal. Default is OFF.

note: type: Plain text
en: The number of lines that will be scrolled up/down in the article pager when using cursor-up/down. The default is 1 (line-by-line). Set to 0 to get traditional B<\%tin>(1)  page-by-page scrolling. Set to -1 to get page-by-page scrolling where the top/bottom line is carried over onto the next page.  This setting supersedes B<show_last_line_prev_page>=ON. Set to -2 to get half-page scrolling. This setting supersedes B<full_page_scroll>=OFF.
en_GB: The number of lines that will be scrolled up/down in the article pager when using cursor-up/down. The default is 1 (line-by-line). Set to 0 to get traditional B<\%tin>(1) page-by-page scrolling. Set to -1 to get page-by-page scrolling where the top/bottom line is carried over onto the next page.  This setting supersedes B<show_last_line_prev_page>=ON. Set to -2 to get half-page scrolling. This setting supersedes B<full_page_scroll>=OFF.

note: type: Plain text
en: The path that specifies the signature file to use when posting, following up to or replying to an article. If the path is a directory then the signature will be randomly generated from files that are in the specified directory. If a file named I<.sigfixed> does exist in that dir or I<${TIN_HOMEDIR:-"$HOME"}/.sigfixed> does exist it will be prepended to the chosen signature (first match counts). If the path starts with a ! the program the path points to will be executed to generate a signature. In order to pass the group name to the program, %G can be specified.  This will be replaced by the name of the current newsgroup. --none will suppress any signature. Default is I<${TIN_HOMEDIR:-"$HOME"}/.Sig>.  See also I<${TIN_HOMEDIR:-"$HOME"}/.sigfixed>.
en_GB: The path that specifies the signature file to use when posting, following up to or replying to an article. If the path is a directory then the signature will be randomly generated from files that are in the specified directory. If a file named I<.sigfixed> does exist in that dir or I<${TIN_HOMEDIR:-"$HOME"}/.sigfixed> does exist it will be prepended to the chosen signature (first match counts). If the path starts with a ! the program the path points to will be executed to generate a signature. In order to pass the group name to the program, %G can be specified. This will be replaced by the name of the current newsgroup. --none will suppress any signature. Default is I<${TIN_HOMEDIR:-"$HOME"}/.Sig>. See also I<${TIN_HOMEDIR:-"$HOME"}/.sigfixed>.

note: type: Plain text
en: Decode German style TeX umlaut codes to ISO If ON, show "a as Umlaut-a, etc. Default is OFF. This behavior can also be toggled in the article viewer via B<PageToggleTex2iso> ('B<">').
en_GB: Decode German style TeX umlaut codes to ISO If ON, show "a as Umlaut-a, etc. Default is OFF. This behaviour can also be toggled in the article viewer via B<PageToggleTex2iso> ('B<">').

note: type: Plain text
en: Allows you to select how B<\%tin>(1)  treats blank lines in article bodies.  Default is 0. This option does not affect lines within verbatim blocks and is applied before B<hideline_regex>.
en_GB: Allows you to select how B<\%tin>(1) treats blank lines in article bodies.  Default is 0. This option does not affect lines within verbatim blocks and is applied before B<hideline_regex>.

note: type: Plain text
en: If enabled B<\%tin>(1)  uses ANSI-colors. Default is OFF.
en_GB: If enabled B<\%tin>(1)  uses ANSI-colours. Default is OFF.

note: type: Plain text
en: A regular expression that B<\%tin>(1)  will use to find the begin of a verbatim block. Default is #v+
en_GB: A regular expression that B<\%tin>(1) will use to find the begin of a verbatim block. Default is #v+

note: type: Plain text
en: A regular expression that B<\%tin>(1)  will use to find the end of a verbatim block. Default is #v-
en_GB: A regular expression that B<\%tin>(1) will use to find the end of a verbatim block. Default is #v-

note: type: Plain text
en: Allows you to select how B<\%tin>(1)  treats verbatim blocks in article bodies.  Default is 1.
en_GB: Allows you to select how B<\%tin>(1) treats verbatim blocks in article bodies. Default is 1.

note: type: Plain text
en: Defines the name of your organization. $B<ORGANIZATION> overrides any specified value.
en_GB: Defines the name of your organisation. $B<ORGANIZATION> overrides any specified value.

note: type: Plain text
en: Defines the email address to which users can send bug reports using a built-in function. The default points to a developers mailing list located at tin.org. You might want to change this address to one of your local administration if you want to deal with your lusers problems on your own.
en_GB: Defines the e-mail address to which users can send bug reports using a built-in function. The default points to a developers mailing list located at tin.org. You might want to change this address to one of your local administration if you want to deal with your lusers problems on your own.

note: type: Plain text
en: This file provides short descriptions of each newsgroup. It is normally updated by the local news server (e.g., B<\%innd>(8))  whenever a new group is created. Each line consist of two tab-separated fields "I<group.name>	I<one-line description>".
en_GB: This file provides short descriptions of each newsgroup. It is normally updated by the local news server (e.g.,  B<\%innd>(8))  whenever a new group is created. Each line consist of two tab-separated fields "I<group.name>	I<one-line description>".

note: type: Plain text
en: This file might hold a default organization to be used in the ''Organization:'' header. $B<ORGANIZATION> has a higher priority if set.
en_GB: This file might hold a default organisation to be used in the ''Organization:'' header. $B<ORGANIZATION> has a higher priority if set.

note: type: Plain text
en: This file specifies the organization of the news overview database (see also B<\%newsoverview>(5)).  The order of lines in this file is important; it determines the order in which the fields will appear in the database. See also B<\%overview.fmt>(5).  B<\%tin>(1)  only tries to read the file if you read directly from the local spool, if you read news via NNTP, B<\%tin>(1)  uses the LIST OVERVIEW.FMT (B<RFC\ 3977>) command instead.
en_GB: This file specifies the organisation of the news overview database (see also B<\%newsoverview>(5)).  The order of lines in this file is important; it determines the order in which the fields will appear in the database. See also B<\%overview.fmt>(5).  B<\%tin>(1)  only tries to read the file if you read directly from the local spool, if you read news via NNTP, B<\%tin>(1)  uses the LIST OVERVIEW.FMT (B<RFC\ 3977>) command instead.
