bashburn-info — BashBurn mailing list

Re: [Bashburn-info] Mailing list AWOL

[Steven W. O. <st...@sy...>]

On Tuesday, Oct 7th 2008 at 05:07 -0000, quoth Nick Warne:

=>
=>This list seems to be not working again...
=>
=>Nick
=>-- 
=>Free Software Foundation Associate Member 5508
=>

If you want to crank up bas...@sy... it's available.

-- 
steveo at syslang dot net TMMP1 http://frambors.syslang.net/
Do you have neighbors who are not frambors? Steven W. Orr

Re: [Bashburn-info] 3.0 Beta 1

[Nick W. <ni...@uk...>]

On Tue, 07 Oct 2008 02:10:43 +0200
Markus Kollmar <mar...@on...> wrote:

> By the way - did you removed the link to the svn web-interface on the
> bashburn website? I cna't find it anymore. I think it would be nice
> to have it there, or don' t think so?

It is still there, Markus.  Got to 'downloads' page - at the very
bottom is the link to the web SVN.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] man page

[Steven W. O. <st...@sy...>]

On Monday, Oct 6th 2008 at 17:47 -0000, quoth Anders Lind?n:

=>On Monday 06 October 2008 20:25:13 Steven W. Orr wrote:
=>> Anders, I don't know what that thingy is in your name between the d 
=>and
=>> the r but it makes groff slightly upset. Maybe you should change your 
=>name
=>> ;-)
=>>
=>I'll get right on that, is BashBurn McSwede better? :-)

Lemme see:

name='BashBurn McSwede'
for (( ii=0; ii<${#name}; ii++ ))
do
    [[ $${name:ii:1} =~ '[a-zA-Z ]' ]] || echo "bad letter: $letter"
done

Yup. That's a good one. I'm not too picky (;-)>

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

Re: [Bashburn-info] 3.0 Beta 1

[Steven W. O. <st...@sy...>]

On Monday, Oct 6th 2008 at 18:03 -0000, quoth Anders Lind?n:

=>So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If anyone 
=>feels that's a bad idea let me know, otherwise I'll do it. I'll include the 
=>English, Swedish and German translation because as far as I know those 
=>are the ones updated. 
=>We've tested this thing pretty good so I feel good releasing a beta to 
=>hunt down any hard to find bugs that might still be there.

Sounds delovely :-)


-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

Re: [Bashburn-info] 3.0 Beta 1

[Markus K. <mar...@on...>]

Anders Lindén schrieb:
> So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If anyone 
> feels that's a bad idea let me know, otherwise I'll do it. I'll include the 
> English, Swedish and German translation because as far as I know those 
> are the ones updated. 
> We've tested this thing pretty good so I feel good releasing a beta to 
> hunt down any hard to find bugs that might still be there.
>   

Ok, Anders. Big marking as beta I think would be ok. So we could get 
more people for testing - and since there is a "rule" to release often 
in open source development, this may also a point.

Ahh - Anders you can look to the Swedish translation. I have added the 
variable

bb_main_menu=MAIN

in file "BashBurn.lang" for main-menue header text printing. Translate it to swedish if necessary.



By the way - did you removed the link to the svn web-interface on the bashburn website? I cna't find it anymore.
I think it would be nice to have it there, or don' t think so?

Markus

Re: [Bashburn-info] 3.0 Beta 1

[Markus K. <mar...@on...>]

Anders Lindén schrieb:
> So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If anyone 
> feels that's a bad idea let me know, otherwise I'll do it. I'll include the 
> English, Swedish and German translation because as far as I know those 
> are the ones updated. 
> We've tested this thing pretty good so I feel good releasing a beta to 
> hunt down any hard to find bugs that might still be there.
>   

Ok, Anders. Big marking as beta I think would be ok. So we could get 
more people for testing - and since there is a "rule" to release often 
in open source development, this may also a point.

Ahh - Anders you can look to the Swedish translation. I have added the 
variable

bb_main_menu=MAIN

in file "BashBurn.lang" for main-menue header text printing. Translate it to swedish if necessary.


Markus

Re: [Bashburn-info] 3.0 Beta 1

[Nick W. <ni...@uk...>]

On Tue, 7 Oct 2008 00:03:25 +0200
Anders Lindén <and...@gm...> wrote:

> So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If
> anyone feels that's a bad idea let me know, otherwise I'll do it.
> I'll include the English, Swedish and German translation because as
> far as I know those are the ones updated. 
> We've tested this thing pretty good so I feel good releasing a beta
> to hunt down any hard to find bugs that might still be there.

Agreed.

As far as I am concerned, I have learnt a lot lately on CD/DVD burning,
and BashBurn *just* works and is damn good.

Of course, that is why years ago I found it, as it just done what I
needed without the bollocks GUI apps try to do.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] man page

[Anders L. <and...@gm...>]

On Sunday 05 October 2008 03:53:46 Steven W. Orr wrote:
> I moved bashburn.1.gz to bashburn.1
>
> I also did a bit of hacking in the manpage structure. I'm not great at 
the
> macro usage but I did fix a few things. Let me know if you see any
> problems.

Man page looks sweet. Nice work everyone. Oh, and if you want to be 
added to the contact page on the web page let me know. I didn't want to 
add anyone without consent and be responsible for a crap ton of spam. 

-- 
Anders Lindén
http://bashburn.dose.se

Re: [Bashburn-info] man page

[Anders L. <and...@gm...>]

On Monday 06 October 2008 20:25:13 Steven W. Orr wrote:
> Anders, I don't know what that thingy is in your name between the d 
and
> the r but it makes groff slightly upset. Maybe you should change your 
name
> ;-)
>
I'll get right on that, is BashBurn McSwede better? :-)

