bashburn-info — BashBurn mailing list

[Bashburn-info] Temp. configure help files

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

On Mon, 1 Sep 2008 13:18:47 +0100
Nick Warne <ni...@uk...> wrote:


> There is still a lot of work to be done with the help text though - I
> don't even know where to start with that!

OK, I had a brainwave.  There is now a configure_temp_help.lang file
that gets used.  These can be removed as/when the real
BBLANG/configure.lang files are updated/fixed.

At least a user of a different language now gets configure help in
English rather than nothing.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Blanking type help mismatch

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

On Mon, 1 Sep 2008 10:58:15 +0100
Nick Warne <ni...@uk...> wrote:


> OK, I see this was introduced for the English lang files only.
> 
> RIGHT, I will fix up at least the menus for the other languages.
> Czech is nearly done.  This will take me a while, but hopefully I
> will get it done and committed today.
> 
> Steve:  Leave off doing your stuff on the lang files for a bit until I
> commit later today.

OK, the files are done and committed - please test the configure menu
in differnet languages, and if you can read the other languages, please
look for any mistakes I made.

The lang/German/configure.lang has yet to be done, but I need a working
bashburn menu to do it, so will fix the German file later when things
are functional again in HEAD.

There is still a lot of work to be done with the help text though - I
don't even know where to start with that!

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Blanking type help mismatch

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

On Mon, 1 Sep 2008 09:12:41 +0100
Nick Warne <ni...@uk...> wrote:


> BTW, I just found out as well that the English lang configure.lang
> file is the only language file that has the options (e.g.):
> 
> bb_conf_ch_blanking
> bb_conf_ch_norm
> 
> et al
> 
> So doesn't the file menus/configure.sh break for other languages?

OK, I see this was introduced for the English lang files only.

RIGHT, I will fix up at least the menus for the other languages.  Czech
is nearly done.  This will take me a while, but hopefully I will get
it done and committed today.

Steve:  Leave off doing your stuff on the lang files for a bit until I
commit later today.

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] Blanking type help mismatch

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

I noticed the help text states that the default blanking type is 'all'
yet the default configuration file created from BashBurn.sh is set to
'fast'.

Anders, I guess this is your area on what it should be?

BTW, I just found out as well that the English lang configure.lang file
is the only language file that has the options (e.g.):

bb_conf_ch_blanking
bb_conf_ch_norm

et al

So doesn't the file menus/configure.sh break for other languages?

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] Latest commit breaks BB

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

I had to revert to an early revision today, as latest commit breaks the
menu (i.e. no menu at all) - and as I am still heavily testing it for
functionality...

Now, I am all for this revamp, but I can't see how leaving the code in
a broken state so BB doesn't work at all helps anybody...

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Question on Language files

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

On Monday, Sep 1st 2008 at 00:34 -0000, quoth Steven W. Orr:

=>On Sunday, Aug 31st 2008 at 17:53 -0000, quoth Nick Warne:
=>
=>=>On Sun, 31 Aug 2008 22:50:09 +0200
=>=>Anders Lind?n <and...@gm...> wrote:
=>=>
=>=>> On Sun, 2008-08-31 at 16:08 -0400, Steven W. Orr wrote:
=>=>> > On Sunday, Aug 31st 2008 at 14:39 -0000, quoth Nick Warne:
=>=>> > 
=>=>
=>=>
=>=>./lang/German/BashBurn.lang:22:bb_text_7="Suche CD Brenner...."
=>=>./lang/Czech/BashBurn.lang:22:bb_text_7="Detekuji CD mechaniku ...."
=>=>./lang/Norwegian/BashBurn.lang:22:bb_text_7="Finn cd-brennar...."
=>=>./lang/Spanish/BashBurn.lang:22:bb_text_7="Detectando grabadora de
=>=>CD ...."
=>=>./lang/English/BashBurn.lang:22:bb_text_7='Detecting CD
=>=>Writer ....'
=>=>./lang/Italian/BashBurn.lang:22:bb_text_7="Sto cercando il
=>=>masterizzatore
=>=>cd ...."
=>=>./lang/Swedish/BashBurn.lang:22:bb_text_7="S??ker efter
=>=>CD-br??nnare ...."
=>=>./lang/Polish/BashBurn.lang:22:bb_text_7="Wykrywanie
=>=>nagrywarki..."
=>=>
=>=>
=>=>It is only the English language files that have single quotes...
=>=>
=>
=>You said it exactly right. I just haven't yet gotten to all of the 
=>language files.

Ok. I conned myself into doin ze German files. Alles is hoffentlich in 
Ordnung bei der Vaterland.

