Changes

   mv $1.bak $1

   mv $1.bak $1

   

   

   B=`cat $1.po |grep msgid |wc -l`

   B=`cat $1.po |grep msgid |wc -l`

   D=`expr $B - 1`

   D=`expr $B - 1`

   E=`expr $B - $C`

   E=`expr $B - $C`

:I am wondering why we are using perl to replace as we can also use sed and if readability is not an issue we can do the whole CDATA tag conversin at once

:I am wondering why we are using perl to replace as we can also use sed and if readability is not an issue we can do the whole CDATA tag conversin at once

: <pre>sed -e 's/<!\[CDATA\[/STARTCDATA/g' -e 's/\]\]>/ENDCDATA/g' -e 's/\]\]>/ENDCDATA/g' -e 's/\]\]>/ENDCDATA/g' -e 's/\]\]>/ENDCDATA/g' < /path/to/orignal.file > /path/to/conversion.file</pre>

: <pre>sed -e 's/<!\[CDATA\[/STARTCDATA/g' -e 's/\]\]>/ENDCDATA/g' -e 's/\&>/AMP/g' < original.file > conversion.file</pre>

 

: And back

: And back

: <pre>sed -e 's/STARTCDATA/<!\[CDATA\[/g' -e 's/ENDCDATA/\]\]>/g' -e 's/AMP/\&/g' < /path/to/conversion.file > /path/to/new.file</pre>

::yes but there are more conversions, so it was easier to operate on the one file, efficiency isn't a concern

 

: On top off that I would retrieve the numeric value for C like this, which saves you some mathematics

: <pre>C=`cat $1 |grep '<entry>' |wc -l`</pre>

 

====newpomerge====

====newpomerge====