[Bashburn-info] 3.0 Beta 1

[Anders L. <and...@gm...>]

So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If anyone 
feels that's a bad idea let me know, otherwise I'll do it. I'll include the 
English, Swedish and German translation because as far as I know those 
are the ones updated. 
We've tested this thing pretty good so I feel good releasing a beta to 
hunt down any hard to find bugs that might still be there.
-- 
Anders Lindén
http://bashburn.dose.se

Re: [Bashburn-info] man page

[Anders L. <and...@gm...>]

On Monday 06 October 2008 21:03:02 Nick Warne wrote:
> On Mon, 6 Oct 2008 14:25:13 -0400 (EDT)
>
> "Steven W. Orr" <st...@sy...> wrote:
> > Anders, I don't know what that thingy is in your name between the 
d
> > and the r but it makes groff slightly upset. Maybe you should 
change
> > your name ;-)
>
> That is an é (I bet Steve can't see that :-D )
>
> Lowercase E with acute (U+00E9)
>
> I guess us Europeans ought to drag you Yanks to the real Internet 
;-)
>
> As an aside, try pronouncing it.  I can after 10 Swedish beers.
>
> Nick

To be honest, Swedish beer sucks. We know how to make safe cars 
but we have a long way to go until we brew a decent beer. 

-- 
Anders Lindén
http://bashburn.dose.se

Re: [Bashburn-info] man page

[Nick W. <ni...@uk...>]

On Mon, 6 Oct 2008 14:25:13 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> You can look at the bashburn.ps with some PostScript viewer like
> evince or gv. It's publication quality.

'gv' That is cool.  Learn something everyday with GNU/Linux.

Great job Steve.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Some language and user-interface things

[Markus K. <mar...@on...>]

Nick Warne schrieb:
> On Mon, 06 Oct 2008 16:56:23 +0200
> Markus Kollmar <mar...@on...> wrote:
>   
>   
>> Ok, sorry was my fault (not entered correct burning drive on my new 
>> slackware system).
>>     
>
> Yes, I did test this with a stupid /dev/cdrom99 entry, and nothing gets
> reported.  I will look at a doing check first to see if the drive is
> valid. Or perhaps the easiest option is to change the INFORMATION text
> to report if you do not see any output, then the valid entry for burner
> is incorrect.
>
> Slackware :-)  Good man :-)
>
> Nick
>   
Hehe Nick. :-)

Yes you are right, I think also it is much work to grep the output of 
the burner-option (since it seems not strongly formated and some part of 
output goes not to stdout I think.)

And the users of bashburn - like you said - are mostly not totally new 
users of a command line tool (since they must - to define burn data with 
bashburn - have a minimal knowledge of standard bash commands like 
'cp',...).

Hm, Nick is also Slackware user...
Good man. :-)

(Maybe we should make a slackware package if we have bashburn 3.0 finished.)

Re: [Bashburn-info] Some language and user-interface things