-- 
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] Question on Language files

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

On Sunday, Aug 31st 2008 at 17:53 -0000, quoth Nick Warne:

=>On Sun, 31 Aug 2008 22:50:09 +0200
=>Anders Lind?n <and...@gm...> wrote:
=>
=>> On Sun, 2008-08-31 at 16:08 -0400, Steven W. Orr wrote:
=>> > On Sunday, Aug 31st 2008 at 14:39 -0000, quoth Nick Warne:
=>> > 
=>
=>
=>./lang/German/BashBurn.lang:22:bb_text_7="Suche CD Brenner...."
=>./lang/Czech/BashBurn.lang:22:bb_text_7="Detekuji CD mechaniku ...."
=>./lang/Norwegian/BashBurn.lang:22:bb_text_7="Finn cd-brennar...."
=>./lang/Spanish/BashBurn.lang:22:bb_text_7="Detectando grabadora de
=>CD ...."
=>./lang/English/BashBurn.lang:22:bb_text_7='Detecting CD
=>Writer ....'
=>./lang/Italian/BashBurn.lang:22:bb_text_7="Sto cercando il
=>masterizzatore
=>cd ...."
=>./lang/Swedish/BashBurn.lang:22:bb_text_7="S??ker efter
=>CD-br??nnare ...."
=>./lang/Polish/BashBurn.lang:22:bb_text_7="Wykrywanie
=>nagrywarki..."
=>
=>
=>It is only the English language files that have single quotes...
=>

You said it exactly right. I just haven't yet gotten to all of the 
language files.

Re: [Bashburn-info] Question on Language files

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

On Sunday, Aug 31st 2008 at 16:50 -0000, quoth Anders Lind?n:

=>> Do you hate it? Do you love it?
=>> 
=>
=>Sound great to me. I think we should use this system, and I'll contact
=>Stevens lawyers to settle a licensing fee. :-)

Trust me, you could never afford it. ;-)>

Re: [Bashburn-info] Question on Language files

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

On Sun, 31 Aug 2008 22:50:09 +0200
Anders Lindén <and...@gm...> wrote:

> On Sun, 2008-08-31 at 16:08 -0400, Steven W. Orr wrote:
> > On Sunday, Aug 31st 2008 at 14:39 -0000, quoth Nick Warne:
> > 
> > =>I just noticed a lot of the English Lang files text is wrapped in
> > =>singles quotes '  whereas most other languages use double quotes "
> > =>
> > =>Why is this?  Does it matter?  Should there be a convention
> > anyway if =>either work (as they seem to do)?
> > =>
> > =>I can clean up if desired tomorrow (pub time now ;-) )
> > =>
> > =>Nick
> > 
> > There's nothing wrong with how things are written. using any of the 
> > working quoting systems. I personally use a style that I developed
> > called The Steven Orr System of Minimal Shell Quoting. (patent
> > pending) :-(
> > 
> > Anyhoo, it looks like this:
> > 
> > foo=Hello					# Case 1
> > bar='Woops. I slipped.'				# Cabe B
> > baz="I like to say $foo when I meet peopls."	# Case iii
> > 
> > so what you have here is three distinct situations:
> > 
> > In case 1, the value in question is a s single word. There is no
> > need to quote anything. You are allowed to use both single or
> > double quotes, but but not using anything, the reader of the code
> > immediately sees that there is a value that is composed of just one
> > word.
> > 
> > Case 2 is obviously a multi-word value with no variable expansion.
> > No double quotes needed. Yes, "s are legal, but I can look at a
> > long string and see right away that there is no variable expansion
> > going on.
> > 
> > Case 3 tells me right away that there are variables afoot.
> > 
> > So you asked about a convention? There it is.
> > 
> > Do you hate it? Do you love it?
> > 
> 
> Sound great to me. I think we should use this system, and I'll contact
> Stevens lawyers to settle a licensing fee. :-)
> 

I dunno if I said it right.  The files under bashburn/lang/ ...

e.g.


./lang/German/BashBurn.lang:22:bb_text_7="Suche CD Brenner...."
./lang/Czech/BashBurn.lang:22:bb_text_7="Detekuji CD mechaniku ...."
./lang/Norwegian/BashBurn.lang:22:bb_text_7="Finn cd-brennar...."
./lang/Spanish/BashBurn.lang:22:bb_text_7="Detectando grabadora de
CD ...."
./lang/English/BashBurn.lang:22:bb_text_7='Detecting CD
Writer ....'
./lang/Italian/BashBurn.lang:22:bb_text_7="Sto cercando il
masterizzatore
cd ...."
./lang/Swedish/BashBurn.lang:22:bb_text_7="Söker efter
CD-brännare ...."
./lang/Polish/BashBurn.lang:22:bb_text_7="Wykrywanie
nagrywarki..."


