On Mon, 26 Aug 2002 20:10:10 +0200
Michel Arboi <[EMAIL PROTECTED]> wrote:
> Marc Spitzer <[EMAIL PROTECTED]> writes:
>
> > and I belive that it would be better to keep
> > things together by language, you do not want
> > to check 4+ places to se you translated everything.
>
> L=kl # language code
> for I in *.nasl; do
> X=$(basename "$I" .nasl)
> M="$X".msg."$L"
> if [ ! -f "$M ]; then echo "Need to translate $I into Klingon"; fi
or
grep -vl Klingon *.nasl |awk '{print "the following needs Klingon
Trans.: " $0}'
big deal, the real goal of this exercise is not to find the ones that
need to be transited but to make it easy on the translator to do a good
job and to make it simple enough to parse that you do not have to load
a custom parser library and a DTD and have to xmlify the config file.
XML is not fun/easy to work with.
In all honesty I would have no problem with the originally proposed
syntax, the one grouped by language option. That way the nice and
kind and selfless(it this a little too thick?) translator can have all
the key/value pairs in 1 place to read and write out all the new ones
to one other place. This makes it easier to check the work and faster
to write it. And it would be easy to parse. The only thing I would add
to it would be triple quoted strings for text that spans more then 1
line.
Think of it like here doc from shell and remove all leading whitespace
only
lines and translate newlines into ; for feeding the client.
marc
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.