[Nick W. <ni...@uk...>]

On Mon, 06 Oct 2008 16:56:23 +0200
Markus Kollmar <mar...@on...> wrote:
  
> Ok, sorry was my fault (not entered correct burning drive on my new 
> slackware system).

Yes, I did test this with a stupid /dev/cdrom99 entry, and nothing gets
reported.  I will look at a doing check first to see if the drive is
valid. Or perhaps the easiest option is to change the INFORMATION text
to report if you do not see any output, then the valid entry for burner
is incorrect.

Slackware :-)  Good man :-)

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] man page

[Nick W. <ni...@uk...>]

On Mon, 6 Oct 2008 14:25:13 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> On Monday, Oct 6th 2008 at 04:00 -0000, quoth Nick Warne:
> 
> =>On Sun, 5 Oct 2008 18:20:14 -0400 (EDT)
> =>"Steven W. Orr" <st...@sy...> wrote:
> =>
> =>> On Sunday, Oct 5th 2008 at 12:10 -0000, quoth Nick Warne:
> =>> 
> =>> =>On Sun, 5 Oct 2008 10:49:34 -0400 (EDT)
> =>> =>"Steven W. Orr" <st...@sy...> wrote:
> =>> =>
> =>> =>> On Sunday, Oct 5th 2008 at 05:56 -0000, quoth Nick Warne:
> =>> =>> 
> =>> =>> =>On Sat, 4 Oct 2008 21:53:46 -0400 (EDT)
> =>> =>> =>"Steven W. Orr" <st...@sy...> wrote:
> =>> =>> =>
> =>> =>> =>> I moved bashburn.1.gz to bashburn.1
> =>> =>> =>> 
> =>> =>> =>> I also did a bit of hacking in the manpage structure. I'm
> not =>> =>> great =>> at the macro usage but I did fix a few things.
> Let me =>> know =>> if you see =>> any problems.
> =>> =>> =>
> =>> =>> =>Steve, you should have said.  I have a man page template,
> and =>> the =>> =>bashburn man page gets created from that using sed
> wizardry =>> - that =>> way =>it is easy to change anything.
> =>> =>> =>
> =>> =>> =>http://anaturb.net/create_man_p.htm
> =>> =>> 
> =>> =>> Sorry, I don't understand. Is there a template somewhere?
> =>> =>
> =>> =>Yes, I have a bashburn template directory, so I edit the
> template =>> and =>then create the man page.
> =>> =>
> =>> =>I was wondering where it should go, as it should NOT be in the
> =>> release =>files, so I guess it could live in trunk only just for
> man =>> page edits, =>and just the man page itself gets moved over to
> release. =>> =>
> =>> =>Let me do some documentation and upload it anyway.
> =>> 
> =>> Now I see the problem. The content and shape of the src repository
> =>> has nothing at all to do with the content and shape of the
> released =>> code.
> =>> 
> =>> So.... If you have a script, or a body of software that should be
> =>> executed in order to generate a man page, then the man page itself
> =>> should not be checked into the repository at all. IOW, the file
> =>> bashburn.1 (.gz or otherwise) is not a file that was *written* by
> a =>> person. It's a file that was generated. (If you ever worked in
> the =>> ClearCase world, we would call such things "derived
> objects".) You =>> have some file which right now is sitting in Merry
> Old England and =>> that was used as input to something which
> resulted in bashburn.1 . If =>> you got hit by a bus then we'd be
> sitting on the .1 file, which =>> probably isn't a huge loss (the
> file, not you), but we'd have no way =>> to start from what you
> started from. =>> 
> =>> >From there, look at the Install.sh file after I modified it.
> There's =>> >no 
> =>> reason for the man page to be treated the same as every other
> file. =>> We can write exceptions, lots and lots of them if we want
> to. =>> 
> =>> So what you should do is to check in the real src code and the
> =>> script(s) you run to create the output man page. Make sense?
> =>> 
> =>
> =>OK, I moved the whole lot up - have a look and see what y'all think.
> =>
> =>Steve: I tweaked the man page a little more from what you done.
> 
> I just created a Makefile which when run will create bashburn.1 as
> output. The makefile has a bashburn.1 and a clean as a target. The
> Install.sh will automatically run the makefile to get the most
> uptodate bashburn.1. The file bashburn.man is deleted. There are two
> additional targets in the Makefile: bashburn.man and bashburn.ps
> (Note that they use the -pte options to groff.)
> 
> You can look at the bashburn.ps with some PostScript viewer like
> evince or gv. It's publication quality. The .man file is just plain
> text. There's a lot more to go to make the man page technically
> correct. I'm not *sold* on the idea of the bashburn.sed file as being
> less work to learn than learning
> 
> man 7 groff_man
> 
> but let's go with it for the time being.
> Also, I deleted the .man file and the .1 file from the docs dir since
> they are now files that are made.
> 
> Look good?
> 