It is only the English language files that have single quotes...

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Question on Language files

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

On Sun, 2008-08-31 at 16:08 -0400, Steven W. Orr wrote:
> On Sunday, Aug 31st 2008 at 14:39 -0000, quoth Nick Warne:
> 
> =>I just noticed a lot of the English Lang files text is wrapped in
> =>singles quotes '  whereas most other languages use double quotes "
> =>
> =>Why is this?  Does it matter?  Should there be a convention anyway if
> =>either work (as they seem to do)?
> =>
> =>I can clean up if desired tomorrow (pub time now ;-) )
> =>
> =>Nick
> 
> There's nothing wrong with how things are written. using any of the 
> working quoting systems. I personally use a style that I developed called 
> The Steven Orr System of Minimal Shell Quoting. (patent pending) :-(
> 
> Anyhoo, it looks like this:
> 
> foo=Hello					# Case 1
> bar='Woops. I slipped.'				# Cabe B
> baz="I like to say $foo when I meet peopls."	# Case iii
> 
> so what you have here is three distinct situations:
> 
> In case 1, the value in question is a s single word. There is no need to 
> quote anything. You are allowed to use both single or double quotes, but 
> but not using anything, the reader of the code immediately sees that there 
> is a value that is composed of just one word.
> 
> Case 2 is obviously a multi-word value with no variable expansion. No 
> double quotes needed. Yes, "s are legal, but I can look at a long string 
> and see right away that there is no variable expansion going on.
> 
> Case 3 tells me right away that there are variables afoot.
> 
> So you asked about a convention? There it is.
> 
> Do you hate it? Do you love it?
> 

Sound great to me. I think we should use this system, and I'll contact
Stevens lawyers to settle a licensing fee. :-)

-- 
Anders Lindén
http://bashburn.sf.net

Re: [Bashburn-info] Question on Language files

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

On Sunday, Aug 31st 2008 at 14:39 -0000, quoth Nick Warne:

=>I just noticed a lot of the English Lang files text is wrapped in
=>singles quotes '  whereas most other languages use double quotes "
=>
=>Why is this?  Does it matter?  Should there be a convention anyway if
=>either work (as they seem to do)?
=>
=>I can clean up if desired tomorrow (pub time now ;-) )
=>
=>Nick

There's nothing wrong with how things are written. using any of the 
working quoting systems. I personally use a style that I developed called 
The Steven Orr System of Minimal Shell Quoting. (patent pending) :-(

Anyhoo, it looks like this:

foo=Hello					# Case 1
bar='Woops. I slipped.'				# Cabe B
baz="I like to say $foo when I meet peopls."	# Case iii

so what you have here is three distinct situations:

In case 1, the value in question is a s single word. There is no need to 
quote anything. You are allowed to use both single or double quotes, but 
but not using anything, the reader of the code immediately sees that there 
is a value that is composed of just one word.

Case 2 is obviously a multi-word value with no variable expansion. No 
double quotes needed. Yes, "s are legal, but I can look at a long string 
and see right away that there is no variable expansion going on.

Case 3 tells me right away that there are variables afoot.

So you asked about a convention? There it is.

Do you hate it? Do you love it?

-- 
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

[Bashburn-info] Question on Language files

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

I just noticed a lot of the English Lang files text is wrapped in
singles quotes '  whereas most other languages use double quotes "

Why is this?  Does it matter?  Should there be a convention anyway if
either work (as they seem to do)?

I can clean up if desired tomorrow (pub time now ;-) )

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Functionality TESTING thread

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

On Sun, 31 Aug 2008 17:02:19 +0100
Nick Warne <ni...@uk...> wrote:

> I think we ought to start a thread reporting successful functionality
> 
> I just fixed a broken data recording - committed.
> 
> So please just reply to this thread as each function is proven to work
> so we have some sort of visible guide.
> 
> 
> Data recording WORKS
> 

Burning ISO works

-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] Functionality TESTING thread

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

I think we ought to start a thread reporting successful functionality

I just fixed a broken data recording - committed.

So please just reply to this thread as each function is proven to work
so we have some sort of visible guide.


Data recording WORKS

-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] func/isofunc.sh peculair goings-on

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

