2011-10-12 00:32:59 +05:30
|
|
|
/* top_nls.c - provide the basis for future nls translations */
|
|
|
|
|
/*
|
2013-01-01 11:30:00 +05:30
|
|
|
* Copyright (c) 2011-2013, by: James C. Warner
|
2011-10-12 00:32:59 +05:30
|
|
|
* All rights reserved. 8921 Hilloway Road
|
|
|
|
|
* Eden Prairie, Minnesota 55347 USA
|
|
|
|
|
*
|
|
|
|
|
* This file may be used subject to the terms and conditions of the
|
|
|
|
|
* GNU Library General Public License Version 2, or any later version
|
|
|
|
|
* at your option, as published by the Free Software Foundation.
|
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
* GNU Library General Public License for more details.
|
|
|
|
|
*/
|
|
|
|
|
/* For contributions to this program, the author wishes to thank:
|
|
|
|
|
* Craig Small, <csmall@small.dropbear.id.au>
|
|
|
|
|
* Sami Kerola, <kerolasa@iki.fi>
|
|
|
|
|
*/
|
|
|
|
|
|
2011-11-02 23:00:03 +05:30
|
|
|
#include <locale.h>
|
2011-10-12 00:32:59 +05:30
|
|
|
#include <stdio.h>
|
|
|
|
|
#include <string.h>
|
|
|
|
|
|
2011-10-17 04:26:11 +05:30
|
|
|
#include "../include/nls.h"
|
|
|
|
|
|
2011-10-12 00:32:59 +05:30
|
|
|
#include "top.h"
|
|
|
|
|
#include "top_nls.h"
|
|
|
|
|
|
2013-03-03 11:30:00 +05:30
|
|
|
#ifdef VALIDATE_NLS
|
|
|
|
|
#include <stdlib.h>
|
|
|
|
|
#endif
|
|
|
|
|
|
2011-11-02 23:00:03 +05:30
|
|
|
// Programmer Note(s):
|
|
|
|
|
// Preparation ---------------------------------------------
|
|
|
|
|
// Unless you have *something* following the gettext macro,
|
|
|
|
|
// xgettext will refuse to see any TRANSLATORS comments.
|
|
|
|
|
// Thus empty strings have been added for potential future
|
|
|
|
|
// comment additions.
|
|
|
|
|
//
|
|
|
|
|
// Also, by omitting the argument for the --add-comments
|
2012-04-23 22:20:49 +05:30
|
|
|
// XGETTEXT_OPTION in po/Makevars, *any* preceding c style
|
2011-11-02 23:00:03 +05:30
|
|
|
// comment will be propagated to the .pot file, providing
|
|
|
|
|
// that the gettext macro isn't empty as discussed above.
|
2011-11-07 04:38:43 +05:30
|
|
|
// However, this is far too aggressive so we have chosen
|
|
|
|
|
// the word 'Translation' to denote xgettext comments.
|
2011-11-02 23:00:03 +05:30
|
|
|
//
|
|
|
|
|
// /* Need Not Say 'TRANSLATORS': ...
|
|
|
|
|
// snprintf(buf, sizeof(buf), "%s", _( // unseen comment
|
|
|
|
|
//
|
2011-11-07 04:38:43 +05:30
|
|
|
// /* Translation Hint: ...
|
2011-11-02 23:00:03 +05:30
|
|
|
// snprintf(buf, sizeof(buf), "%s", _("" // now it's seen!
|
|
|
|
|
//
|
|
|
|
|
// Translation, from po/ directory after make --------------
|
|
|
|
|
// ( this is the procedure used before any translations were )
|
|
|
|
|
// ( available in the po/ directory, which contained only the )
|
|
|
|
|
// ( procps-ng.pot, this domain's template file. )
|
|
|
|
|
//
|
|
|
|
|
// ( below: ll_CC = language/country as in 'zh_CN' or 'en_AU' )
|
|
|
|
|
//
|
|
|
|
|
// msginit --locale=ll_CC --no-wrap
|
|
|
|
|
// . creates a ll_CC.po file from the template procps-ng.pot
|
|
|
|
|
// . may also duplicate msgid as msgstr if languages similar
|
|
|
|
|
// msgen --no-wrap ll_CC.po --output-file=ll_CC.po
|
|
|
|
|
// . duplicates every msgid literal as msgstr value
|
|
|
|
|
// . this is the file that's edited
|
|
|
|
|
// . replace "Content-Type: ... charset=ASCII\n"
|
|
|
|
|
// with "... charset=UTF-8\n"
|
|
|
|
|
// . translate msgstr values, leaving msgid unchanged
|
|
|
|
|
// msgfmt ll_CC.po --strict --output-file=procps-ng.mo
|
2013-03-19 10:30:00 +05:30
|
|
|
// . after which ensure, chmod 644
|
|
|
|
|
// . then copy
|
|
|
|
|
// to /usr/share/locale-langpack/ll_CC/LC_MESSAGES/
|
|
|
|
|
// or /usr/share/locale/ll_CC/LC_MESSAGES/
|
2011-11-02 23:00:03 +05:30
|
|
|
// Testing -------------------------------------------------
|
|
|
|
|
// export LC_ALL= && export LANGUAGE=ll_CC
|
|
|
|
|
// run some capable program like top
|
|
|
|
|
//
|
2011-10-12 00:32:59 +05:30
|
|
|
|
|
|
|
|
/*
|
2012-09-19 12:32:02 +05:30
|
|
|
* These are our string tables with the following contents:
|
|
|
|
|
* Head : column headings with varying size limits
|
2011-10-12 00:32:59 +05:30
|
|
|
* Desc : fields descriptions not to exceed 20 screen positions
|
|
|
|
|
* Norm : regular text possibly also containing c-format specifiers
|
|
|
|
|
* Uniq : show_special specially formatted strings
|
|
|
|
|
*
|
2011-10-14 22:15:44 +05:30
|
|
|
* The latter table presents the greatest translation challenge !
|
2012-09-19 12:32:02 +05:30
|
|
|
*
|
|
|
|
|
* We go to the trouble of creating the nls string tables to achieve
|
|
|
|
|
* these objectives:
|
|
|
|
|
* + the overhead of repeated runtime calls to gettext()
|
|
|
|
|
* will be avoided
|
|
|
|
|
* + the order of the strings in the template (.pot) file
|
|
|
|
|
* can be completely controlled
|
|
|
|
|
* + none of the important translator only comments will
|
|
|
|
|
* clutter and obscure the main program
|
2011-10-12 00:32:59 +05:30
|
|
|
*/
|
2014-02-25 11:30:00 +05:30
|
|
|
const char *Head_nlstab[EU_MAXPFLGS];
|
|
|
|
|
const char *Desc_nlstab[EU_MAXPFLGS];
|
2011-10-12 00:32:59 +05:30
|
|
|
const char *Norm_nlstab[norm_MAX];
|
|
|
|
|
const char *Uniq_nlstab[uniq_MAX];
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* This routine builds the nls table containing plain text only
|
|
|
|
|
* used as the field descriptions. Each translated line MUST be
|
|
|
|
|
* kept to a maximum of 20 characters or less! */
|
2012-09-19 12:32:02 +05:30
|
|
|
static void build_two_nlstabs (void) {
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-11-07 04:38:43 +05:30
|
|
|
/* Translation Notes ------------------------------------------------
|
|
|
|
|
. It is strongly recommend that the --no-wrap command line option
|
|
|
|
|
. be used with all supporting translation tools, when available.
|
|
|
|
|
.
|
2012-09-19 12:32:02 +05:30
|
|
|
. The following line pairs contain only plain text and consist of:
|
|
|
|
|
. 1) a field name/column header - mostly upper case
|
|
|
|
|
. 2) the related description - both upper and lower case
|
|
|
|
|
.
|
|
|
|
|
. To avoid truncation at runtime, each column header is noted with
|
|
|
|
|
. its maximum size and the following description must not exceed
|
|
|
|
|
. 20 characters. Fewer characters are ok.
|
2011-11-07 04:38:43 +05:30
|
|
|
.
|
|
|
|
|
. */
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'PID' = 5 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_PID] = _("PID");
|
|
|
|
|
Desc_nlstab[EU_PID] = _("Process Id");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'PPID' = 5 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_PPD] = _("PPID");
|
|
|
|
|
Desc_nlstab[EU_PPD] = _("Parent Process pid");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'UID' = 5 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_UED] = _("UID");
|
|
|
|
|
Desc_nlstab[EU_UED] = _("Effective User Id");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'USER' = 8 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_UEN] = _("USER");
|
|
|
|
|
Desc_nlstab[EU_UEN] = _("Effective User Name");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'RUID' = 5 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_URD] = _("RUID");
|
|
|
|
|
Desc_nlstab[EU_URD] = _("Real User Id");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'RUSER' = 8 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_URN] = _("RUSER");
|
|
|
|
|
Desc_nlstab[EU_URN] = _("Real User Name");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'SUID' = 5 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_USD] = _("SUID");
|
|
|
|
|
Desc_nlstab[EU_USD] = _("Saved User Id");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'SUSER' = 8 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_USN] = _("SUSER");
|
|
|
|
|
Desc_nlstab[EU_USN] = _("Saved User Name");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'GID' = 5 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_GID] = _("GID");
|
|
|
|
|
Desc_nlstab[EU_GID] = _("Group Id");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'GROUP' = 8 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_GRP] = _("GROUP");
|
|
|
|
|
Desc_nlstab[EU_GRP] = _("Group Name");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'PGRP' = 5 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_PGD] = _("PGRP");
|
|
|
|
|
Desc_nlstab[EU_PGD] = _("Process Group Id");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'TTY' = 8 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_TTY] = _("TTY");
|
|
|
|
|
Desc_nlstab[EU_TTY] = _("Controlling Tty");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'TPGID' = 5 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_TPG] = _("TPGID");
|
|
|
|
|
Desc_nlstab[EU_TPG] = _("Tty Process Grp Id");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'SID' = 5 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_SID] = _("SID");
|
|
|
|
|
Desc_nlstab[EU_SID] = _("Session Id");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'PR' = 3 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_PRI] = _("PR");
|
|
|
|
|
Desc_nlstab[EU_PRI] = _("Priority");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'NI' = 3 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_NCE] = _("NI");
|
|
|
|
|
Desc_nlstab[EU_NCE] = _("Nice Value");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'nTH' = 3 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_THD] = _("nTH");
|
|
|
|
|
Desc_nlstab[EU_THD] = _("Number of Threads");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'P' = 1 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_CPN] = _("P");
|
|
|
|
|
Desc_nlstab[EU_CPN] = _("Last Used Cpu (SMP)");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum '%CPU' = 4 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_CPU] = _("%CPU");
|
|
|
|
|
Desc_nlstab[EU_CPU] = _("CPU Usage");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum '' = 6 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_TME] = _("TIME");
|
|
|
|
|
Desc_nlstab[EU_TME] = _("CPU Time");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'TIME+' = 9 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_TM2] = _("TIME+");
|
|
|
|
|
Desc_nlstab[EU_TM2] = _("CPU Time, hundredths");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum '%MEM' = 4 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_MEM] = _("%MEM");
|
|
|
|
|
Desc_nlstab[EU_MEM] = _("Memory Usage (RES)");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'VIRT' = 5 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_VRT] = _("VIRT");
|
|
|
|
|
Desc_nlstab[EU_VRT] = _("Virtual Image (KiB)");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'SWAP' = 4 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_SWP] = _("SWAP");
|
|
|
|
|
Desc_nlstab[EU_SWP] = _("Swapped Size (KiB)");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'RES' = 4 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_RES] = _("RES");
|
|
|
|
|
Desc_nlstab[EU_RES] = _("Resident Size (KiB)");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'CODE' = 4 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_COD] = _("CODE");
|
|
|
|
|
Desc_nlstab[EU_COD] = _("Code Size (KiB)");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'DATA' = 4 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_DAT] = _("DATA");
|
|
|
|
|
Desc_nlstab[EU_DAT] = _("Data+Stack (KiB)");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'SHR' = 4 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_SHR] = _("SHR");
|
|
|
|
|
Desc_nlstab[EU_SHR] = _("Shared Memory (KiB)");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'nMaj' = 4 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_FL1] = _("nMaj");
|
|
|
|
|
Desc_nlstab[EU_FL1] = _("Major Page Faults");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'nMin' = 4 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_FL2] = _("nMin");
|
|
|
|
|
Desc_nlstab[EU_FL2] = _("Minor Page Faults");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'nDRT' = 4 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_DRT] = _("nDRT");
|
|
|
|
|
Desc_nlstab[EU_DRT] = _("Dirty Pages Count");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'S' = 1 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_STA] = _("S");
|
|
|
|
|
Desc_nlstab[EU_STA] = _("Process Status");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'COMMAND' = 7 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_CMD] = _("COMMAND");
|
|
|
|
|
Desc_nlstab[EU_CMD] = _("Command Name/Line");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'WCHAN' = 7 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_WCH] = _("WCHAN");
|
|
|
|
|
Desc_nlstab[EU_WCH] = _("Sleeping in Function");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'Flags' = 8 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_FLG] = _("Flags");
|
|
|
|
|
Desc_nlstab[EU_FLG] = _("Task Flags <sched.h>");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'CGROUPS' = 7 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_CGR] = _("CGROUPS");
|
|
|
|
|
Desc_nlstab[EU_CGR] = _("Control Groups");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'SUPGIDS' = 7 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_SGD] = _("SUPGIDS");
|
|
|
|
|
Desc_nlstab[EU_SGD] = _("Supp Groups IDs");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'SUPGRPS' = 7 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_SGN] = _("SUPGRPS");
|
|
|
|
|
Desc_nlstab[EU_SGN] = _("Supp Groups Names");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'TGID' = 5 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_TGD] = _("TGID");
|
|
|
|
|
Desc_nlstab[EU_TGD] = _("Thread Group Id");
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
#ifdef OOMEM_ENABLE
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'Adj' = 3 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_OOA] = _("Adj");
|
|
|
|
|
Desc_nlstab[EU_OOA] = _("oom_adjustment (2^X)");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'Badness' = 8 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_OOM] = _("Badness");
|
|
|
|
|
Desc_nlstab[EU_OOM] = _("oom_score (badness)");
|
2011-10-12 00:32:59 +05:30
|
|
|
#endif
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'ENVIRON' = 7 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_ENV] = _("ENVIRON");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: the abbreviation 'vars' below is shorthand for
|
2012-07-01 10:30:22 +05:30
|
|
|
'variables' */
|
2014-02-25 11:30:00 +05:30
|
|
|
Desc_nlstab[EU_ENV] = _("Environment vars");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'vMj' = 3 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_FV1] = _("vMj");
|
|
|
|
|
Desc_nlstab[EU_FV1] = _("Major Faults delta");
|
2012-09-19 12:32:02 +05:30
|
|
|
/* Translation Hint: maximum 'vMn' = 3 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_FV2] = _("vMn");
|
|
|
|
|
Desc_nlstab[EU_FV2] = _("Minor Faults delta");
|
2013-02-28 11:30:00 +05:30
|
|
|
/* Translation Hint: maximum 'USED' = 4 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_USE] = _("USED");
|
|
|
|
|
Desc_nlstab[EU_USE] = _("Res+Swap Size (KiB)");
|
2013-11-11 11:30:00 +05:30
|
|
|
/* Translation Hint: maximum 'nsIPC' = 10 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_NS1] = _("nsIPC");
|
|
|
|
|
Desc_nlstab[EU_NS1] = _("IPC namespace Inode");
|
2013-11-11 11:30:00 +05:30
|
|
|
/* Translation Hint: maximum 'nsMNT' = 10 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_NS2] = _("nsMNT");
|
|
|
|
|
Desc_nlstab[EU_NS2] = _("MNT namespace Inode");
|
2013-11-11 11:30:00 +05:30
|
|
|
/* Translation Hint: maximum 'nsNET' = 10 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_NS3] = _("nsNET");
|
|
|
|
|
Desc_nlstab[EU_NS3] = _("NET namespace Inode");
|
2013-11-11 11:30:00 +05:30
|
|
|
/* Translation Hint: maximum 'nsPID' = 10 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_NS4] = _("nsPID");
|
|
|
|
|
Desc_nlstab[EU_NS4] = _("PID namespace Inode");
|
2013-11-11 11:30:00 +05:30
|
|
|
/* Translation Hint: maximum 'nsUSER' = 10 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_NS5] = _("nsUSER");
|
|
|
|
|
Desc_nlstab[EU_NS5] = _("USER namespace Inode");
|
2013-11-11 11:30:00 +05:30
|
|
|
/* Translation Hint: maximum 'nsUTS' = 10 */
|
2014-02-25 11:30:00 +05:30
|
|
|
Head_nlstab[EU_NS6] = _("nsUTS");
|
|
|
|
|
Desc_nlstab[EU_NS6] = _("UTS namespace Inode");
|
2011-10-12 00:32:59 +05:30
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* This routine builds the nls table containing both plain text
|
|
|
|
|
* and regular c-format strings. */
|
|
|
|
|
static void build_norm_nlstab (void) {
|
|
|
|
|
|
2011-11-07 04:38:43 +05:30
|
|
|
/* Translation Notes ------------------------------------------------
|
|
|
|
|
. It is strongly recommend that the --no-wrap command line option
|
|
|
|
|
. be used with all supporting translation tools, when available.
|
|
|
|
|
.
|
|
|
|
|
. This group of lines contains both plain text and c-format strings.
|
|
|
|
|
.
|
|
|
|
|
. Some strings reflect switches used to affect the running program
|
|
|
|
|
. and should not be translated without also making corresponding
|
|
|
|
|
. c-code logic changes.
|
|
|
|
|
. */
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2012-12-12 11:30:00 +05:30
|
|
|
Norm_nlstab[EXIT_signals_fmt] = _(""
|
2011-10-12 00:32:59 +05:30
|
|
|
"\tsignal %d (%s) was caught by %s, please\n"
|
2011-12-07 16:11:14 +05:30
|
|
|
"\tsee http://www.debian.org/Bugs/Reporting\n");
|
|
|
|
|
Norm_nlstab[WRONG_switch_fmt] = _(""
|
2011-10-12 00:32:59 +05:30
|
|
|
"inappropriate '%s'\n"
|
2012-12-13 11:30:00 +05:30
|
|
|
"Usage:\n %s%s");
|
2011-12-07 16:11:14 +05:30
|
|
|
Norm_nlstab[HELP_cmdline_fmt] = _(""
|
2012-12-13 11:30:00 +05:30
|
|
|
" %s\n"
|
|
|
|
|
"Usage:\n %s%s");
|
2011-12-07 16:11:14 +05:30
|
|
|
Norm_nlstab[FAIL_statopn_fmt] = _("failed /proc/stat open: %s");
|
|
|
|
|
Norm_nlstab[FAIL_openlib_fmt] = _("failed openproc: %s");
|
|
|
|
|
Norm_nlstab[BAD_delayint_fmt] = _("bad delay interval '%s'");
|
|
|
|
|
Norm_nlstab[BAD_niterate_fmt] = _("bad iterations argument '%s'");
|
|
|
|
|
Norm_nlstab[LIMIT_exceed_fmt] = _("pid limit (%d) exceeded");
|
|
|
|
|
Norm_nlstab[BAD_mon_pids_fmt] = _("bad pid '%s'");
|
|
|
|
|
Norm_nlstab[MISSING_args_fmt] = _("-%c requires argument");
|
|
|
|
|
Norm_nlstab[BAD_widtharg_fmt] = _("bad width arg '%s', must > %d");
|
|
|
|
|
Norm_nlstab[UNKNOWN_opts_fmt] = _(""
|
2011-10-12 00:32:59 +05:30
|
|
|
"unknown option '%c'\n"
|
2012-12-13 11:30:00 +05:30
|
|
|
"Usage:\n %s%s");
|
2011-12-07 16:11:14 +05:30
|
|
|
Norm_nlstab[DELAY_secure_txt] = _("-d disallowed in \"secure\" mode");
|
|
|
|
|
Norm_nlstab[DELAY_badarg_txt] = _("-d requires positive argument");
|
|
|
|
|
Norm_nlstab[ON_word_only_txt] = _("On");
|
|
|
|
|
Norm_nlstab[OFF_one_word_txt] = _("Off");
|
2011-11-07 04:38:43 +05:30
|
|
|
/* Translation Hint: Only the following words should be translated
|
2013-03-19 10:30:00 +05:30
|
|
|
. secs (seconds), max (maximum), user, field, cols (columns)*/
|
2012-12-13 11:30:00 +05:30
|
|
|
Norm_nlstab[USAGE_abbrev_txt] = _(" -hv | -bcHiOSs -d secs -n max -u|U user -p pid(s) -o field -w [cols]");
|
2011-12-07 16:11:14 +05:30
|
|
|
Norm_nlstab[FAIL_statget_txt] = _("failed /proc/stat read");
|
|
|
|
|
Norm_nlstab[FOREST_modes_fmt] = _("Forest mode %s");
|
|
|
|
|
Norm_nlstab[FAIL_tty_get_txt] = _("failed tty get");
|
2013-01-16 11:30:00 +05:30
|
|
|
Norm_nlstab[FAIL_tty_set_fmt] = _("failed tty set: %s");
|
2011-12-07 16:11:14 +05:30
|
|
|
Norm_nlstab[CHOOSE_group_txt] = _("Choose field group (1 - 4)");
|
|
|
|
|
Norm_nlstab[DISABLED_cmd_txt] = _("Command disabled, 'A' mode required");
|
|
|
|
|
Norm_nlstab[DISABLED_win_fmt] = _("Command disabled, activate %s with '-' or '_'");
|
|
|
|
|
Norm_nlstab[COLORS_nomap_txt] = _("No colors to map!");
|
|
|
|
|
Norm_nlstab[FAIL_rc_open_fmt] = _("Failed '%s' open: %s");
|
|
|
|
|
Norm_nlstab[WRITE_rcfile_fmt] = _("Wrote configuration to '%s'");
|
|
|
|
|
Norm_nlstab[DELAY_change_fmt] = _("Change delay from %.1f to");
|
|
|
|
|
Norm_nlstab[THREADS_show_fmt] = _("Show threads %s");
|
|
|
|
|
Norm_nlstab[IRIX_curmode_fmt] = _("Irix mode %s");
|
2012-11-25 10:30:03 +05:30
|
|
|
Norm_nlstab[GET_pid2kill_fmt] = _("PID to signal/kill [default pid = %d]");
|
2011-12-07 16:11:14 +05:30
|
|
|
Norm_nlstab[GET_sigs_num_fmt] = _("Send pid %d signal [%d/sigterm]");
|
|
|
|
|
Norm_nlstab[FAIL_signals_fmt] = _("Failed signal pid '%d' with '%d': %s");
|
|
|
|
|
Norm_nlstab[BAD_signalid_txt] = _("Invalid signal");
|
2012-11-25 10:30:03 +05:30
|
|
|
Norm_nlstab[GET_pid2nice_fmt] = _("PID to renice [default pid = %d]");
|
2011-12-07 16:11:14 +05:30
|
|
|
Norm_nlstab[GET_nice_num_fmt] = _("Renice PID %d to value");
|
|
|
|
|
Norm_nlstab[FAIL_re_nice_fmt] = _("Failed renice of PID %d to %d: %s");
|
|
|
|
|
Norm_nlstab[NAME_windows_fmt] = _("Rename window '%s' to (1-3 chars)");
|
|
|
|
|
Norm_nlstab[TIME_accumed_fmt] = _("Cumulative time %s");
|
|
|
|
|
Norm_nlstab[GET_max_task_fmt] = _("Maximum tasks = %d, change to (0 is unlimited)");
|
|
|
|
|
Norm_nlstab[BAD_max_task_txt] = _("Invalid maximum");
|
|
|
|
|
Norm_nlstab[HILIGHT_cant_txt] = _("Nothing to highlight!");
|
|
|
|
|
Norm_nlstab[GET_user_ids_txt] = _("Which user (blank for all)");
|
|
|
|
|
Norm_nlstab[UNKNOWN_cmds_txt] = _("Unknown command - try 'h' for help");
|
2012-06-30 10:30:22 +05:30
|
|
|
Norm_nlstab[SCROLL_coord_fmt] = _("scroll coordinates: y = %d/%%d (tasks), x = %d/%d (fields)");
|
2011-12-07 16:11:14 +05:30
|
|
|
Norm_nlstab[FAIL_alloc_c_txt] = _("failed memory allocate");
|
|
|
|
|
Norm_nlstab[FAIL_alloc_r_txt] = _("failed memory re-allocate");
|
|
|
|
|
Norm_nlstab[BAD_numfloat_txt] = _("Unacceptable floating point");
|
|
|
|
|
Norm_nlstab[BAD_username_txt] = _("Invalid user");
|
|
|
|
|
Norm_nlstab[FOREST_views_txt] = _("forest view");
|
|
|
|
|
Norm_nlstab[FAIL_widepid_txt] = _("failed pid maximum size test");
|
|
|
|
|
Norm_nlstab[FAIL_widecpu_txt] = _("failed number of cpus test");
|
|
|
|
|
Norm_nlstab[RC_bad_files_fmt] = _("incompatible rcfile, you should delete '%s'");
|
|
|
|
|
Norm_nlstab[RC_bad_entry_fmt] = _("window entry #%d corrupt, please delete '%s'");
|
|
|
|
|
Norm_nlstab[NOT_onsecure_txt] = _("Unavailable in secure mode");
|
|
|
|
|
Norm_nlstab[NOT_smp_cpus_txt] = _("Only 1 cpu detected");
|
|
|
|
|
Norm_nlstab[BAD_integers_txt] = _("Unacceptable integer");
|
|
|
|
|
Norm_nlstab[SELECT_clash_txt] = _("conflicting process selections (U/p/u)");
|
2012-03-07 18:37:07 +05:30
|
|
|
/* Translation Hint: This is an abbreviation (limit 3 characters) for:
|
|
|
|
|
. kibibytes (1024 bytes) */
|
|
|
|
|
Norm_nlstab[AMT_kilobyte_txt] = _("KiB");
|
|
|
|
|
/* Translation Hint: This is an abbreviation (limit 3 characters) for:
|
|
|
|
|
. mebibytes (1,048,576 bytes) */
|
|
|
|
|
Norm_nlstab[AMT_megabyte_txt] = _("MiB");
|
|
|
|
|
/* Translation Hint: This is an abbreviation (limit 3 characters) for:
|
|
|
|
|
. gibibytes (1,073,741,824 bytes) */
|
|
|
|
|
Norm_nlstab[AMT_gigabyte_txt] = _("GiB");
|
2012-12-14 11:30:00 +05:30
|
|
|
/* Translation Hint: This is an abbreviation (limit 3 characters) for:
|
|
|
|
|
. tebibytes (1,099,511,627,776 bytes) */
|
|
|
|
|
Norm_nlstab[AMT_terabyte_txt] = _("TiB");
|
2012-12-18 11:30:00 +05:30
|
|
|
/* Translation Hint: This is an abbreviation (limit 3 characters) for:
|
|
|
|
|
. pebibytes (1,024 tebibytes) */
|
|
|
|
|
Norm_nlstab[AMT_petabyte_txt] = _("PiB");
|
|
|
|
|
/* Translation Hint: This is an abbreviation (limit 3 characters) for:
|
|
|
|
|
. exbibytes (1,024 pebibytes) */
|
|
|
|
|
Norm_nlstab[AMT_exxabyte_txt] = _("EiB");
|
2011-12-07 16:11:14 +05:30
|
|
|
Norm_nlstab[WORD_threads_txt] = _("Threads");
|
|
|
|
|
Norm_nlstab[WORD_process_txt] = _("Tasks");
|
2011-11-07 14:38:27 +05:30
|
|
|
/* Translation Hint: The following "word" is meant to represent either a single
|
|
|
|
|
. cpu or all of the processors in a multi-processor computer
|
|
|
|
|
. (should be exactly 6 characters, not counting the colon)*/
|
2011-12-07 16:11:14 +05:30
|
|
|
Norm_nlstab[WORD_allcpus_txt] = _("Cpu(s):");
|
2011-11-07 14:38:27 +05:30
|
|
|
/* Translation Hint: The following "word" is meant to represent a single processor
|
|
|
|
|
. (should be exactly 3 characters) */
|
2011-12-07 16:11:14 +05:30
|
|
|
Norm_nlstab[WORD_eachcpu_fmt] = _("Cpu%-3d:");
|
2011-12-21 02:13:54 +05:30
|
|
|
/* Translation Hint: The following word "another" must have 1 trailing space */
|
|
|
|
|
Norm_nlstab[WORD_another_txt] = _("another ");
|
|
|
|
|
Norm_nlstab[FIND_no_next_txt] = _("Locate next inactive, use \"L\"");
|
|
|
|
|
Norm_nlstab[GET_find_str_txt] = _("Locate string");
|
|
|
|
|
Norm_nlstab[FIND_no_find_fmt] = _("%s\"%s\" not found");
|
2012-10-03 23:43:13 +05:30
|
|
|
Norm_nlstab[XTRA_fixwide_fmt] = _("width incr is %d, change to (0 default, -1 auto)");
|
2012-12-02 11:30:00 +05:30
|
|
|
Norm_nlstab[XTRA_warncfg_txt] = _("Overwrite existing obsolete/corrupted rcfile?");
|
2013-03-03 11:30:00 +05:30
|
|
|
Norm_nlstab[XTRA_badflds_fmt] = _("unrecognized field name '%s'");
|
2013-01-29 11:30:00 +05:30
|
|
|
Norm_nlstab[XTRA_winsize_txt] = _("even using field names only, window is now too small");
|
top: add a flexible 'Inspect' capability
This commit introduces an extremely powerful, flexible
brand new capability. Now, users can pause the normal
iterative display and inspect the contents of any file
or output from any script, command, or even pipelines.
It's invoked via the 'Y' interactive command which, in
turn, is supported with simple user supplied additions
as new entries in the top personal configuration file.
A separate new 'Inspect' window supports scrolling and
searching, similar to the main top display. Except it
extends existing 'L'/'&' (locate/locate-next) commands
so that an out-of-view match automatically adjusts the
horizontal position bringing such data into view. And
it provides for multiple successive same line matches.
Also, the basic 'more/less' navigation keys are active
in this new 'Inspect' window, to ease user transition.
There are no program changes required when entries are
added to or deleted from the rcfile. And there are no
known limits to the complexity of a script, command or
pipeline, other than the unidirectional nature imposed
by the 'popen' function call which top cannot violate.
Since it's impossible to predict exactly what contents
will be generated, top treats all output as raw binary
data. Any control characters display in '^C' notation
while all other unprintable characters show as '<AB>'.
The biggest problem encountered was with the find/next
capability since that strstr guy was really diminished
given the possibility that numerous 'strings' could be
encountered *within* many of top's raw, binary 'rows'.
Oh, and another problem was in maintaining the perfect
left & right text justification of this commit message
along with all of the commit summaries. Some of those
summaries (like this very one) are of course, slightly
shorter, to make room for the 'man document' addition.
Enjoy!
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-11-25 10:30:05 +05:30
|
|
|
#ifndef INSP_OFFDEMO
|
|
|
|
|
Norm_nlstab[YINSP_demo01_txt] = _("Open Files");
|
|
|
|
|
Norm_nlstab[YINSP_demo02_txt] = _("NUMA Info");
|
|
|
|
|
Norm_nlstab[YINSP_demo03_txt] = _("Log");
|
2012-12-10 11:30:00 +05:30
|
|
|
Norm_nlstab[YINSP_deqfmt_txt] = _("the '=' key will eventually show the actual file read or command(s) excuted ...");
|
|
|
|
|
Norm_nlstab[YINSP_deqtyp_txt] = _("demo");
|
2012-12-04 11:30:00 +05:30
|
|
|
Norm_nlstab[YINSP_dstory_txt] = _(""
|
top: add a flexible 'Inspect' capability
This commit introduces an extremely powerful, flexible
brand new capability. Now, users can pause the normal
iterative display and inspect the contents of any file
or output from any script, command, or even pipelines.
It's invoked via the 'Y' interactive command which, in
turn, is supported with simple user supplied additions
as new entries in the top personal configuration file.
A separate new 'Inspect' window supports scrolling and
searching, similar to the main top display. Except it
extends existing 'L'/'&' (locate/locate-next) commands
so that an out-of-view match automatically adjusts the
horizontal position bringing such data into view. And
it provides for multiple successive same line matches.
Also, the basic 'more/less' navigation keys are active
in this new 'Inspect' window, to ease user transition.
There are no program changes required when entries are
added to or deleted from the rcfile. And there are no
known limits to the complexity of a script, command or
pipeline, other than the unidirectional nature imposed
by the 'popen' function call which top cannot violate.
Since it's impossible to predict exactly what contents
will be generated, top treats all output as raw binary
data. Any control characters display in '^C' notation
while all other unprintable characters show as '<AB>'.
The biggest problem encountered was with the find/next
capability since that strstr guy was really diminished
given the possibility that numerous 'strings' could be
encountered *within* many of top's raw, binary 'rows'.
Oh, and another problem was in maintaining the perfect
left & right text justification of this commit message
along with all of the commit summaries. Some of those
summaries (like this very one) are of course, slightly
shorter, to make room for the 'man document' addition.
Enjoy!
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-11-25 10:30:05 +05:30
|
|
|
"This is simulated output representing the contents of some file or the output\n"
|
|
|
|
|
"from some command. Exactly which commands and/or files are solely up to you.\n"
|
|
|
|
|
"\n"
|
|
|
|
|
"Although this text is for information purposes only, it can still be scrolled\n"
|
|
|
|
|
"and searched like real output will be. You are encouraged to experiment with\n"
|
|
|
|
|
"those features as explained in the prologue above.\n"
|
|
|
|
|
"\n"
|
|
|
|
|
"To enable real Inspect functionality, entries must be added to the end of the\n"
|
|
|
|
|
"top personal personal configuration file. You could use your favorite editor\n"
|
|
|
|
|
"to accomplish this, taking care not to disturb existing entries.\n"
|
|
|
|
|
"\n"
|
|
|
|
|
"Another way to add entries is illustrated below, but it risks overwriting the\n"
|
|
|
|
|
"rcfile. Redirected echoes must not replace (>) but append (>>) to that file.\n"
|
|
|
|
|
"\n"
|
|
|
|
|
" /bin/echo -e \"pipe\\tOpen Files\\tlsof -P -p %d 2>&1\" >> ~/.toprc\n"
|
|
|
|
|
" /bin/echo -e \"file\\tNUMA Info\\t/proc/%d/numa_maps\" >> ~/.toprc\n"
|
|
|
|
|
" /bin/echo -e \"pipe\\tLog\\ttail -n200 /var/log/syslog | sort -Mr\" >> ~/.toprc\n"
|
|
|
|
|
"\n"
|
|
|
|
|
"If you don't know the location or name of the top rcfile, use the 'W' command\n"
|
|
|
|
|
"and note those details. After backing up the current rcfile, try issuing the\n"
|
|
|
|
|
"above echoes exactly as shown, replacing '.toprc' as appropriate. The safest\n"
|
|
|
|
|
"approach would be to use copy then paste to avoid any typing mistakes.\n"
|
|
|
|
|
"\n"
|
|
|
|
|
"Finally, restart top to reveal what actual Inspect entries combined with this\n"
|
|
|
|
|
"new command can offer. The possibilities are endless, especially considering\n"
|
|
|
|
|
"that 'pipe' type entries can include shell scripts too!\n"
|
|
|
|
|
"\n"
|
|
|
|
|
"For additional important information, please consult the top documentation.\n"
|
|
|
|
|
"Then enhance top with your very own customized 'file' and 'pipe' entries.\n"
|
|
|
|
|
"\n"
|
|
|
|
|
"Enjoy!\n");
|
|
|
|
|
Norm_nlstab[YINSP_noents_txt] = _("to enable 'Y' press <Enter> then type 'W' and restart top");
|
|
|
|
|
#else
|
|
|
|
|
Norm_nlstab[YINSP_noents_txt] = _("to enable 'Y' please consult the top man page (press Enter)");
|
|
|
|
|
#endif
|
2012-12-04 11:30:00 +05:30
|
|
|
Norm_nlstab[YINSP_failed_fmt] = _("Selection failed with: %s\n");
|
top: add a flexible 'Inspect' capability
This commit introduces an extremely powerful, flexible
brand new capability. Now, users can pause the normal
iterative display and inspect the contents of any file
or output from any script, command, or even pipelines.
It's invoked via the 'Y' interactive command which, in
turn, is supported with simple user supplied additions
as new entries in the top personal configuration file.
A separate new 'Inspect' window supports scrolling and
searching, similar to the main top display. Except it
extends existing 'L'/'&' (locate/locate-next) commands
so that an out-of-view match automatically adjusts the
horizontal position bringing such data into view. And
it provides for multiple successive same line matches.
Also, the basic 'more/less' navigation keys are active
in this new 'Inspect' window, to ease user transition.
There are no program changes required when entries are
added to or deleted from the rcfile. And there are no
known limits to the complexity of a script, command or
pipeline, other than the unidirectional nature imposed
by the 'popen' function call which top cannot violate.
Since it's impossible to predict exactly what contents
will be generated, top treats all output as raw binary
data. Any control characters display in '^C' notation
while all other unprintable characters show as '<AB>'.
The biggest problem encountered was with the find/next
capability since that strstr guy was really diminished
given the possibility that numerous 'strings' could be
encountered *within* many of top's raw, binary 'rows'.
Oh, and another problem was in maintaining the perfect
left & right text justification of this commit message
along with all of the commit summaries. Some of those
summaries (like this very one) are of course, slightly
shorter, to make room for the 'man document' addition.
Enjoy!
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-11-25 10:30:05 +05:30
|
|
|
Norm_nlstab[YINSP_pidbad_fmt] = _("unable to inspect, pid %d not found");
|
2012-12-05 11:30:00 +05:30
|
|
|
Norm_nlstab[YINSP_pidsee_fmt] = _("inspect at PID [default pid = %d]");
|
top: add a flexible 'Inspect' capability
This commit introduces an extremely powerful, flexible
brand new capability. Now, users can pause the normal
iterative display and inspect the contents of any file
or output from any script, command, or even pipelines.
It's invoked via the 'Y' interactive command which, in
turn, is supported with simple user supplied additions
as new entries in the top personal configuration file.
A separate new 'Inspect' window supports scrolling and
searching, similar to the main top display. Except it
extends existing 'L'/'&' (locate/locate-next) commands
so that an out-of-view match automatically adjusts the
horizontal position bringing such data into view. And
it provides for multiple successive same line matches.
Also, the basic 'more/less' navigation keys are active
in this new 'Inspect' window, to ease user transition.
There are no program changes required when entries are
added to or deleted from the rcfile. And there are no
known limits to the complexity of a script, command or
pipeline, other than the unidirectional nature imposed
by the 'popen' function call which top cannot violate.
Since it's impossible to predict exactly what contents
will be generated, top treats all output as raw binary
data. Any control characters display in '^C' notation
while all other unprintable characters show as '<AB>'.
The biggest problem encountered was with the find/next
capability since that strstr guy was really diminished
given the possibility that numerous 'strings' could be
encountered *within* many of top's raw, binary 'rows'.
Oh, and another problem was in maintaining the perfect
left & right text justification of this commit message
along with all of the commit summaries. Some of those
summaries (like this very one) are of course, slightly
shorter, to make room for the 'man document' addition.
Enjoy!
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-11-25 10:30:05 +05:30
|
|
|
Norm_nlstab[YINSP_rcfile_fmt] = _("could not parse rcfile inspect entry %d");
|
2012-11-28 11:30:00 +05:30
|
|
|
Norm_nlstab[YINSP_status_fmt] = _("%s: %*d-%-*d lines, %*d-%*d columns, %lu bytes read");
|
top: add a flexible 'Inspect' capability
This commit introduces an extremely powerful, flexible
brand new capability. Now, users can pause the normal
iterative display and inspect the contents of any file
or output from any script, command, or even pipelines.
It's invoked via the 'Y' interactive command which, in
turn, is supported with simple user supplied additions
as new entries in the top personal configuration file.
A separate new 'Inspect' window supports scrolling and
searching, similar to the main top display. Except it
extends existing 'L'/'&' (locate/locate-next) commands
so that an out-of-view match automatically adjusts the
horizontal position bringing such data into view. And
it provides for multiple successive same line matches.
Also, the basic 'more/less' navigation keys are active
in this new 'Inspect' window, to ease user transition.
There are no program changes required when entries are
added to or deleted from the rcfile. And there are no
known limits to the complexity of a script, command or
pipeline, other than the unidirectional nature imposed
by the 'popen' function call which top cannot violate.
Since it's impossible to predict exactly what contents
will be generated, top treats all output as raw binary
data. Any control characters display in '^C' notation
while all other unprintable characters show as '<AB>'.
The biggest problem encountered was with the find/next
capability since that strstr guy was really diminished
given the possibility that numerous 'strings' could be
encountered *within* many of top's raw, binary 'rows'.
Oh, and another problem was in maintaining the perfect
left & right text justification of this commit message
along with all of the commit summaries. Some of those
summaries (like this very one) are of course, slightly
shorter, to make room for the 'man document' addition.
Enjoy!
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-11-25 10:30:05 +05:30
|
|
|
Norm_nlstab[YINSP_workin_txt] = _("patience please, working...");
|
2013-03-03 11:30:00 +05:30
|
|
|
/* Translation Hint: Below are 2 abbreviations which can be as long as needed:
|
|
|
|
|
. FLD = FIELD, VAL = VALUE */
|
2013-03-05 11:30:00 +05:30
|
|
|
Norm_nlstab[OSEL_prompts_fmt] = _("add filter #%d (%s) as: [!]FLD?VAL");
|
2013-03-03 11:30:00 +05:30
|
|
|
Norm_nlstab[OSEL_casenot_txt] = _("ignoring case");
|
|
|
|
|
Norm_nlstab[OSEL_caseyes_txt] = _("case sensitive");
|
|
|
|
|
Norm_nlstab[OSEL_errdups_txt] = _("duplicate filter was ignored");
|
|
|
|
|
Norm_nlstab[OSEL_errdelm_fmt] = _("'%s' filter delimiter is missing");
|
|
|
|
|
Norm_nlstab[OSEL_errvalu_fmt] = _("'%s' filter value is missing");
|
|
|
|
|
Norm_nlstab[WORD_include_txt] = _("include");
|
|
|
|
|
Norm_nlstab[WORD_exclude_txt] = _("exclude");
|
2013-03-05 11:30:00 +05:30
|
|
|
Norm_nlstab[OSEL_statlin_fmt] = _("<Enter> to resume, filters: %s");
|
2013-03-03 11:30:00 +05:30
|
|
|
Norm_nlstab[WORD_noneone_txt] = _("none");
|
2013-04-08 12:30:00 +05:30
|
|
|
Norm_nlstab[NUMA_nodenam_fmt] = _("Node%-2d:");
|
|
|
|
|
Norm_nlstab[NUMA_nodeget_fmt] = _("expand which node (0-%d)");
|
|
|
|
|
Norm_nlstab[NUMA_nodebad_txt] = _("invalid node");
|
|
|
|
|
Norm_nlstab[NUMA_nodenot_txt] = _("sorry, NUMA extensions unavailable");
|
2011-10-12 00:32:59 +05:30
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* This routine builds the nls table containing specially
|
|
|
|
|
* formatted strings designed to fit within an 80x24 terminal. */
|
2011-11-06 05:04:50 +05:30
|
|
|
static void build_uniq_nlstab (void) {
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-11-07 04:38:43 +05:30
|
|
|
/* Translation Notes ------------------------------------------------
|
|
|
|
|
. It is strongly recommend that the --no-wrap command line option
|
|
|
|
|
. be used with all supporting translation tools, when available.
|
|
|
|
|
.
|
|
|
|
|
. The next several text groups contain special escape sequences
|
|
|
|
|
. representing values used to index a table at run-time.
|
|
|
|
|
.
|
|
|
|
|
. Each such sequence consists of a tilde (~) followed by an ascii
|
2011-12-07 17:10:37 +05:30
|
|
|
. number in the range of '1' - '8'. Examples are '~2', '~8', etc.
|
2011-11-07 04:38:43 +05:30
|
|
|
. These escape sequences must never themselves be translated but
|
|
|
|
|
. could be deleted.
|
|
|
|
|
.
|
|
|
|
|
. If you remove these escape sequences (both tilde and number) it
|
|
|
|
|
. would make translation easier. However, the ability to display
|
|
|
|
|
. colors and bold text at run-time will have been lost.
|
|
|
|
|
.
|
|
|
|
|
. Additionally, each of these text groups was designed to display
|
|
|
|
|
. in a 80x24 terminal window. Hopefully, any translations will
|
|
|
|
|
. adhere to that goal lest the translated text be truncated.
|
|
|
|
|
.
|
|
|
|
|
. If you would like additional information regarding these strings,
|
top: add a flexible 'Inspect' capability
This commit introduces an extremely powerful, flexible
brand new capability. Now, users can pause the normal
iterative display and inspect the contents of any file
or output from any script, command, or even pipelines.
It's invoked via the 'Y' interactive command which, in
turn, is supported with simple user supplied additions
as new entries in the top personal configuration file.
A separate new 'Inspect' window supports scrolling and
searching, similar to the main top display. Except it
extends existing 'L'/'&' (locate/locate-next) commands
so that an out-of-view match automatically adjusts the
horizontal position bringing such data into view. And
it provides for multiple successive same line matches.
Also, the basic 'more/less' navigation keys are active
in this new 'Inspect' window, to ease user transition.
There are no program changes required when entries are
added to or deleted from the rcfile. And there are no
known limits to the complexity of a script, command or
pipeline, other than the unidirectional nature imposed
by the 'popen' function call which top cannot violate.
Since it's impossible to predict exactly what contents
will be generated, top treats all output as raw binary
data. Any control characters display in '^C' notation
while all other unprintable characters show as '<AB>'.
The biggest problem encountered was with the find/next
capability since that strstr guy was really diminished
given the possibility that numerous 'strings' could be
encountered *within* many of top's raw, binary 'rows'.
Oh, and another problem was in maintaining the perfect
left & right text justification of this commit message
along with all of the commit summaries. Some of those
summaries (like this very one) are of course, slightly
shorter, to make room for the 'man document' addition.
Enjoy!
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-11-25 10:30:05 +05:30
|
|
|
. please see the prologue to the show_special function in the top.c
|
2011-11-07 04:38:43 +05:30
|
|
|
. source file.
|
|
|
|
|
. */
|
2011-10-14 22:15:44 +05:30
|
|
|
|
2011-12-07 16:11:14 +05:30
|
|
|
Uniq_nlstab[KEYS_helpbas_fmt] = _(""
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
"Help for Interactive Commands~2 - %s\n"
|
|
|
|
|
"Window ~1%s~6: ~1Cumulative mode ~3%s~2. ~1System~6: ~1Delay ~3%.1f secs~2; ~1Secure mode ~3%s~2.\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
"\n"
|
top: provide the means to adjust scaled process memory
This commit is an unrequested outgrowth of the earlier
change dealing with summary area memory field scaling.
That user selectable scaling provision is now extended
to include 6 (at present) task oriented memory fields.
The new companion 'e' (lower case) interactive command
has been added and, like the 'E' command, it can cycle
each of the currently displayed memory columns between
KiB through TiB. There are, however, some differences.
Where '+' indicates summary area truncation at a given
radix, task memory fields are automatically scaled for
their column. Thus, not all rows use the same scaling.
And, while summary area field widths were not changed,
the task memory columns were widened in order to offer
more meaningful data when the radix was increased. The
precision is automatically increased in step with each
radix: MiB displays 2 decimal places, GiB 3 and TiB 4.
To compliment that additional precision, both the %CPU
and %MEM fields were widened by 1 column and now offer
precision up to 3 decimal places. But, unique to %CPU,
widening could already have occurred due to the number
of processors in some massively parallel boxes. At any
rate, total extra width for both memory and percentage
fields could amount to twenty (precious) columns more.
So for both the memory and % fields the original width
(along with loss of precision) can be restored via new
compiler conditionals which this commit also provides.
p.s. and it will be rcfile preserved for any restarts!
(now that we know a '.' + 2 spaces is squeezed to one)
(everything's perfectly justified, but it's just luck)
Reference(s):
http://www.freelists.org/post/procps/top-regression-reports
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-12-14 11:30:00 +05:30
|
|
|
" Z~5,~1B~5,E,e Global: '~1Z~2' colors; '~1B~2' bold; '~1E~2'/'~1e~2' summary/task memory scale\n"
|
2012-12-23 11:30:00 +05:30
|
|
|
" l,t,m Toggle Summary: '~1l~2' load avg; '~1t~2' task/cpu stats; '~1m~2' memory info\n"
|
2013-04-08 12:30:00 +05:30
|
|
|
" 0,1,2,3,I Toggle: '~10~2' zeros; '~11~2/~12~2/~13~2' cpus or numa node views; '~1I~2' Irix mode\n"
|
2012-09-21 11:31:01 +05:30
|
|
|
" f,F,X Fields: '~1f~2'/'~1F~2' add/remove/order/sort; '~1X~2' increase fixed-width\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
"\n"
|
top: add a flexible 'Inspect' capability
This commit introduces an extremely powerful, flexible
brand new capability. Now, users can pause the normal
iterative display and inspect the contents of any file
or output from any script, command, or even pipelines.
It's invoked via the 'Y' interactive command which, in
turn, is supported with simple user supplied additions
as new entries in the top personal configuration file.
A separate new 'Inspect' window supports scrolling and
searching, similar to the main top display. Except it
extends existing 'L'/'&' (locate/locate-next) commands
so that an out-of-view match automatically adjusts the
horizontal position bringing such data into view. And
it provides for multiple successive same line matches.
Also, the basic 'more/less' navigation keys are active
in this new 'Inspect' window, to ease user transition.
There are no program changes required when entries are
added to or deleted from the rcfile. And there are no
known limits to the complexity of a script, command or
pipeline, other than the unidirectional nature imposed
by the 'popen' function call which top cannot violate.
Since it's impossible to predict exactly what contents
will be generated, top treats all output as raw binary
data. Any control characters display in '^C' notation
while all other unprintable characters show as '<AB>'.
The biggest problem encountered was with the find/next
capability since that strstr guy was really diminished
given the possibility that numerous 'strings' could be
encountered *within* many of top's raw, binary 'rows'.
Oh, and another problem was in maintaining the perfect
left & right text justification of this commit message
along with all of the commit summaries. Some of those
summaries (like this very one) are of course, slightly
shorter, to make room for the 'man document' addition.
Enjoy!
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-11-25 10:30:05 +05:30
|
|
|
" L,&,<,> . Locate: '~1L~2'/'~1&~2' find/again; Move sort column: '~1<~2'/'~1>~2' left/right\n"
|
2012-09-20 11:31:01 +05:30
|
|
|
" R,H,V,J . Toggle: '~1R~2' Sort; '~1H~2' Threads; '~1V~2' Forest view; '~1J~2' Num justify\n"
|
|
|
|
|
" c,i,S,j . Toggle: '~1c~2' Cmd name/line; '~1i~2' Idle; '~1S~2' Time; '~1j~2' Str justify\n"
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
" x~5,~1y~5 . Toggle highlights: '~1x~2' sort field; '~1y~2' running tasks\n"
|
|
|
|
|
" z~5,~1b~5 . Toggle: '~1z~2' color/mono; '~1b~2' bold/reverse (only if 'x' or 'y')\n"
|
2013-03-03 11:30:00 +05:30
|
|
|
" u,U,o,O . Filter by: '~1u~2'/'~1U~2' effective/any user; '~1o~2'/'~1O~2' other criteria\n"
|
|
|
|
|
" n,#,^O . Set: '~1n~2'/'~1#~2' max tasks displayed; Show: ~1Ctrl~2+'~1O~2' other filter(s)\n"
|
2012-12-23 11:30:00 +05:30
|
|
|
" C,... . Toggle scroll coordinates msg for: ~1up~2,~1down~2,~1left~2,~1right~2,~1home~2,~1end~2\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
"\n"
|
|
|
|
|
"%s"
|
top: add a flexible 'Inspect' capability
This commit introduces an extremely powerful, flexible
brand new capability. Now, users can pause the normal
iterative display and inspect the contents of any file
or output from any script, command, or even pipelines.
It's invoked via the 'Y' interactive command which, in
turn, is supported with simple user supplied additions
as new entries in the top personal configuration file.
A separate new 'Inspect' window supports scrolling and
searching, similar to the main top display. Except it
extends existing 'L'/'&' (locate/locate-next) commands
so that an out-of-view match automatically adjusts the
horizontal position bringing such data into view. And
it provides for multiple successive same line matches.
Also, the basic 'more/less' navigation keys are active
in this new 'Inspect' window, to ease user transition.
There are no program changes required when entries are
added to or deleted from the rcfile. And there are no
known limits to the complexity of a script, command or
pipeline, other than the unidirectional nature imposed
by the 'popen' function call which top cannot violate.
Since it's impossible to predict exactly what contents
will be generated, top treats all output as raw binary
data. Any control characters display in '^C' notation
while all other unprintable characters show as '<AB>'.
The biggest problem encountered was with the find/next
capability since that strstr guy was really diminished
given the possibility that numerous 'strings' could be
encountered *within* many of top's raw, binary 'rows'.
Oh, and another problem was in maintaining the perfect
left & right text justification of this commit message
along with all of the commit summaries. Some of those
summaries (like this very one) are of course, slightly
shorter, to make room for the 'man document' addition.
Enjoy!
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-11-25 10:30:05 +05:30
|
|
|
" W,Y Write configuration file '~1W~2'; Inspect other output '~1Y~2'\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
" q Quit\n"
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
" ( commands shown with '.' require a ~1visible~2 task display ~1window~2 ) \n"
|
|
|
|
|
"Press '~1h~2' or '~1?~2' for help with ~1Windows~2,\n"
|
2013-01-16 11:30:00 +05:30
|
|
|
"Type 'q' or <Esc> to continue ");
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-11-07 04:38:43 +05:30
|
|
|
/* Translation Hint: As is true for the text above, the "keys" shown to the left and
|
|
|
|
|
. also imbedded in the translatable text (along with escape seqs)
|
|
|
|
|
. should never themselves be translated. */
|
2011-12-07 16:11:14 +05:30
|
|
|
Uniq_nlstab[KEYS_helpext_fmt] = _(""
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
" k,r Manipulate tasks: '~1k~2' kill; '~1r~2' renice\n"
|
2011-12-07 16:11:14 +05:30
|
|
|
" d or s Set update interval\n");
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-12-07 16:11:14 +05:30
|
|
|
Uniq_nlstab[WINDOWS_help_fmt] = _(""
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
"Help for Windows / Field Groups~2 - \"Current Window\" = ~1 %s ~6\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
"\n"
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
". Use multiple ~1windows~2, each with separate config opts (color,fields,sort,etc)\n"
|
|
|
|
|
". The 'current' window controls the ~1Summary Area~2 and responds to your ~1Commands~2\n"
|
|
|
|
|
" . that window's ~1task display~2 can be turned ~1Off~2 & ~1On~2, growing/shrinking others\n"
|
|
|
|
|
" . with ~1NO~2 task display, some commands will be ~1disabled~2 ('i','R','n','c', etc)\n"
|
|
|
|
|
" until a ~1different window~2 has been activated, making it the 'current' window\n"
|
|
|
|
|
". You ~1change~2 the 'current' window by: ~1 1~2) cycling forward/backward;~1 2~2) choosing\n"
|
|
|
|
|
" a specific field group; or~1 3~2) exiting the color mapping or fields screens\n"
|
|
|
|
|
". Commands ~1available anytime -------------~2\n"
|
|
|
|
|
" A . Alternate display mode toggle, show ~1Single~2 / ~1Multiple~2 windows\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
" g . Choose another field group and make it 'current', or change now\n"
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
" by selecting a number from: ~1 1~2 =%s;~1 2~2 =%s;~1 3~2 =%s; or~1 4~2 =%s\n"
|
|
|
|
|
". Commands ~1requiring~2 '~1A~2' mode~1 -------------~2\n"
|
|
|
|
|
" G . Change the ~1Name~5 of the 'current' window/field group\n"
|
|
|
|
|
" ~1*~4 a , w . Cycle through all four windows: '~1a~5' Forward; '~1w~5' Backward\n"
|
|
|
|
|
" ~1*~4 - , _ . Show/Hide: '~1-~5' ~1Current~2 window; '~1_~5' all ~1Visible~2/~1Invisible~2\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
" The screen will be divided evenly between task displays. But you can make\n"
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
" some ~1larger~2 or ~1smaller~2, using '~1n~2' and '~1i~2' commands. Then later you could:\n"
|
|
|
|
|
" ~1*~4 = , + . Rebalance tasks: '~1=~5' ~1Current~2 window; '~1+~5' ~1Every~2 window\n"
|
|
|
|
|
" (this also forces the ~1current~2 or ~1every~2 window to become visible)\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
"\n"
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
"In '~1A~2' mode, '~1*~4' keys are your ~1essential~2 commands. Please try the '~1a~2' and '~1w~2'\n"
|
2011-12-07 16:11:14 +05:30
|
|
|
"commands plus the 'g' sub-commands NOW. Press <Enter> to make 'Current' ");
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-11-07 04:38:43 +05:30
|
|
|
/* Translation Notes ------------------------------------------------
|
|
|
|
|
. The following 'Help for color mapping' simulated screen should
|
|
|
|
|
. probably NOT be translated. It is terribly hard to follow in
|
|
|
|
|
. this form and any translation could produce unpleasing results
|
|
|
|
|
. that are unlikely to parallel the running top program.
|
|
|
|
|
.
|
|
|
|
|
. If you decide to proceed with translation, do the following
|
2011-12-07 17:10:37 +05:30
|
|
|
. lines only, taking care not to disturbe the tilde + number.
|
2011-11-07 04:38:43 +05:30
|
|
|
.
|
2011-12-07 17:10:37 +05:30
|
|
|
. Simulated screen excerpt:
|
2011-11-07 04:38:43 +05:30
|
|
|
. --> " Tasks:~3 64 ~2total,~3 2 ~3running,~3 62
|
|
|
|
|
. --> " %%Cpu(s):~3 76.5 ~2user,~3 11.2 ~2system,~
|
2011-12-07 17:10:37 +05:30
|
|
|
. --> " ~1 Nasty Message! ~4 -or- ~1Input Prompt~5
|
2011-11-07 04:38:43 +05:30
|
|
|
.
|
|
|
|
|
. --> " available toggles: ~1B~2 =disable bold globa
|
|
|
|
|
. --> " ~1z~2 =color/mono (~1%s~2), ~1b~2 =tasks
|
|
|
|
|
.
|
|
|
|
|
. --> "Select ~1target~2 as upper case letter:\n"
|
|
|
|
|
. --> " S~2 = Summary Data,~1 M~2 = Messages/Prompt
|
|
|
|
|
. --> " H~2 = Column Heads,~1 T~2 = Task Informatio
|
|
|
|
|
. --> "Select ~1color~2 as number:\n"
|
|
|
|
|
. --> " 0~2 = black,~1 1~2 = red, ~1 2~2 = gree
|
|
|
|
|
. --> " 4~2 = blue, ~1 5~2 = magenta,~1 6~2 = cyan
|
|
|
|
|
. */
|
2011-12-07 16:11:14 +05:30
|
|
|
Uniq_nlstab[COLOR_custom_fmt] = _(""
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
"Help for color mapping~2 - %s\n"
|
|
|
|
|
"current window: ~1%s~6\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
"\n"
|
|
|
|
|
" color - 04:25:44 up 8 days, 50 min, 7 users, load average:\n"
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
" Tasks:~3 64 ~2total,~3 2 ~3running,~3 62 ~2sleeping,~3 0 ~2stopped,~3\n"
|
|
|
|
|
" %%Cpu(s):~3 76.5 ~2user,~3 11.2 ~2system,~3 0.0 ~2nice,~3 12.3 ~2idle~3\n"
|
|
|
|
|
" ~1 Nasty Message! ~4 -or- ~1Input Prompt~5\n"
|
|
|
|
|
" ~1 PID TTY PR NI %%CPU TIME+ VIRT SWAP S COMMAND ~6\n"
|
|
|
|
|
" 17284 ~8pts/2 ~7 8 0 0.0 0:00.75 1380 0 S /bin/bash ~8\n"
|
|
|
|
|
" ~1 8601 pts/1 7 -10 0.4 0:00.03 916 0 R color -b -z~7\n"
|
|
|
|
|
" 11005 ~8? ~7 9 0 0.0 0:02.50 2852 1008 S amor -sessi~8\n"
|
|
|
|
|
" available toggles: ~1B~2 =disable bold globally (~1%s~2),\n"
|
|
|
|
|
" ~1z~2 =color/mono (~1%s~2), ~1b~2 =tasks \"bold\"/reverse (~1%s~2)\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
"\n"
|
2013-01-16 11:30:00 +05:30
|
|
|
"1) Select a ~1target~2 as an upper case letter, ~1current target~2 is ~1 %c ~4:\n"
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
" S~2 = Summary Data,~1 M~2 = Messages/Prompts,\n"
|
|
|
|
|
" H~2 = Column Heads,~1 T~2 = Task Information\n"
|
2013-01-16 11:30:00 +05:30
|
|
|
"2) Select a ~1color~2 as a number, ~1current color~2 is ~1 %d ~4:\n"
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
" 0~2 = black,~1 1~2 = red, ~1 2~2 = green,~1 3~2 = yellow,\n"
|
|
|
|
|
" 4~2 = blue, ~1 5~2 = magenta,~1 6~2 = cyan, ~1 7~2 = white\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
"\n"
|
2013-01-16 11:30:00 +05:30
|
|
|
"3) Then use these keys when finished:\n"
|
|
|
|
|
" 'q' to abort changes to window '~1%s~2'\n"
|
|
|
|
|
" 'a' or 'w' to commit & change another, <Enter> to commit and end ");
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-12-07 16:11:14 +05:30
|
|
|
Uniq_nlstab[FIELD_header_fmt] = _(""
|
top: redesign Uniq_nlstab/show_special (nls quirks)
Until this patch, top had used some strings with
special escape sequences to produce colors, normal
text, bold text, etc. They took the following form,
explained by an excerpt from program comments:
...
Our special formatting consists of:
"some text <_delimiter_> some more text <_delimiter_>...\n"
Where <_delimiter_> is a single byte in the range of:
\001 through \010 (in decimalizee, 1 - 8)
and is used to select an 'attribute' from a capabilities table
which is then applied to the *preceding* substring.
...
Unfortunately, these nonprinting values revealed
insurmountable inconsistencies in both the front-end
and back-end translation tools.
The xgettext (extraction) program would take those
special escapes, convert them and then output raw
binary values. Thus the .pot file would contain
lots of unprintable stuff making it unreadable.
If the following was added to po/Makevars, most of
those special escapes would be preserved in their
escape notation:
XGETTEXT_OPTIONS = ... --escape
But two escapes were converted from octal notation
and there was no way to prevent it:
\007 --> \a
\010 --> \b
After a pass through the msginit program, most of
the escapes were reconverted to raw binary values
making translation impossible. There was no
"--escape" option for the back-end programs like
there was for xgettext.
But the real killer was the escape \004, also used
in some of top's special strings. This value would
be silently accepted by xgettext, only to produce
the following fatal error in back-end programs like
msginit, msgfmt and msgen:
.pot:2647: context separator <EOT> within string
To quote from one of the references below:
"Would you create a suite of tools that silently
allow what is destined to become a fatal error
to pass unnoticed?"
So the bottom line was: top's special strings, in
use for the past nine years, had to be redesigned.
References:
http://www.freelists.org/post/procps/procpsng-nls-support,11
http://www.freelists.org/post/procps/procpsng-nls-support,14
2011-10-20 00:44:37 +05:30
|
|
|
"Fields Management~2 for window ~1%s~6, whose current sort field is ~1%s~2\n"
|
2011-10-12 00:32:59 +05:30
|
|
|
" Navigate with Up/Dn, Right selects for move then <Enter> or Left commits,\n"
|
2013-01-29 11:30:00 +05:30
|
|
|
" 'd' or <Space> toggles display, 's' sets sort. Use 'q' or <Esc> to end!\n");
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-12-07 16:11:14 +05:30
|
|
|
Uniq_nlstab[STATE_line_1_fmt] = _("%s:~3"
|
|
|
|
|
" %3u ~2total,~3 %3u ~2running,~3 %3u ~2sleeping,~3 %3u ~2stopped,~3 %3u ~2zombie~3\n");
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-12-07 16:11:14 +05:30
|
|
|
Uniq_nlstab[STATE_lin2x4_fmt] = _("%%%s~3"
|
|
|
|
|
" %#5.1f ~2user,~3 %#5.1f ~2system,~3 %#5.1f ~2nice,~3 %#5.1f ~2idle~3\n");
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-12-07 16:11:14 +05:30
|
|
|
Uniq_nlstab[STATE_lin2x5_fmt] = _("%%%s~3"
|
|
|
|
|
" %#5.1f ~2user,~3 %#5.1f ~2system,~3 %#5.1f ~2nice,~3 %#5.1f ~2idle,~3 %#5.1f ~2IO-wait~3\n");
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-11-07 04:38:43 +05:30
|
|
|
/* Translation Hint: Only the following abbreviations need be translated
|
|
|
|
|
. us = user, sy = system, ni = nice, id = idle, wa = wait,
|
|
|
|
|
. hi hardware interrupt, si = software interrupt */
|
2011-12-07 16:11:14 +05:30
|
|
|
Uniq_nlstab[STATE_lin2x6_fmt] = _("%%%s~3"
|
|
|
|
|
" %#5.1f ~2us,~3 %#5.1f ~2sy,~3 %#5.1f ~2ni,~3 %#5.1f ~2id,~3 %#5.1f ~2wa,~3 %#5.1f ~2hi,~3 %#5.1f ~2si~3\n");
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-11-07 04:38:43 +05:30
|
|
|
/* Translation Hint: Only the following abbreviations need be translated
|
|
|
|
|
. us = user, sy = system, ni = nice, id = idle, wa = wait,
|
|
|
|
|
. hi hardware interrupt, si = software interrupt, st = steal time */
|
2011-12-07 16:11:14 +05:30
|
|
|
Uniq_nlstab[STATE_lin2x7_fmt] = _("%%%s~3"
|
|
|
|
|
"%#5.1f ~2us,~3%#5.1f ~2sy,~3%#5.1f ~2ni,~3%#5.1f ~2id,~3%#5.1f ~2wa,~3%#5.1f ~2hi,~3%#5.1f ~2si,~3%#5.1f ~2st~3\n");
|
2011-10-12 00:32:59 +05:30
|
|
|
|
2011-11-07 04:38:43 +05:30
|
|
|
/* Translation Hint: Only the following need be translated
|
|
|
|
|
. abbreviations: Mem = physical memory/ram, Swap = the linux swap file
|
|
|
|
|
. words: total, used, free, buffers, cached */
|
2011-12-07 16:11:14 +05:30
|
|
|
Uniq_nlstab[MEMORY_lines_fmt] = _(""
|
2012-12-14 11:30:00 +05:30
|
|
|
"%s Mem: ~3 %9.9s~2total,~3 %9.9s~2used,~3 %9.9s~2free,~3 %9.9s~2buffers~3\n"
|
2013-08-09 10:30:00 +05:30
|
|
|
"%s Swap:~3 %9.9s~2total,~3 %9.9s~2used,~3 %9.9s~2free.~3 %9.9s~2cached Mem~3\n");
|
top: add a flexible 'Inspect' capability
This commit introduces an extremely powerful, flexible
brand new capability. Now, users can pause the normal
iterative display and inspect the contents of any file
or output from any script, command, or even pipelines.
It's invoked via the 'Y' interactive command which, in
turn, is supported with simple user supplied additions
as new entries in the top personal configuration file.
A separate new 'Inspect' window supports scrolling and
searching, similar to the main top display. Except it
extends existing 'L'/'&' (locate/locate-next) commands
so that an out-of-view match automatically adjusts the
horizontal position bringing such data into view. And
it provides for multiple successive same line matches.
Also, the basic 'more/less' navigation keys are active
in this new 'Inspect' window, to ease user transition.
There are no program changes required when entries are
added to or deleted from the rcfile. And there are no
known limits to the complexity of a script, command or
pipeline, other than the unidirectional nature imposed
by the 'popen' function call which top cannot violate.
Since it's impossible to predict exactly what contents
will be generated, top treats all output as raw binary
data. Any control characters display in '^C' notation
while all other unprintable characters show as '<AB>'.
The biggest problem encountered was with the find/next
capability since that strstr guy was really diminished
given the possibility that numerous 'strings' could be
encountered *within* many of top's raw, binary 'rows'.
Oh, and another problem was in maintaining the perfect
left & right text justification of this commit message
along with all of the commit summaries. Some of those
summaries (like this very one) are of course, slightly
shorter, to make room for the 'man document' addition.
Enjoy!
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-11-25 10:30:05 +05:30
|
|
|
|
|
|
|
|
Uniq_nlstab[INSP_hdrsels_fmt] = _(""
|
2012-12-04 11:30:00 +05:30
|
|
|
"Inspection~2 Pause at: pid ~1%d~6 running ~1%s~6 as user ~1%s~6\n"
|
top: add a flexible 'Inspect' capability
This commit introduces an extremely powerful, flexible
brand new capability. Now, users can pause the normal
iterative display and inspect the contents of any file
or output from any script, command, or even pipelines.
It's invoked via the 'Y' interactive command which, in
turn, is supported with simple user supplied additions
as new entries in the top personal configuration file.
A separate new 'Inspect' window supports scrolling and
searching, similar to the main top display. Except it
extends existing 'L'/'&' (locate/locate-next) commands
so that an out-of-view match automatically adjusts the
horizontal position bringing such data into view. And
it provides for multiple successive same line matches.
Also, the basic 'more/less' navigation keys are active
in this new 'Inspect' window, to ease user transition.
There are no program changes required when entries are
added to or deleted from the rcfile. And there are no
known limits to the complexity of a script, command or
pipeline, other than the unidirectional nature imposed
by the 'popen' function call which top cannot violate.
Since it's impossible to predict exactly what contents
will be generated, top treats all output as raw binary
data. Any control characters display in '^C' notation
while all other unprintable characters show as '<AB>'.
The biggest problem encountered was with the find/next
capability since that strstr guy was really diminished
given the possibility that numerous 'strings' could be
encountered *within* many of top's raw, binary 'rows'.
Oh, and another problem was in maintaining the perfect
left & right text justification of this commit message
along with all of the commit summaries. Some of those
summaries (like this very one) are of course, slightly
shorter, to make room for the 'man document' addition.
Enjoy!
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-11-25 10:30:05 +05:30
|
|
|
"Use~2: left/right then <Enter> to ~1select~5 an option; 'q' or <Esc> to ~1end~5 !\n"
|
|
|
|
|
"Options~2: ~1%s\n");
|
|
|
|
|
|
|
|
|
|
Uniq_nlstab[INSP_hdrview_fmt] = _(""
|
2012-12-04 11:30:00 +05:30
|
|
|
"Inspection~2 View at: ~1%s~3, ~1%s~3, ~1%s~3. Locating: ~1%s~6\n"
|
top: add a flexible 'Inspect' capability
This commit introduces an extremely powerful, flexible
brand new capability. Now, users can pause the normal
iterative display and inspect the contents of any file
or output from any script, command, or even pipelines.
It's invoked via the 'Y' interactive command which, in
turn, is supported with simple user supplied additions
as new entries in the top personal configuration file.
A separate new 'Inspect' window supports scrolling and
searching, similar to the main top display. Except it
extends existing 'L'/'&' (locate/locate-next) commands
so that an out-of-view match automatically adjusts the
horizontal position bringing such data into view. And
it provides for multiple successive same line matches.
Also, the basic 'more/less' navigation keys are active
in this new 'Inspect' window, to ease user transition.
There are no program changes required when entries are
added to or deleted from the rcfile. And there are no
known limits to the complexity of a script, command or
pipeline, other than the unidirectional nature imposed
by the 'popen' function call which top cannot violate.
Since it's impossible to predict exactly what contents
will be generated, top treats all output as raw binary
data. Any control characters display in '^C' notation
while all other unprintable characters show as '<AB>'.
The biggest problem encountered was with the find/next
capability since that strstr guy was really diminished
given the possibility that numerous 'strings' could be
encountered *within* many of top's raw, binary 'rows'.
Oh, and another problem was in maintaining the perfect
left & right text justification of this commit message
along with all of the commit summaries. Some of those
summaries (like this very one) are of course, slightly
shorter, to make room for the 'man document' addition.
Enjoy!
Signed-off-by: Jim Warner <james.warner@comcast.net>
2012-11-25 10:30:05 +05:30
|
|
|
"Use~2: left/right/up/down/etc to ~1navigate~5 the output; 'L'/'&' to ~1locate~5/~1next~5.\n"
|
|
|
|
|
"Or~2: <Enter> to ~1select another~5; 'q' or <Esc> to ~1end~5 !\n");
|
2011-10-12 00:32:59 +05:30
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
2011-11-02 23:00:03 +05:30
|
|
|
* This function must be called very early at startup, before
|
|
|
|
|
* any other function call, and especially before any changes
|
|
|
|
|
* have been made to the terminal if VALIDATE_NLS is defined!
|
|
|
|
|
*
|
|
|
|
|
* The gettext documentation suggests that alone among locale
|
|
|
|
|
* variables LANGUAGE=ll_CC may be abbreviated as LANGUAGE=ll
|
|
|
|
|
* to denote the language's main dialect. Unfortunately this
|
|
|
|
|
* does not appear to be true. One must specify the complete
|
|
|
|
|
* ll_CC. Optionally, a '.UTF-8' or '.uft8' suffix, as shown
|
|
|
|
|
* in the following examples, may also be included:
|
|
|
|
|
* export LANGUAGE=ll_CC # minimal requirement
|
|
|
|
|
* export LANGUAGE=ll_CC.UTF-8 # optional convention
|
|
|
|
|
* export LANGUAGE=ll_CC.utf8 # ok, too
|
|
|
|
|
*
|
|
|
|
|
* Additionally, as suggested in the gettext documentation, a
|
|
|
|
|
* user will also have to export an empty LC_ALL= to actually
|
|
|
|
|
* enable any translations.
|
|
|
|
|
*/
|
2011-11-06 05:04:50 +05:30
|
|
|
void initialize_nls (void) {
|
2011-10-29 07:08:08 +05:30
|
|
|
#ifdef VALIDATE_NLS
|
|
|
|
|
static const char *nls_err ="\t%s_nlstab[%d] == NULL\n";
|
|
|
|
|
int i;
|
|
|
|
|
|
2011-11-02 23:00:03 +05:30
|
|
|
setlocale (LC_ALL, "");
|
|
|
|
|
bindtextdomain(PACKAGE, LOCALEDIR);
|
|
|
|
|
textdomain(PACKAGE);
|
|
|
|
|
|
2012-09-19 12:32:02 +05:30
|
|
|
memset(Head_nlstab, 0, sizeof(Head_nlstab));
|
2011-10-29 07:08:08 +05:30
|
|
|
memset(Desc_nlstab, 0, sizeof(Desc_nlstab));
|
2012-09-19 12:32:02 +05:30
|
|
|
build_two_nlstabs();
|
2014-02-25 11:30:00 +05:30
|
|
|
for (i = 0; i < EU_MAXPFLGS; i++) {
|
2012-09-19 12:32:02 +05:30
|
|
|
if (!Head_nlstab[i]) {
|
|
|
|
|
fprintf(stderr, nls_err, "Head", i);
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
2011-10-29 07:08:08 +05:30
|
|
|
if (!Desc_nlstab[i]) {
|
|
|
|
|
fprintf(stderr, nls_err, "Desc", i);
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
2012-09-19 12:32:02 +05:30
|
|
|
}
|
2011-10-29 07:08:08 +05:30
|
|
|
memset(Norm_nlstab, 0, sizeof(Norm_nlstab));
|
2011-10-12 00:32:59 +05:30
|
|
|
build_norm_nlstab();
|
2011-10-29 07:08:08 +05:30
|
|
|
for (i = 0; i < norm_MAX; i++)
|
|
|
|
|
if (!Norm_nlstab[i]) {
|
|
|
|
|
fprintf(stderr, nls_err, "Norm", i);
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
|
|
|
|
memset(Uniq_nlstab, 0, sizeof(Uniq_nlstab));
|
2011-11-06 05:04:50 +05:30
|
|
|
build_uniq_nlstab();
|
2011-10-29 07:08:08 +05:30
|
|
|
for (i = 0; i < uniq_MAX; i++)
|
|
|
|
|
if (!Uniq_nlstab[i]) {
|
|
|
|
|
fprintf(stderr, nls_err, "Uniq", i);
|
|
|
|
|
exit(1);
|
|
|
|
|
}
|
|
|
|
|
#else
|
2011-11-02 23:00:03 +05:30
|
|
|
setlocale (LC_ALL, "");
|
|
|
|
|
bindtextdomain(PACKAGE, LOCALEDIR);
|
|
|
|
|
textdomain(PACKAGE);
|
|
|
|
|
|
2012-09-19 12:32:02 +05:30
|
|
|
build_two_nlstabs();
|
2011-10-29 07:08:08 +05:30
|
|
|
build_norm_nlstab();
|
2011-11-06 05:04:50 +05:30
|
|
|
build_uniq_nlstab();
|
2011-10-29 07:08:08 +05:30
|
|
|
#endif
|
2011-10-12 00:32:59 +05:30
|
|
|
}
|