Steve,

Great job.  Please also update BUILD_README file to to reflect changes.

This is very good.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] man page

[Nick W. <ni...@uk...>]

On Mon, 6 Oct 2008 14:25:13 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> Anders, I don't know what that thingy is in your name between the d
> and the r but it makes groff slightly upset. Maybe you should change
> your name ;-)

That is an é (I bet Steve can't see that :-D )

Lowercase E with acute (U+00E9)

I guess us Europeans ought to drag you Yanks to the real Internet ;-)

As an aside, try pronouncing it.  I can after 10 Swedish beers.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Some language and user-interface things

[Nick W. <ni...@uk...>]

On Mon, 06 Oct 2008 16:56:23 +0200
Markus Kollmar <mar...@on...> wrote:

> Nick Warne wrote:
> > On Mon, 06 Oct 2008 15:57:45 +0200
> > Markus Kollmar <mar...@on...> wrote:
> >
> >   
> >> Nick Warne wrote:
> >>     
> >>> On Mon, 06 Oct 2008 13:44:19 +0200
> >>> Markus Kollmar <mar...@on...> wrote:
> >>>
> >>>
> >>>   
> >>>       
> >>>> --> 2.  The option
> >>>>
> >>>> bb_conf_ch_dropts=\
> >>>> "This option specifies the driver specific options used
> >>>> when burning a disc. An examples is 
> >>>> ${BBOPTIONCOLOR}burnfree${BBCOLOROFF} for
> >>>> avoiding buffer underruns. You can specify several options by
> >>>> separating them with a comma. This option is non-mandatory and
> >>>> can be skipped. Current setting is:
> >>>> ${BBOPTIONCOLOR}${BBOPT_ONE}${BBCOLOROFF}, and below is a list
> >>>> of possible options. ${bb_conf_cancel_quote}"
> >>>>
> >>>> says that below will occur a list with possible driver options,
> >>>> but there is none? Has it to be hardcoded in lang-files or is
> >>>> there a command we can get this options?
> >>>>     
> >>>>         
> >>> OK, I fixed this up too - cool feature!
> >>>
> >>> Nick
> >>>   
> >>>       
> >> Nick does this print some options on your screen?
> >> I have tested it myself but i got no option list...
> >>
> >>     
> >
> > Yes, works fine here.  Have you svn update again since?
> >
> > Nick
> >   
> Ok, sorry was my fault (not entered correct burning drive on my new 
> slackware system).
> 
> But we got the whole dump of the command - even in my case a warning 
> message, and not just the option list?

Markus,

I think that is how it used to work if I remember correctly.  I did
read the cdrecord man page, but can't see any option to just extract
'options'.

I guess we could do some sort of grep magic on the output, but then as
we don't know what make/model/CD/DVD burners/drives have with all the
possible options returned, it would be an impossible job.

Also, if somebody is nerdy enough to use BashBurn, then I think the
return output will be no problem for the user :-)

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] man page

[Steven W. O. <st...@sy...>]

On Monday, Oct 6th 2008 at 04:00 -0000, quoth Nick Warne:

=>On Sun, 5 Oct 2008 18:20:14 -0400 (EDT)
=>"Steven W. Orr" <st...@sy...> wrote:
=>
=>> On Sunday, Oct 5th 2008 at 12:10 -0000, quoth Nick Warne:
=>> 
=>> =>On Sun, 5 Oct 2008 10:49:34 -0400 (EDT)
=>> =>"Steven W. Orr" <st...@sy...> wrote:
=>> =>
=>> =>> On Sunday, Oct 5th 2008 at 05:56 -0000, quoth Nick Warne:
=>> =>> 
=>> =>> =>On Sat, 4 Oct 2008 21:53:46 -0400 (EDT)
=>> =>> =>"Steven W. Orr" <st...@sy...> wrote:
=>> =>> =>
=>> =>> =>> I moved bashburn.1.gz to bashburn.1
=>> =>> =>> 
=>> =>> =>> I also did a bit of hacking in the manpage structure. I'm not
=>> =>> great =>> at the macro usage but I did fix a few things. Let me
=>> know =>> if you see =>> any problems.
=>> =>> =>
=>> =>> =>Steve, you should have said.  I have a man page template, and
=>> the =>> =>bashburn man page gets created from that using sed wizardry
=>> - that =>> way =>it is easy to change anything.
=>> =>> =>
=>> =>> =>http://anaturb.net/create_man_p.htm
=>> =>> 
=>> =>> Sorry, I don't understand. Is there a template somewhere?
=>> =>
=>> =>Yes, I have a bashburn template directory, so I edit the template
=>> and =>then create the man page.
=>> =>
=>> =>I was wondering where it should go, as it should NOT be in the
=>> release =>files, so I guess it could live in trunk only just for man
=>> page edits, =>and just the man page itself gets moved over to release.
=>> =>
=>> =>Let me do some documentation and upload it anyway.
=>> 
=>> Now I see the problem. The content and shape of the src repository
=>> has nothing at all to do with the content and shape of the released
=>> code.
=>> 
=>> So.... If you have a script, or a body of software that should be
=>> executed in order to generate a man page, then the man page itself
=>> should not be checked into the repository at all. IOW, the file
=>> bashburn.1 (.gz or otherwise) is not a file that was *written* by a
=>> person. It's a file that was generated. (If you ever worked in the
=>> ClearCase world, we would call such things "derived objects".) You
=>> have some file which right now is sitting in Merry Old England and
=>> that was used as input to something which resulted in bashburn.1 . If
=>> you got hit by a bus then we'd be sitting on the .1 file, which
=>> probably isn't a huge loss (the file, not you), but we'd have no way
=>> to start from what you started from.
=>> 
=>> >From there, look at the Install.sh file after I modified it. There's
=>> >no 
=>> reason for the man page to be treated the same as every other file.
=>> We can write exceptions, lots and lots of them if we want to.
=>> 
=>> So what you should do is to check in the real src code and the
=>> script(s) you run to create the output man page. Make sense?
=>> 
=>
=>OK, I moved the whole lot up - have a look and see what y'all think.
=>
=>Steve: I tweaked the man page a little more from what you done.

I just created a Makefile which when run will create bashburn.1 as output. 
The makefile has a bashburn.1 and a clean as a target. The Install.sh will 
automatically run the makefile to get the most uptodate bashburn.1. The 
file bashburn.man is deleted. There are two additional targets in the 
Makefile: bashburn.man and bashburn.ps (Note that they use the -pte 
options to groff.)

You can look at the bashburn.ps with some PostScript viewer like evince or 
gv. It's publication quality. The .man file is just plain text. There's a 
lot more to go to make the man page technically correct. I'm not *sold* on 
the idea of the bashburn.sed file as being less work to learn than 
learning

man 7 groff_man

but let's go with it for the time being.

Anders, I don't know what that thingy is in your name between the d and 
the r but it makes groff slightly upset. Maybe you should change your name 
;-)

Also, I deleted the .man file and the .1 file from the docs dir since they 
are now files that are made.

Look good?

-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

Re: [Bashburn-info] Some language and user-interface things

[Markus K. <mar...@on...>]

Nick Warne wrote:
> On Mon, 06 Oct 2008 15:57:45 +0200
> Markus Kollmar <mar...@on...> wrote:
>
>   
>> Nick Warne wrote:
>>     
>>> On Mon, 06 Oct 2008 13:44:19 +0200
>>> Markus Kollmar <mar...@on...> wrote:
>>>
>>>
>>>   
>>>       
>>>> --> 2.  The option
>>>>
>>>> bb_conf_ch_dropts=\
>>>> "This option specifies the driver specific options used
>>>> when burning a disc. An examples is 
>>>> ${BBOPTIONCOLOR}burnfree${BBCOLOROFF} for
>>>> avoiding buffer underruns. You can specify several options by
>>>> separating them with a comma. This option is non-mandatory and can
>>>> be skipped. Current setting is:
>>>> ${BBOPTIONCOLOR}${BBOPT_ONE}${BBCOLOROFF}, and below is a list
>>>> of possible options. ${bb_conf_cancel_quote}"
>>>>
>>>> says that below will occur a list with possible driver options,
>>>> but there is none? Has it to be hardcoded in lang-files or is
>>>> there a command we can get this options?
>>>>     
>>>>         
>>> OK, I fixed this up too - cool feature!
>>>
>>> Nick
>>>   
>>>       
>> Nick does this print some options on your screen?
>> I have tested it myself but i got no option list...
>>
>>     
>
> Yes, works fine here.  Have you svn update again since?
>
> Nick
>   
Ok, sorry was my fault (not entered correct burning drive on my new 
slackware system).

