[Peter Belkner]
> finally, I've published a respective ß-version:
> http://pbelkner.de/projects/files/bs1770gain/bs1770gain/0.8.5-beta-2/.
Good to see progress. Did not take the time to look at it yet. :)
Did you end up with two different formats, one XML and one quasi-XML
with invalid XML synta
Hi Petter,
finally, I've published a respective ß-version:
http://pbelkner.de/projects/files/bs1770gain/bs1770gain/0.8.5-beta-2/.
Best regards
Peter
On 22.09.2022 09:42, Petter Reinholdtsen wrote:
[Peter Belkner]
I consider this a dilemma: readable vs. syntactical correct output. For
thos
Hi Petter,
I consider this a dilemma: readable vs. syntactical correct output. For
those who prefer syntactical correct output over readable output I
introduced a variant to option '--xml': '--xml=cdata'. Because this
breaks backward compatibility by introducing CDATA sections to the
output I
[Peter Belkner]
> I consider this a dilemma: readable vs. syntactical correct output. For
> those who prefer syntactical correct output over readable output I
> introduced a variant to option '--xml': '--xml=cdata'. Because this
> breaks backward compatibility by introducing CDATA sections to th
[Etienne Dechamps 2019-10-20]
> Version: 0.6.5-1
>
> Steps to reproduce:
>
> $ sox -n '1 & 2.wav' synth 1 sine 1000
> $ bs1770gain --xml --suppress-progress . | xmllint -
> -:3: parser error : xmlParseEntityRef: no name
>
> ^
>
> Correct escaping wou
Package: bs1770gain
Version: 0.6.5-1
Steps to reproduce:
$ sox -n '1 & 2.wav' synth 1 sine 1000
$ bs1770gain --xml --suppress-progress . | xmllint -
-:3: parser error : xmlParseEntityRef: no name
^
Correct escaping would be "1 & 2.wav".
This is a re
6 matches
Mail list logo
