Closed sjpotter closed 1 year ago
That's awfully weird. The text that gets inserted into the NZB is largely hardcoded and there's no namespaces in sight.
Are you using some tool that could be inserting the namespace? I note that --minify
is specified, and you don't get pretty printed output like you show above.
argh. you're right. I had a python tool I wrote to insert passwords and compress. that's what's doing it. sorry. looked at original source and its right.
If it helps, --nzb-compress
can be used for compression (password insertion already done via --nzb-password
), which might remove the need for an external script.
I downloaded the latest release off of github and it appears to be creating invalid nzbs
version:
I run it as
what I end up with is an nzb that looks like
now the
ns0:
prefix isn't invalid xml, but it does seem to cause it to fail in apps (say nzbget) that don't expect it and expect just a plain tag. if I run it through with a simple sed/vi search and replace (%s/ns0://g
) its usable.sabnzbd also doesn't specify using a namespace tag: https://sabnzbd.org/wiki/extra/nzb-spec
also note that the head tag was output twice, once with ns0: once without)
Is it possible to at least have a cmd line option to control this?