But we got the whole dump of the command - even in my case a warning 
message, and not just the option list?


Markus

Re: [Bashburn-info] Functionality TESTING thread

[Nick W. <ni...@uk...>]

On Thu, 2 Oct 2008 16:31:49 +0100
Nick Warne <ni...@uk...> wrote:

> On Thu, 2 Oct 2008 16:12:11 +0100
> Nick Warne <ni...@li...> wrote:
> 
> > If at first you don't succeed, try, try again UNTIL the bloody thing
> > does work :-)
> > 
> > Date: Thu, 2 Oct 2008 15:37:51 +0100
> > From: Nick Warne <ni...@li...>
> > To: <and...@gm...>, "Steven W. Orr" <st...@sy...>
> > Subject: Fw: [Bashburn-info] Functionality TESTING thread
> > 
> > 
> > 
> > For some reason my mails to the list randomly do not appear...
> > 
> > Begin forwarded message:
> > 
> > Date: Thu, 2 Oct 2008 15:34:55 +0100
> > From: Nick Warne <ni...@li...>
> > To: bashburn <Bas...@li...>
> > Subject: Re: [Bashburn-info] Functionality TESTING thread
> > 
> > 
> > On Thu, 02 Oct 2008 15:53:01 +0200
> > Anders Lindén <and...@gm...> wrote:
> > 
> > > 
> > > > Keep this tidy!.
> > > >  
> > > >  Data recording WORKS
> > > >  
> > > >  Burning ISO works
> > > >  
> > > >  HD file to CD (data recording) - works
> > > >  
> > > >  Data DVD burning works.
> > > >  
> > > >  *.mp3 to Audio CD works.
> > > >  
> > > >  CD ripping to *.ogg -> hard drive works
> > > >  
> > > >  CD ripping to *.mp3 -> hard drive works
> > > >  
> > > >  CD ripping to *.flac -> hard drive works
> > > >  
> > > >  AudioCD-CD copy works
> > > >  
> > > >  Copy Audio CD [CD to harddrive] -  works
> > > >  
> > > >  Create Mp3s from Wavs - works
> > > >  
> > > >  Create Oggs from Wavs - works
> > > >  
> > > >  Create Flacs from Wavs - works
> > > >  
> > > >  Create ISO from files in <burn directory> - works
> > > >  
> > > >  Data CD to CD (copy)  - works
> > > >  
> > > >  *.ogg to Audio CD - works
> > > > 
> > > >  *.flac to Audio CD - works
> > > > 
> > > >  *.wav to Audio CD - works
> > > 
> > >    Create ISO from CD (And edit mounted ISO) - works
> >  
> > 
> > Setting up two CD drives and configuring - works
> > 
> > Burning Audio CD from CD reader -> CD Burner - works! (how trick is
> > that!!)
> > 
> > Copy Data CD -> Data CD (two drives) - works

DVD iso image [3) Burn DVD image] - works!  (My first DVD :-)) ).



-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Some language and user-interface things

[Nick W. <ni...@uk...>]

On Mon, 06 Oct 2008 13:44:19 +0200
Markus Kollmar <mar...@on...> wrote:


> --> 2.  The option
> 
> bb_conf_ch_dropts=\
> "This option specifies the driver specific options used
> when burning a disc. An examples is 
> ${BBOPTIONCOLOR}burnfree${BBCOLOROFF} for
> avoiding buffer underruns. You can specify several options by
> separating them with a comma. This option is non-mandatory and can be
> skipped. Current setting is:
> ${BBOPTIONCOLOR}${BBOPT_ONE}${BBCOLOROFF}, and below is a list
> of possible options. ${bb_conf_cancel_quote}"
> 
> says that below will occur a list with possible driver options, but 
> there is none? Has it to be hardcoded in lang-files or is there a 
> command we can get this options?