On Sun, 31 Aug 2008 11:18:18 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> =>ls -lsa /home/nick/burn/
> =>total 8
> =>4 drwxr-xr-x  2 nick users 4096 2008-08-31 14:29 ./
> =>4 drwx------ 59 nick users 4096 2008-08-31 14:33 ../
> =>
> =>2) ISO
> =>
> =>2) Create ISO from CD
> =>
> =>An ISO exists in /home/nick/burn. Delete or move it
> =>before attempting to create a new one.
> =>
> =>Nick
> 
> You're reading it backwards. 0 is success. 0 means "Success! Yess
> there's an iso file there." 1 means "Failure! Bad! No is file there!"
> 

I am not reading it anyway - this is what BB tells me when my burndir
is empty.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] func/isofunc.sh peculair goings-on

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

On Sunday, Aug 31st 2008 at 11:10 -0000, quoth Nick Warne:

=>On Sun, 31 Aug 2008 11:02:43 -0400 (EDT)
=>"Steven W. Orr" <st...@sy...> wrote:
=>
=>> On Sunday, Aug 31st 2008 at 10:45 -0000, quoth Nick Warne:
=>> 
=>> =>I am a bit confused here over what this function does.
=>> =>
=>> =>check_for_iso()
=>> =>{
=>> =>    cd ${BBBURNDIR}
=>> =>    (( $(find ${BBBURNDIR} -iname '*.iso' | wc -l) > 0 ))
=>> =>}
=>> 
=>> The exit status of every function is the result of the last command.
=>> The test function returns 0 or 1 so that's what the function returns.
=>> 
=>> The part I don't get is why the cd command is there.
=>
=>Yep, but the function reports I have an *.iso file in my burndir even
=>though it is empty...
=>
=>ls -lsa /home/nick/burn/
=>total 8
=>4 drwxr-xr-x  2 nick users 4096 2008-08-31 14:29 ./
=>4 drwx------ 59 nick users 4096 2008-08-31 14:33 ../
=>
=>2) ISO
=>
=>2) Create ISO from CD
=>
=>An ISO exists in /home/nick/burn. Delete or move it
=>before attempting to create a new one.
=>
=>Nick

You're reading it backwards. 0 is success. 0 means "Success! Yess there's 
an iso file there." 1 means "Failure! Bad! No is file there!"

-- 
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] func/isofunc.sh peculair goings-on

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

On Sun, 31 Aug 2008 11:02:43 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> On Sunday, Aug 31st 2008 at 10:45 -0000, quoth Nick Warne:
> 
> =>I am a bit confused here over what this function does.
> =>
> =>check_for_iso()
> =>{
> =>    cd ${BBBURNDIR}
> =>    (( $(find ${BBBURNDIR} -iname '*.iso' | wc -l) > 0 ))
> =>}
> 
> The exit status of every function is the result of the last command.
> The test function returns 0 or 1 so that's what the function returns.
> 
> The part I don't get is why the cd command is there.

Yep, but the function reports I have an *.iso file in my burndir even
though it is empty...

ls -lsa /home/nick/burn/
total 8
4 drwxr-xr-x  2 nick users 4096 2008-08-31 14:29 ./
4 drwx------ 59 nick users 4096 2008-08-31 14:33 ../

2) ISO

2) Create ISO from CD

An ISO exists in /home/nick/burn. Delete or move it
before attempting to create a new one.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] func/isofunc.sh peculair goings-on

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

On Sunday, Aug 31st 2008 at 10:45 -0000, quoth Nick Warne:

=>I am a bit confused here over what this function does.
=>
=>check_for_iso()
=>{
=>    cd ${BBBURNDIR}
=>    (( $(find ${BBBURNDIR} -iname '*.iso' | wc -l) > 0 ))
=>}

The exit status of every function is the result of the last command.
The test function returns 0 or 1 so that's what the function returns.

The part I don't get is why the cd command is there.

=>
=>The reason being, while tracing a _not_right_error_message, the
=>function from the iso menu 'burn iso from CD' reports I already have an
=>ISO file in my burndir, even though it is empty.
=>
=>The easy fix is to add in the check to see if the burndir is empty
=>first, but I am confused why the above function reports true (i.e.
=>*.iso exists).
=>
=>
=>cd to burn directory
=>find /path/to/burndir -iname....
=>
=>
=>confused?
=>
=>Nick


-- 
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

[Bashburn-info] func/isofunc.sh peculair goings-on

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

I am a bit confused here over what this function does.

check_for_iso()
{
    cd ${BBBURNDIR}
    (( $(find ${BBBURNDIR} -iname '*.iso' | wc -l) > 0 ))
}

?

