One of the senior administrators gave me a shell script to modify and it begins as follows:
if ] && ]
{more code follows}
Why the double square brackets? (10 Replies)
Hi
First apologies if this has been raised before.
I've got the following in a ksh script:
if ]
For some reason this does not work. But if I remove the double square brackets to:
if
This works.
I thought ksh supported the ]. Or is there more to it?
Thanks in advance. (3 Replies)
Hi,
I just came across an interesting shell script syntax like the one below:
] && (trap 'rm -rf ${WORK_DIR}/*.$$; echo "\n\nInterrupted !!\n\n"; exit 4' 1 2 3 15)
Can someone please explain the code snippet above?
The trap command bit is fine but ] && is the hazy part.
Generally we use an... (2 Replies)
hi guys,
i'm writing a script that looks for a unquie id in a file and replaces a string between two square brackets on the same line as the unquie id:
.......
.......
0001 zz 43242 replace this text] name
0002 sd 65466 UK] country
.......
.......
how can i find line with id 0001... (6 Replies)
Hi All,
I have a text file which looks like this:
computer programming
systems engineering
I want to get rid of these square brackets and also the text that is inside these brackets. So that my final text file looks like this:
computer programming
systems engineering
I am using... (3 Replies)
Hi frieds, I don't understand the difference between single square bracket and double square brackets in a IF condition.
Ex.
if ;
then
RETURNJOB=1
else
RETURNJOB=0
fi
It run, but this
if ];
then
RETURNJOB=1
else
RETURNJOB=0
fi (4 Replies)
I'm trying to convert this line:
to
\ with sed.
This is what I have so far:
sed -e 's/\]*\)\]/\\\\\/'
but this still gives me .
Any suggestions? (15 Replies)
I wanted to store the number inside the square bracket between colon( : ) and closing suqre bracket(]) in some variable.
Suppose I have lines like :
Input file :
20140320 00:08:23.846 INFO 84] - anything in line
20140320 00:08:23.846 Test 589] - Virtual and lab lab anything... (18 Replies)
Hi All,
Hope you all are doing good. Yesterday in my project i came across a scenario which i can not guess why it was working in one region and why it was not in another region. Please find my issue below.
I am using AIX version 6.0 of UNIX in my project, in shell scripting i have the... (1 Reply)
Discussion started by: mad man
1 Replies
LEARN ABOUT DEBIAN
pocompendium
pocompendium(1) Translate Toolkit 1.3.0 pocompendium(1)NAME
pocompendium - Create a PO compendium from a directory of PO files.
SYNOPSIS
pocompendium [options] output.po <-d po-directory(ies)|po-file(s)>
DESCRIPTION
Takes a directory of translated PO files and creates a single PO files called a PO compendium. This compendium can be used to review word
choice conflicts or as input during a merge using pomigrate(1).
OPTIONS -v, --invert
creates an inverse compendium with msgid and msgstr swapped
-e, --errors
only ouput message bundles that have conflicts
-c, --correct
only ouput message bundles that are correctly translated
-i, --ignore-case
drops all strings to lowercase
-st, -tilde, --strip-accel-amp
remove all & style accelerator markers
-sa, -amp, --strip-accel-tilde
remove all ~ style accelerator markers
-su, --strip-accel-under
remove all _ style accelerator markers
EXAMPLES
Compendium creation
create a compendium with all your translations to use as input during a message merge either when migrating an existing project or starting
a new one.
Conflicting translations
use --errors to find where you have translated an English string differently. Many times this is OK but often it will pick up subtle spell-
ing mistakes or help you to migrate older translations to a newer choice of words.
Conflicting word choice
use --invert and --errors to get a compendium file that show how you have used a translated word for different English words. You might
have chosen a word that is valid for both of the English expressions but that in the context of computers would cause confusion for the
user. You can now easily identify these words and make changes in the underlying translations.
Narrowing Results
PO files treat slight changes in capitalisation, accelerator, punctuation and whitespace as different translations. In cases 2) and 3)
above it is sometimes useful to remove the inconsistencies so that you can focus on the errors in translation not on shifts in capitals. To
this end you can use the following: --ignore-case, --strip-accel-amp, --strip-accel-tilde, --strip-accel-under.
OPERATION
pocompendium makes use of the Gettext tool msgcat(1) to perform its task. It traverses the PO directories and cat's all found PO files into
the single compendium output file. It then uses msgattrib(1) to extract only certain messages, msghack to invert messages and msgfilter(1)
to convert messages to lowercase.
BUGS
There are some absolute/relative path name issues.
Translate Toolkit 1.3.0 pocompendium(1)