OK, I fixed this up too - cool feature!

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Some language and user-interface things

[Nick W. <ni...@uk...>]

On Mon, 6 Oct 2008 14:05:18 +0100
Nick Warne <ni...@uk...> wrote:

> On Mon, 6 Oct 2008 13:46:33 +0100
> Nick Warne <ni...@uk...> wrote:
> 
> > On Mon, 06 Oct 2008 13:44:19 +0200
> > Markus Kollmar <mar...@on...> wrote:
> > 
> > > --> 3.  in file "configure.sh":
> > > 
> > > ---SNIP
> > > config_default()
> > > {
> > >     pretty_top
> > >     top_info_line
> > >     get_really_sure && return
> > >     configure_changes=( \
> > >             'BBISCONF|0' \
> > >             'BBCDWRITER|<Change me>' \
> > >             'BBCDROM|<Change me>' \
> > >             'BBCDMNT|<Change me>' \
> > >             'BBSPEED|-1' \
> > >             'BBBLANKING|fast' \
> > >             'BBNUMDEV|1' \
> > >             'BBBURNDIR|/tmp/burn' \
> > >             'BBFIFODIR|/tmp' \
> > >             'BBDESCRIPTION|Burnt with BashBurn' \
> > >             'BBAUTHOR|<Change me>' \
> > >             'BBLABEL|BashBurn CD/DVD' \
> > >             'BBNORMALIZE|no' \
> > >             'BBOPT|ONE: ' \
> > >             'BBDELTEMPBURN|no' \
> > >             'BBOVERBURN|no' \
> > >             'BBBITRATE|192' \
> > >             'BBLANG|English' \
> > >             'BBDTAO|-tao' \
> > >             'BBPADDING|-pad' \
> > >             )
> > >     conf_set_aval "${configure_changes[@]}"
> > >     config_revert
> > > #    bb_parse_config
> > > }
> > > 
> > > ----SNIP
> > > 
> > > maybe
> > > "'BBOPT|ONE: ' \"  should become  "'BBOPT_ONE:| ' \"
> > 
> > Dead right - well spotted.  I have fixed this up and committed.
> 
> OK, do a svn update.  BBOPT_ONE doesn't mean a lot, so I have changed
> this to be what it is BBDRIVEROPT.

Oh, forgot.  After pulling this in, start BB, go to configure and just
'apply changes' - this will update your .bashburnrc file with the
renmaed $VAR

Nick


-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Some language and user-interface things

[Nick W. <ni...@uk...>]

On Mon, 6 Oct 2008 13:46:33 +0100
Nick Warne <ni...@uk...> wrote:

> On Mon, 06 Oct 2008 13:44:19 +0200
> Markus Kollmar <mar...@on...> wrote:
> 
> > --> 3.  in file "configure.sh":
> > 
> > ---SNIP
> > config_default()
> > {
> >     pretty_top
> >     top_info_line
> >     get_really_sure && return
> >     configure_changes=( \
> >             'BBISCONF|0' \
> >             'BBCDWRITER|<Change me>' \
> >             'BBCDROM|<Change me>' \
> >             'BBCDMNT|<Change me>' \
> >             'BBSPEED|-1' \
> >             'BBBLANKING|fast' \
> >             'BBNUMDEV|1' \
> >             'BBBURNDIR|/tmp/burn' \
> >             'BBFIFODIR|/tmp' \
> >             'BBDESCRIPTION|Burnt with BashBurn' \
> >             'BBAUTHOR|<Change me>' \
> >             'BBLABEL|BashBurn CD/DVD' \
> >             'BBNORMALIZE|no' \
> >             'BBOPT|ONE: ' \
> >             'BBDELTEMPBURN|no' \
> >             'BBOVERBURN|no' \
> >             'BBBITRATE|192' \
> >             'BBLANG|English' \
> >             'BBDTAO|-tao' \
> >             'BBPADDING|-pad' \
> >             )
> >     conf_set_aval "${configure_changes[@]}"
> >     config_revert
> > #    bb_parse_config
> > }
> > 
> > ----SNIP
> > 
> > maybe
> > "'BBOPT|ONE: ' \"  should become  "'BBOPT_ONE:| ' \"
> 
> Dead right - well spotted.  I have fixed this up and committed.