The reason being, while tracing a _not_right_error_message, the
function from the iso menu 'burn iso from CD' reports I already have an
ISO file in my burndir, even though it is empty.

The easy fix is to add in the check to see if the burndir is empty
first, but I am confused why the above function reports true (i.e.
*.iso exists).


cd to burn directory
find /path/to/burndir -iname....


confused?

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Pressing any key in menu balks

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

On Sunday, Aug 31st 2008 at 06:26 -0000, quoth Anders Lind?n:

=>Nice work guys. It seems to work perfectly.

You expected less? ;-)

It only took about twenty tries.

=>
=>On Sun, Aug 31, 2008 at 10:12 AM, Nick Warne <ni...@uk...> wrote:
=>> On Sat, 30 Aug 2008 18:55:47 -0400 (EDT)
=>> "Steven W. Orr" <st...@sy...> wrote:
=>>
=>>> =>> I think this time we got it.
=>>> =>
=>>> =>Last commit broke it again.  ~ # @ ...
=>>>
=>>> This time for sure. (Wait, didn't I say that last time?)
=>>>
=>>> Thanks Nick. Break it again! I dare you!
=>>
=>> OK, looks good :-)
=>>
=>> AFAICS the menu now is 100% functional and correct.  I haven't used it
=>> to burn anything yet though.

Re: [Bashburn-info] Config menu issue

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

On Sun, 31 Aug 2008 14:08:40 +0100
Nick Warne <ni...@uk...> wrote:

> Me again :-)
> 
> I just noticed a strange behaviour.
> 
> Go to the config menu, and change something (just a yes/no option is
> suffice). Then apply. Then change it back - apply - change again -
> apply etc.
> 
> The menu changes like this for _all_ the values:
> 
> (no)
> ( yes)
> (  no)
> (    yes)
> (     no)
> (      yes)

Actually, just keep applying changes (22) does it - no need to change
anything.

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] Config menu issue

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

Me again :-)

I just noticed a strange behaviour.

Go to the config menu, and change something (just a yes/no option is
suffice). Then apply. Then change it back - apply - change again - apply
etc.

The menu changes like this for _all_ the values:

(no)
( yes)
(  no)
(    yes)
(     no)
(      yes)

and sure enough .bashburnrc files has the additional spaces too.

I think this is something to do with misc/commands.idx, but having read
that file, I am not too sure I fully understand it, so will not touch
it.

This doesn't appear to happen in the 'advanced config menu', though

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Reworded bb_conf_xit_2 + colour issue

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

On Sun, 31 Aug 2008 10:11:14 +0100
Nick Warne <ni...@uk...> wrote:

> Hi all,

> Also I noticed the the colour $VAR in the lang files do NOT get
> applied (i.e. no colour coded highlights on words).  I guess Steve
> can fix this as per his remarks on revision 405.

OK, I have traced this.

From the file:
menus/configure.sh

the function 'change_option' passes the parameters

to

func/configfunc.sh

Line 55.

The second arg is the help text from the lang files assigned to

typeset prompt

...

echo -e "${BBINFOLINE}\n${prompt}"

prints it, but seems to ignore the embedded {COLOR} options from the
lang. file[s].

Time for a beer...

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Pressing any key in menu balks

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

Nice work guys. It seems to work perfectly.

On Sun, Aug 31, 2008 at 10:12 AM, Nick Warne <ni...@uk...> wrote:
> On Sat, 30 Aug 2008 18:55:47 -0400 (EDT)
> "Steven W. Orr" <st...@sy...> wrote:
>
>> =>> I think this time we got it.
>> =>
>> =>Last commit broke it again.  ~ # @ ...
>>
>> This time for sure. (Wait, didn't I say that last time?)
>>
>> Thanks Nick. Break it again! I dare you!
>
> OK, looks good :-)
>
> AFAICS the menu now is 100% functional and correct.  I haven't used it
> to burn anything yet though.
>
> Nick
> --
> Free Software Foundation Associate Member 5508
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bashburn-info mailing list
> Bas...@li...
> https://lists.sourceforge.net/lists/listinfo/bashburn-info
>



-- 
Anders Lindén

http://bashburn.sf.net

[Bashburn-info] Reworded bb_conf_xit_2 + colour issue

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

Hi all,

lang/English/configure.lang

I have changed the wording slightly in this commit, as it wasn't easy
to understand (or what option to use) before - I guess over language
people could look and revise as necessary.


Also I noticed the the colour $VAR in the lang files do NOT get applied
(i.e. no colour coded highlights on words).  I guess Steve can fix this
as per his remarks on revision 405.

Nick
-- 
Free Software Foundation Associate Member 5508