OK, do a svn update.  BBOPT_ONE doesn't mean a lot, so I have changed
this to be what it is BBDRIVEROPT.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Some language and user-interface things

[Nick W. <ni...@uk...>]

On Mon, 06 Oct 2008 13:44:19 +0200
Markus Kollmar <mar...@on...> wrote:

> --> 3.  in file "configure.sh":
> 
> ---SNIP
> config_default()
> {
>     pretty_top
>     top_info_line
>     get_really_sure && return
>     configure_changes=( \
>             'BBISCONF|0' \
>             'BBCDWRITER|<Change me>' \
>             'BBCDROM|<Change me>' \
>             'BBCDMNT|<Change me>' \
>             'BBSPEED|-1' \
>             'BBBLANKING|fast' \
>             'BBNUMDEV|1' \
>             'BBBURNDIR|/tmp/burn' \
>             'BBFIFODIR|/tmp' \
>             'BBDESCRIPTION|Burnt with BashBurn' \
>             'BBAUTHOR|<Change me>' \
>             'BBLABEL|BashBurn CD/DVD' \
>             'BBNORMALIZE|no' \
>             'BBOPT|ONE: ' \
>             'BBDELTEMPBURN|no' \
>             'BBOVERBURN|no' \
>             'BBBITRATE|192' \
>             'BBLANG|English' \
>             'BBDTAO|-tao' \
>             'BBPADDING|-pad' \
>             )
>     conf_set_aval "${configure_changes[@]}"
>     config_revert
> #    bb_parse_config
> }
> 
> ----SNIP
> 
> maybe
> "'BBOPT|ONE: ' \"  should become  "'BBOPT_ONE:| ' \"

Dead right - well spotted.  I have fixed this up and committed.

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] Some language and user-interface things

[Markus K. <mar...@on...>]

By testing/debugging german translation i found some things (which also 
affect the other languages):

--> 1.  Seems we can remove following variables from language files?:

bb_conf_menu_root="Root Directory"
bb_conf_def_2="(BBROOTDIR has *no* default - you have to change it!)"
bb_conf_ch_root="This options specifies the location of the BashBurn 
scripts.
You should really have no reason to change this value,
only do so if you know what you're doing.
The current setting is: ${BBOPTIONCOLOR}${BBROOTDIR}${BBCOLOROFF}.
${bb_conf_cancel_quote}"


--> 2.  The option

bb_conf_ch_dropts=\
"This option specifies the driver specific options used
when burning a disc. An examples is 
${BBOPTIONCOLOR}burnfree${BBCOLOROFF} for
avoiding buffer underruns. You can specify several options by separating
them with a comma. This option is non-mandatory and can be skipped.
Current setting is: ${BBOPTIONCOLOR}${BBOPT_ONE}${BBCOLOROFF}, and below 
is a list
of possible options. ${bb_conf_cancel_quote}"

says that below will occur a list with possible driver options, but 
there is none? Has it to be hardcoded in lang-files or is there a 
command we can get this options?


--> 3.  in file "configure.sh":

---SNIP
config_default()
{
    pretty_top
    top_info_line
    get_really_sure && return
    configure_changes=( \
            'BBISCONF|0' \
            'BBCDWRITER|<Change me>' \
            'BBCDROM|<Change me>' \
            'BBCDMNT|<Change me>' \
            'BBSPEED|-1' \
            'BBBLANKING|fast' \
            'BBNUMDEV|1' \
            'BBBURNDIR|/tmp/burn' \
            'BBFIFODIR|/tmp' \
            'BBDESCRIPTION|Burnt with BashBurn' \
            'BBAUTHOR|<Change me>' \
            'BBLABEL|BashBurn CD/DVD' \
            'BBNORMALIZE|no' \
            'BBOPT|ONE: ' \
            'BBDELTEMPBURN|no' \
            'BBOVERBURN|no' \
            'BBBITRATE|192' \
            'BBLANG|English' \
            'BBDTAO|-tao' \
            'BBPADDING|-pad' \
            )
    conf_set_aval "${configure_changes[@]}"
    config_revert
#    bb_parse_config
}

----SNIP

maybe
"'BBOPT|ONE: ' \"  should become  "'BBOPT_ONE:| ' \"

or Steven?


Markus