bashburn-info — BashBurn mailing list

Re: [Bashburn-info] [bashburn] bbmenu: command not found

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

On Sunday, Dec 28th 2008 at 03:31 -0000, quoth Fred Galusik:

=>2008/12/28 Steven W. Orr <st...@sy...>:
=>> Is the package either debian or rpm, or is it something different?
=>It is something different, if you know Crux Linux, it's the same, you
=>will have a tar.gz archive (bashburn#3.0-1.pkg.tar.gz).
=>
=>I have looked for the Arch Linux build, and as you see, it's quite the same :
=>http://repos.archlinux.org/viewvc.cgi/community/multimedia/bashburn/PKGBUILD?revision=1.4&root=community
=>
=>Btw, I don't think that the build is the problem.
=>
=>++ fredg
=>-- 
=>http://fredgnix.tuxfamily.org || http://www.linuxpedia.fr
=>

Excellent. I was in the process of putting an rpm together and I didn't 
want to duplicate your effort. :-)

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

Re: [Bashburn-info] new filemanager

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

On Mon, 13 Oct 2008 23:40:28 +0200
Anders Lindén <and...@gm...> wrote:

> I committed a new version of the file manager that displays files in
> three columns, marked with [d] or  [f] depending on whether they are
> files or directories.  I also added a delete mechanism that works the
> same way as the file linking one. The difference is that the delete
> function is 'locked' to BBBURNDIR. 
> 
> Anyone has a good idea on how to implement a page system? Let's say
> we want to show a maximum of 16 entries per page (Three columns, four
> rows). 
> 
> Anyway, try it out and let me know what you think. 
> 

I have added a small fix - the column count logic was wrong, and every
4th file/dir wasn't being printed to stdout.

Another issue is trying to delete directories.  rm <filename> doesn't
work here, of course.

====
File(s): 12
rm: cannot remove `/home/nick/burn/test': Is a directory
12 -> /home/nick/burn/test deleted.

Files deleted from /home/nick/burn
====

One way is to check if dir is emtpy and use 'rmdir', or the real
dangourous way if it isn't empty is 'rm -[r]f'.

Perhaps it easier to ask used to empty the directory first, as I
wouldn't like to see 'rm -[r]f' in the code.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] new filemanager

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

I committed a new version of the file manager that displays files in three 
columns, marked with [d] or  [f] depending on whether they are files or 
directories.  I also added a delete mechanism that works the same way as the 
file linking one. The difference is that the delete function is 'locked' to 
BBBURNDIR. 

Anyone has a good idea on how to implement a page system? Let's say we want to 
show a maximum of 16 entries per page (Three columns, four rows). 

Anyway, try it out and let me know what you think. 

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

Re: [Bashburn-info] new filemanager

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

On Monday 13 October 2008 16:37:39 Markus Kollmar wrote:
> I think the filemanager is a great idea since it is not easy to explain
> someone
> why he had to give in bash commands to define data - and in other
> bashburn menus not.
> Good work, Anders.
>

Thanks. It was just an idea I wanted to try out. I always felt the linking of 
files, while not difficult didn't really fit into the rest of BashBurn. 

> I suggest to include this in bashburn 3.1 - but we have to improve it to
> make it easy usable:
>
> * color directories in another color as the files

That's an idea. Or maybe some sort of indicator (<Dir>) to show that it's a 
directory and not a file.

> * list files/dirs also horizontal to use display space better

Good idea. 

> * cut list of large data to a "page" and provide a simple page selection

Also a good idea. Maybe show like 25 files/directories by page and the user 
can press 'n' to go to the next page and maybe 'p' to go to the previous.

> * provide also removing of files in the burn-dir in the same usage as
> adding files
> * as a future function we could also provide burn-data saving, which
> allows users to
>   define data once - and store it in a file for future use.
>

Why not.

> One may say the filemanager is not so powerful like the method now to
> define data.
> This may be true for experienced users. But since we also welcome all
> users and give each the ability
> to easy burn cd, we should think of that (we could provide the old data
> definition method in future, too).
>

We could perhaps add a new variable where the user can select to use the old 
way, this file manager or some external one.


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

Re: [Bashburn-info] new filemanager

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

On Monday, Oct 13th 2008 at 10:37 -0000, quoth Markus Kollmar:

=>I think the filemanager is a great idea since it is not easy to explain 
=>someone
=>why he had to give in bash commands to define data - and in other 
=>bashburn menus not.
=>Good work, Anders.
=>
=>I suggest to include this in bashburn 3.1 - but we have to improve it to 
=>make it easy usable:
=>
=>* color directories in another color as the files
=>* list files/dirs also horizontal to use display space better
=>* cut list of large data to a "page" and provide a simple page selection
=>* provide also removing of files in the burn-dir in the same usage as 
=>adding files
=>* as a future function we could also provide burn-data saving, which 
=>allows users to
=>  define data once - and store it in a file for future use.
=>
=>One may say the filemanager is not so powerful like the method now to 
=>define data.
=>This may be true for experienced users. But since we also welcome all 
=>users and give each the ability
=>to easy burn cd, we should think of that (we could provide the old data 
=>definition method in future, too).

I like the idea of the file manager, but there are already so many file 
managers out there that we really don't want to write a new one that might 
prevent the user from selecting one that he already likes (e.g., mc, 
konqueror, etc...)

* The use could have an BBFILEMGR to override the default one that we 
could supply.

* I'm leary of the whole color thing because it currently makes the 
presumption about running with a black background/white foregound. We need 
to implement themes so that people can define things the way they want. 
And if we do it right then users will be able to contribute themes to us 
for distribution.

* The last suggestion about burn-data saving is something I very much 
like. k3b has the same notion, so if you regularly burn the same data over 
an over, you might just select a predefineable project and your burndir 
would automagically populate.

-- 
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] new filemanager

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

I think the filemanager is a great idea since it is not easy to explain 
someone
why he had to give in bash commands to define data - and in other 
bashburn menus not.
Good work, Anders.

I suggest to include this in bashburn 3.1 - but we have to improve it to 
make it easy usable:

* color directories in another color as the files
* list files/dirs also horizontal to use display space better
* cut list of large data to a "page" and provide a simple page selection
* provide also removing of files in the burn-dir in the same usage as 
adding files
* as a future function we could also provide burn-data saving, which 
allows users to
  define data once - and store it in a file for future use.

One may say the filemanager is not so powerful like the method now to 
define data.
This may be true for experienced users. But since we also welcome all 
users and give each the ability
to easy burn cd, we should think of that (we could provide the old data 
definition method in future, too).


Markus

Re: [Bashburn-info] Update on display problem.

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

> 
> 2008/10/11, Nick Warne <ni...@uk...>:
> > On Sat, 11 Oct 2008 15:28:50 +0200
> > Anders Lindén <and...@gm...> wrote:
> >
> >> lör 2008-10-11 klockan 08:06 +0100 skrev Nick Warne:
> >> > On Fri, 10 Oct 2008 21:19:16 -0400 (EDT)
> >> > "Steven W. Orr" <st...@sy...> wrote:
> >> >
> >> > > There are two programs that I'm using to look at the problem.
> >> > >
> >> > > xlsfonts # Used to display the list of all fonts
> >> > > xfd	# to display the characters in a font.
> >> > >
> >> > > I took a look at a large font at random.
> >> > >
> >> > > xfd -fn
> >> > > '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'
> >> > >
> >> > > and it's clear that you can see all of the funny characters.
> >> > >
> >> > > Then I started an xterm using that font.
> >> > >
> >> > > xterm -font
> >> > > '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'
> >> > >
> >> > > Then from that xterm, I run bashburn. I switch from English to
> >> > > Swedish and the problem still persists.
> >> > >
> >> > > So, my question is this: Why do we think that the encoding
> >> > > we're using is even correct in the first place?
> >> > >
> >> > > If someone can show me a program that's written in anything
> >> > > that displays these characters then I can get this solved.
> >> >
> >> > I still think the Sewdish lang files have extraenous control
> >> > chars in it.
> >> >
> >> > Consider this:
> >> >
> >> > echo "Ångra Ändringar"
> >> >
> >> > (Anders: I guess that is an 'Ä' and not a 'Ã' as seen in the
> >> > file?)
> >> >
> >> > Works fine.  So does changing these in Swedish lang file.
> >> >
> >> > Nick
> >>
> >> I noticed that the Swedish configure.lang is not in utf-8 but in
> >> 'Non-ISO extended-ASCII'. Running the config menu now just gives
> >> me a question mark in a circle where the Swedish characters should
> >> be (And settings are still misaligned).
> >> I created a new configure.lang where I just wrote down the menu
> >> text and saved it in utf-8. Then all Swedish characters displayed
> >> correctly (But again, things are still misaligned).
> >>
> >> I'm starting to think maybe it's not worth spending too much time
> >> with this issue. It's not like it breaks anything and we're going
> >> to replace the translation system anyway. Or will this issue still
> >> appear when we gettextifies BashBurn? Thoughts?
> >>
> >>
> >
> > OK, what editor do you use - in fact, what distro do you use?
> >
> > Could it be some mangling on saving the file?
> >
> > I use Nano BTW -> http://www.nano-editor.org/
> >
> On Sun, 12 Oct 2008 00:02:11 +0200
> "Anders Lindén" <and...@gm...> wrote:
>
> I'm using emacs on Gentoo and Ubuntu.

It could be a bash issue - have a read of this:

http://www.divvun.no/doc/tools/utf-8-setup.html

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Update on display problem.

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

I'm using emacs on Gentoo and Ubuntu.

2008/10/11, Nick Warne <ni...@uk...>:
> On Sat, 11 Oct 2008 15:28:50 +0200
> Anders Lindén <and...@gm...> wrote:
>
>> lör 2008-10-11 klockan 08:06 +0100 skrev Nick Warne:
>> > On Fri, 10 Oct 2008 21:19:16 -0400 (EDT)
>> > "Steven W. Orr" <st...@sy...> wrote:
>> >
>> > > There are two programs that I'm using to look at the problem.
>> > >
>> > > xlsfonts # Used to display the list of all fonts
>> > > xfd	# to display the characters in a font.
>> > >
>> > > I took a look at a large font at random.
>> > >
>> > > xfd -fn
>> > > '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'
>> > >
>> > > and it's clear that you can see all of the funny characters.
>> > >
>> > > Then I started an xterm using that font.
>> > >
>> > > xterm -font
>> > > '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'
>> > >
>> > > Then from that xterm, I run bashburn. I switch from English to
>> > > Swedish and the problem still persists.
>> > >
>> > > So, my question is this: Why do we think that the encoding we're
>> > > using is even correct in the first place?
>> > >
>> > > If someone can show me a program that's written in anything that
>> > > displays these characters then I can get this solved.
>> >
>> > I still think the Sewdish lang files have extraenous control chars
>> > in it.
>> >
>> > Consider this:
>> >
>> > echo "Ångra Ändringar"
>> >
>> > (Anders: I guess that is an 'Ä' and not a 'Ã' as seen in the file?)
>> >
>> > Works fine.  So does changing these in Swedish lang file.
>> >
>> > Nick
>>
>> I noticed that the Swedish configure.lang is not in utf-8 but in
>> 'Non-ISO extended-ASCII'. Running the config menu now just gives me a
>> question mark in a circle where the Swedish characters should be (And
>> settings are still misaligned).
>> I created a new configure.lang where I just wrote down the menu text
>> and saved it in utf-8. Then all Swedish characters displayed
>> correctly (But again, things are still misaligned).
>>
>> I'm starting to think maybe it's not worth spending too much time with
>> this issue. It's not like it breaks anything and we're going to
>> replace the translation system anyway. Or will this issue still
>> appear when we gettextifies BashBurn? Thoughts?
>>
>>
>
> OK, what editor do you use - in fact, what distro do you use?
>
> Could it be some mangling on saving the file?
>
> I use Nano BTW -> http://www.nano-editor.org/
>
> Nick
> --
> Free Software Foundation Associate Member 5508
>


-- 
Anders Lindén

http://bashburn.sf.net

Re: [Bashburn-info] Update on display problem.

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

On Sat, 11 Oct 2008 15:28:50 +0200
Anders Lindén <and...@gm...> wrote:

> lör 2008-10-11 klockan 08:06 +0100 skrev Nick Warne:
> > On Fri, 10 Oct 2008 21:19:16 -0400 (EDT)
> > "Steven W. Orr" <st...@sy...> wrote:
> > 
> > > There are two programs that I'm using to look at the problem.
> > > 
> > > xlsfonts # Used to display the list of all fonts
> > > xfd	# to display the characters in a font.
> > > 
> > > I took a look at a large font at random.
> > > 
> > > xfd -fn
> > > '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'
> > > 
> > > and it's clear that you can see all of the funny characters.
> > > 
> > > Then I started an xterm using that font.
> > > 
> > > xterm -font
> > > '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'
> > > 
> > > Then from that xterm, I run bashburn. I switch from English to
> > > Swedish and the problem still persists.
> > > 
> > > So, my question is this: Why do we think that the encoding we're
> > > using is even correct in the first place?
> > > 
> > > If someone can show me a program that's written in anything that
> > > displays these characters then I can get this solved.
> > 
> > I still think the Sewdish lang files have extraenous control chars
> > in it.
> > 
> > Consider this:
> > 
> > echo "Ångra Ändringar"
> > 
> > (Anders: I guess that is an 'Ä' and not a 'Ã' as seen in the file?)
> > 
> > Works fine.  So does changing these in Swedish lang file.
> > 
> > Nick
> 
> I noticed that the Swedish configure.lang is not in utf-8 but in
> 'Non-ISO extended-ASCII'. Running the config menu now just gives me a
> question mark in a circle where the Swedish characters should be (And
> settings are still misaligned).
> I created a new configure.lang where I just wrote down the menu text
> and saved it in utf-8. Then all Swedish characters displayed
> correctly (But again, things are still misaligned). 
> 
> I'm starting to think maybe it's not worth spending too much time with
> this issue. It's not like it breaks anything and we're going to
> replace the translation system anyway. Or will this issue still
> appear when we gettextifies BashBurn? Thoughts?
> 
> 

OK, what editor do you use - in fact, what distro do you use?

Could it be some mangling on saving the file?

I use Nano BTW -> http://www.nano-editor.org/

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Broken website

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

lör 2008-10-11 klockan 08:21 +0100 skrev Nick Warne:
> A few days ago I posted on a DSL site I use about the beta release.
> Somebody there said they couldn't see the site, and another looked at
> it and found why - a lot of the comments in the HTML are not closed
> correctly, i.e. like this:
> 
> <!-- <p class="published">18 days ago</p> --!>
> 
> so some browsers will not show the HTML as it gets rendered as a comment.
> 
> Should be '-->' at the end.
> 
> Nick
> http://bbs.adslguide.org.uk/showthreaded.php?Cat=&Board=linux&Number=3470765&page=0&view=collapsed&sb=5&o=93
> 

Ok, I think I fixed it. Let me know if something still is funky.

-- 

Re: [Bashburn-info] Broken website

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

lör 2008-10-11 klockan 08:21 +0100 skrev Nick Warne:
> A few days ago I posted on a DSL site I use about the beta release.
> Somebody there said they couldn't see the site, and another looked at
> it and found why - a lot of the comments in the HTML are not closed
> correctly, i.e. like this:
> 
> <!-- <p class="published">18 days ago</p> --!>
> 
> so some browsers will not show the HTML as it gets rendered as a comment.
> 
> Should be '-->' at the end.
> 
> Nick
> http://bbs.adslguide.org.uk/showthreaded.php?Cat=&Board=linux&Number=3470765&page=0&view=collapsed&sb=5&o=93
> 

Meh, stupid textpattern. I'll look into it.

-- 

Re: [Bashburn-info] Update on display problem.

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

lör 2008-10-11 klockan 08:06 +0100 skrev Nick Warne:
> On Fri, 10 Oct 2008 21:19:16 -0400 (EDT)
> "Steven W. Orr" <st...@sy...> wrote:
> 
> > There are two programs that I'm using to look at the problem.
> > 
> > xlsfonts # Used to display the list of all fonts
> > xfd	# to display the characters in a font.
> > 
> > I took a look at a large font at random.
> > 
> > xfd -fn
> > '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'
> > 
> > and it's clear that you can see all of the funny characters.
> > 
> > Then I started an xterm using that font.
> > 
> > xterm -font
> > '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'
> > 
> > Then from that xterm, I run bashburn. I switch from English to
> > Swedish and the problem still persists.
> > 
> > So, my question is this: Why do we think that the encoding we're
> > using is even correct in the first place?
> > 
> > If someone can show me a program that's written in anything that
> > displays these characters then I can get this solved.
> 
> I still think the Sewdish lang files have extraenous control chars in
> it.
> 
> Consider this:
> 
> echo "Ångra Ändringar"
> 
> (Anders: I guess that is an 'Ä' and not a 'Ã' as seen in the file?)
> 
> Works fine.  So does changing these in Swedish lang file.
> 
> Nick

I noticed that the Swedish configure.lang is not in utf-8 but in
'Non-ISO extended-ASCII'. Running the config menu now just gives me a
question mark in a circle where the Swedish characters should be (And
settings are still misaligned).
I created a new configure.lang where I just wrote down the menu text and
saved it in utf-8. Then all Swedish characters displayed correctly (But
again, things are still misaligned). 

I'm starting to think maybe it's not worth spending too much time with
this issue. It's not like it breaks anything and we're going to replace
the translation system anyway. Or will this issue still appear when we
gettextifies BashBurn? Thoughts?


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

Re: [Bashburn-info] hint: add a new dir "i18n"

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

On Fri, 10 Oct 2008 19:32:18 +0200
Markus Kollmar <mar...@on...> wrote:

> I have currently added  the new directory "i18n" (which means 
> <i>internationalisatio<n>).
> This is for the future bashburn translation system.
> 
> It has a makefile and some files to test and see how the system could
> work. However it is not perfect and in the very beginning. I added
> it, so that someone can look at it if interested.
> It is still in development so take this as info.
> 
> If you want look how it works, examine the makefile.
> "make help" gives also some hints.
> 
> The file "bashburn_test.sh" may be removed in future. It is only for 
> testing purpose.
> The "gettext..." files are wrapper for the gettext system. I have
> this borrowed from the backup-manager project.
> With this it is possible to get the english text even if gettext is
> not supported in the system.
> 
> However I am not shure, how we exactly would do the translation.
> Should we reuse our ".lang" files?
> Or should we remove them and put all in the source code?
> What would be the cleaner solution?

Good stuff, Markus.  This is a great base to start working on this.

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] Broken website

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

A few days ago I posted on a DSL site I use about the beta release.
Somebody there said they couldn't see the site, and another looked at
it and found why - a lot of the comments in the HTML are not closed
correctly, i.e. like this:

<!-- <p class="published">18 days ago</p> --!>

so some browsers will not show the HTML as it gets rendered as a comment.

Should be '-->' at the end.

Nick
http://bbs.adslguide.org.uk/showthreaded.php?Cat=&Board=linux&Number=3470765&page=0&view=collapsed&sb=5&o=93

-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Update on display problem.

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

On Fri, 10 Oct 2008 21:19:16 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> There are two programs that I'm using to look at the problem.
> 
> xlsfonts # Used to display the list of all fonts
> xfd	# to display the characters in a font.
> 
> I took a look at a large font at random.
> 
> xfd -fn
> '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'
> 
> and it's clear that you can see all of the funny characters.
> 
> Then I started an xterm using that font.
> 
> xterm -font
> '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'
> 
> Then from that xterm, I run bashburn. I switch from English to
> Swedish and the problem still persists.
> 
> So, my question is this: Why do we think that the encoding we're
> using is even correct in the first place?
> 
> If someone can show me a program that's written in anything that
> displays these characters then I can get this solved.

I still think the Sewdish lang files have extraenous control chars in
it.

Consider this:

echo "Ångra Ändringar"

(Anders: I guess that is an 'Ä' and not a 'Ã' as seen in the file?)

Works fine.  So does changing these in Swedish lang file.

Nick
-- 
Free Software Foundation Associate Member 5508

[Bashburn-info] Update on display problem.

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

There are two programs that I'm using to look at the problem.

xlsfonts # Used to display the list of all fonts
xfd	# to display the characters in a font.

I took a look at a large font at random.

xfd -fn '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'

and it's clear that you can see all of the funny characters.

Then I started an xterm using that font.

xterm -font '-adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-9'

Then from that xterm, I run bashburn. I switch from English to Swedish and 
the problem still persists.

So, my question is this: Why do we think that the encoding we're using is 
even correct in the first place?

If someone can show me a program that's written in anything that displays 
these characters then I can get this solved.

-- 
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] hint: add a new dir "i18n"

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

I have currently added  the new directory "i18n" (which means 
<i>internationalisatio<n>).
This is for the future bashburn translation system.

It has a makefile and some files to test and see how the system could work.
However it is not perfect and in the very beginning. I added it, so that 
someone can look at it if interested.
It is still in development so take this as info.

If you want look how it works, examine the makefile.
"make help" gives also some hints.

The file "bashburn_test.sh" may be removed in future. It is only for 
testing purpose.
The "gettext..." files are wrapper for the gettext system. I have this 
borrowed from the backup-manager project.
With this it is possible to get the english text even if gettext is not 
supported in the system.

However I am not shure, how we exactly would do the translation. Should 
we reuse our ".lang" files?
Or should we remove them and put all in the source code?
What would be the cleaner solution?


Markus

Re: [Bashburn-info] Values misaligned in config menus

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

On Fri, 10 Oct 2008 11:24:58 +0100
Nick Warne <ni...@uk...> wrote:

> On Fri, 10 Oct 2008 06:51:43 +0200
> Anders Lindén <and...@gm...> wrote:
> 
> > On Thursday 09 October 2008 03:24:29 Steven W. Orr wrote:
> > > On Wednesday, Oct 8th 2008 at 18:51 -0000, quoth Anders Lind?n:
> > >
> > > =>I've noticed that when I use the Swedish translation, the
> > > current settings =>in the config and advanced menu are not
> > > aligned 
> > evenly. In
> > > English and =>German it all looks right but not in Swedish.
> > > Anyone 
> > have a
> > > clue on why =>this is?
> > >
> > > I'm not sure why, but I see it too. I only see that the last four
> > > menu items are messaed up. The rest is ok.
> > >
> > > If I try this:
> > >
> > > #! /bin/bash
> > > bb_conf_menu_default=$'\205terstll'
> > > printf "%s\n" "$bb_conf_menu_default"
> > >
> > > It prints out something on two lines.
> > >
> > > So for starters, we should not be coding the line up with
> > > embedded 
> > control
> > > characters. We should be using the notation I describe above.
> > >
> > > As for why it displays this way... I suspect it has something to
> > > do wit hwhether the terminal emulator program we're using (each
> > > one of 
> > different)
> > > knows how to handle the characters we try to display. IOW, is the
> > > character that we want to see part of the character set that the 
> > program
> > > knows how to display? This is just a stab because the likelyhood
> > > is 
> > that
> > > Anders is correctly capable of displaying whatver that $'\205'
> > > really 
> > is.
> > 
> > I ran that little test script and the output I get is different. In
> > konsole i get "�terstll" on one line. That is, the "angstrom sign"
> > is replaced with junk.
> > In xterm I get two lines. The first being blank and the second
> > saying "terstll" 
> > 
> 
> This is strange.  In lang/Swedish/configure.lang I see:
> 
> bb_conf_menu_revert='Ã^Ångra ändringar'
> 
> but if I remove the funny chars to:
> 
> Ångra Ãndringar
> 
> which, according to online tramslator means to 'undo changes', then
> the menu works OK.
> 
> BTW, to change the line I have to cut 'n' paste the 'Å' otherwise the
> shell put the funny chars back.
> 
> Also I see the funny '¤' always after the 'Ã', which is wrong, I
> guess.

OK, I uploaded the changes - I wonder if it it svn that mangles the
stuff?

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Values misaligned in config menus

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

On Fri, 10 Oct 2008 06:51:43 +0200
Anders Lindén <and...@gm...> wrote:

> On Thursday 09 October 2008 03:24:29 Steven W. Orr wrote:
> > On Wednesday, Oct 8th 2008 at 18:51 -0000, quoth Anders Lind?n:
> >
> > =>I've noticed that when I use the Swedish translation, the current
> > settings =>in the config and advanced menu are not aligned 
> evenly. In
> > English and =>German it all looks right but not in Swedish. Anyone 
> have a
> > clue on why =>this is?
> >
> > I'm not sure why, but I see it too. I only see that the last four
> > menu items are messaed up. The rest is ok.
> >
> > If I try this:
> >
> > #! /bin/bash
> > bb_conf_menu_default=$'\205terstll'
> > printf "%s\n" "$bb_conf_menu_default"
> >
> > It prints out something on two lines.
> >
> > So for starters, we should not be coding the line up with embedded 
> control
> > characters. We should be using the notation I describe above.
> >
> > As for why it displays this way... I suspect it has something to do
> > wit hwhether the terminal emulator program we're using (each one of 
> different)
> > knows how to handle the characters we try to display. IOW, is the
> > character that we want to see part of the character set that the 
> program
> > knows how to display? This is just a stab because the likelyhood is 
> that
> > Anders is correctly capable of displaying whatver that $'\205'
> > really 
> is.
> 
> I ran that little test script and the output I get is different. In
> konsole i get "�terstll" on one line. That is, the "angstrom sign" is
> replaced with junk.
> In xterm I get two lines. The first being blank and the second saying 
> "terstll" 
> 

This is strange.  In lang/Swedish/configure.lang I see:

bb_conf_menu_revert='Ã^Ångra ändringar'

but if I remove the funny chars to:

Ångra Ãndringar

which, according to online tramslator means to 'undo changes', then the menu works OK.

BTW, to change the line I have to cut 'n' paste the 'Å' otherwise the shell put the funny chars back.

Also I see the funny '¤' always after the 'Ã', which is wrong, I guess.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Values misaligned in config menus

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

On Thursday 09 October 2008 03:24:29 Steven W. Orr wrote:
> On Wednesday, Oct 8th 2008 at 18:51 -0000, quoth Anders Lind?n:
>
> =>I've noticed that when I use the Swedish translation, the current
> settings =>in the config and advanced menu are not aligned 
evenly. In
> English and =>German it all looks right but not in Swedish. Anyone 
have a
> clue on why =>this is?
>
> I'm not sure why, but I see it too. I only see that the last four menu
> items are messaed up. The rest is ok.
>
> If I try this:
>
> #! /bin/bash
> bb_conf_menu_default=$'\205terstll'
> printf "%s\n" "$bb_conf_menu_default"
>
> It prints out something on two lines.
>
> So for starters, we should not be coding the line up with embedded 
control
> characters. We should be using the notation I describe above.
>
> As for why it displays this way... I suspect it has something to do wit
> hwhether the terminal emulator program we're using (each one of 
different)
> knows how to handle the characters we try to display. IOW, is the
> character that we want to see part of the character set that the 
program
> knows how to display? This is just a stab because the likelyhood is 
that
> Anders is correctly capable of displaying whatver that $'\205' really 
is.

I ran that little test script and the output I get is different. In konsole i 
get "�terstll" on one line. That is, the "angstrom sign" is replaced with 
junk.
In xterm I get two lines. The first being blank and the second saying 
"terstll" 

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

Re: [Bashburn-info] Values misaligned in config menus

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

On Thursday, Oct 9th 2008 at 17:15 -0000, quoth Nick Warne:

=>On Thu, 9 Oct 2008 09:52:38 -0400 (EDT)
=>"Steven W. Orr" <st...@sy...> wrote:
=>
=>> On Thursday, Oct 9th 2008 at 02:33 -0000, quoth Nick Warne:
=>> 
=>> =>On Thu, 9 Oct 2008 07:05:09 +0100
=>> =>Nick Warne <ni...@uk...> wrote:
=>> =>
=>> =>> On Wed, 8 Oct 2008 21:24:29 -0400 (EDT)
=>> =>> "Steven W. Orr" <st...@sy...> wrote:
=>> =>> 
=>> =>> > On Wednesday, Oct 8th 2008 at 18:51 -0000, quoth Anders Lind?n:
=>> =>> > 
=>> =>> > =>I've noticed that when I use the Swedish translation, the
=>> current =>> > settings =>in the config and advanced menu are not
=>> aligned evenly. =>> > In English and =>German it all looks right but
=>> not in Swedish. =>> > Anyone have a clue on why =>this is?
=>> =>> > 
=>> =>> > I'm not sure why, but I see it too. I only see that the last
=>> four =>> > menu items are messaed up. The rest is ok.
=>> =>> > 
=>> =>> > If I try this:
=>> =>> > 
=>> =>> > #! /bin/bash
=>> =>> > bb_conf_menu_default=$'\205terstll'
=>> =>> > printf "%s\n" "$bb_conf_menu_default"
=>> =>> > 
=>> =>> > It prints out something on two lines.
=>> =>> > 
=>> =>> > So for starters, we should not be coding the line up with
=>> embedded =>> > control characters. We should be using the notation I
=>> describe =>> > above.
=>> =>> > 
=>> =>> > As for why it displays this way... I suspect it has something
=>> to do =>> > wit hwhether the terminal emulator program we're using
=>> (each one of =>> > different) knows how to handle the characters we
=>> try to display. =>> > IOW, is the character that we want to see part
=>> of the character set =>> > that the program knows how to display?
=>> This is just a stab because =>> > the likelyhood is that Anders is
=>> correctly capable of displaying =>> > whatver that $'\205' really is.
=>> =>> 
=>> =>> Now, I don't see this at all in X using mrxvt terminal.  All are
=>> lined =>> up perfect.  But if I go to virtual terminal Ctrl+Alt+F2
=>> and try it, =>> they are mis-aligned by a space.
=>> =>
=>> =>OK, in xterm I see what you mean.
=>> =>
=>> =>In the Swedish lang configure.lang:
=>> =>
=>> =>bb_conf_menu_default='_____terst____ll'
=>> =>bb_conf_menu_revert='_____ngra ____ndringar'
=>> =>
=>> =>(if you can't see the above try:
=>> =>http://svn.inf.sgsp.edu.pl/filedetails.php?rep=0&path=/bashburn/trunk/lang/Swedish/configure.lang&rev=0&sc=0
=>> =>)
=>> =>
=>> =>appear as:
=>> =>
=>> =>^[[1;31m|-^[[37;40m 20) __^__terst____ll^[[1;31m
=>> =>^[[1;31m|-^[[37;40m 21) __^__ngra ____ndringar^[[1;31m
=>> =>
=>> =>i.e. having ctrl ^ chars in there instead of that funny inverse
=>> question =>mark.
=>> =>
=>> =>Nick
=>> 
=>> 
=>> 
=>> I suspect that it's not the xterm or or mrxvt (not familiar with that 
=>> one). When you start an xterm, you *can* specify the font.
=>> 
=>> e.g.,
=>> 
=>> xterm -font
=>> -adobe-courier-bold-o-normal--14-100-100-100-m-90-iso8859-15
=>> 
=>> I'm guessing that the font that your terminal emulator is using
=>> doesn't have those characters in the font that it's running which are
=>> being mis-displayed.
=>> 
=>> You can get a list of all of the fonts with xlsfonts. We really don't
=>> want to be using a proportional font, so one of the fixed fonts is
=>> probably more appropriate, e.g.,
=>> 
=>
=>Strange though Anders sees this too, with (I guess) a Swedish locale
=>on the machine.
=>
=>Very strange.

Right. But what I'm saying is that it's not a locale problem. It's a font 
problem. Every character that gets displayed is called a glyph. A set of 
glyphs is a font. Not every glyph is represented inside any particular 
font. So, the question for AndErs is: Is the missing character being 
displayed on your terminal emulator correctly by something that is not bb? 
Can you get it to display by using either a shell echo or a printf? Can 
you get it to happen in a C program?

-- 
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] Values misaligned in config menus

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

On Thu, 9 Oct 2008 09:52:38 -0400 (EDT)
"Steven W. Orr" <st...@sy...> wrote:

> On Thursday, Oct 9th 2008 at 02:33 -0000, quoth Nick Warne:
> 
> =>On Thu, 9 Oct 2008 07:05:09 +0100
> =>Nick Warne <ni...@uk...> wrote:
> =>
> =>> On Wed, 8 Oct 2008 21:24:29 -0400 (EDT)
> =>> "Steven W. Orr" <st...@sy...> wrote:
> =>> 
> =>> > On Wednesday, Oct 8th 2008 at 18:51 -0000, quoth Anders Lind?n:
> =>> > 
> =>> > =>I've noticed that when I use the Swedish translation, the
> current =>> > settings =>in the config and advanced menu are not
> aligned evenly. =>> > In English and =>German it all looks right but
> not in Swedish. =>> > Anyone have a clue on why =>this is?
> =>> > 
> =>> > I'm not sure why, but I see it too. I only see that the last
> four =>> > menu items are messaed up. The rest is ok.
> =>> > 
> =>> > If I try this:
> =>> > 
> =>> > #! /bin/bash
> =>> > bb_conf_menu_default=$'\205terstll'
> =>> > printf "%s\n" "$bb_conf_menu_default"
> =>> > 
> =>> > It prints out something on two lines.
> =>> > 
> =>> > So for starters, we should not be coding the line up with
> embedded =>> > control characters. We should be using the notation I
> describe =>> > above.
> =>> > 
> =>> > As for why it displays this way... I suspect it has something
> to do =>> > wit hwhether the terminal emulator program we're using
> (each one of =>> > different) knows how to handle the characters we
> try to display. =>> > IOW, is the character that we want to see part
> of the character set =>> > that the program knows how to display?
> This is just a stab because =>> > the likelyhood is that Anders is
> correctly capable of displaying =>> > whatver that $'\205' really is.
> =>> 
> =>> Now, I don't see this at all in X using mrxvt terminal.  All are
> lined =>> up perfect.  But if I go to virtual terminal Ctrl+Alt+F2
> and try it, =>> they are mis-aligned by a space.
> =>
> =>OK, in xterm I see what you mean.
> =>
> =>In the Swedish lang configure.lang:
> =>
> =>bb_conf_menu_default='_____terst____ll'
> =>bb_conf_menu_revert='_____ngra ____ndringar'
> =>
> =>(if you can't see the above try:
> =>http://svn.inf.sgsp.edu.pl/filedetails.php?rep=0&path=/bashburn/trunk/lang/Swedish/configure.lang&rev=0&sc=0
> =>)
> =>
> =>appear as:
> =>
> =>^[[1;31m|-^[[37;40m 20) __^__terst____ll^[[1;31m
> =>^[[1;31m|-^[[37;40m 21) __^__ngra ____ndringar^[[1;31m
> =>
> =>i.e. having ctrl ^ chars in there instead of that funny inverse
> question =>mark.
> =>
> =>Nick
> 
> 
> 
> I suspect that it's not the xterm or or mrxvt (not familiar with that 
> one). When you start an xterm, you *can* specify the font.
> 
> e.g.,
> 
> xterm -font
> -adobe-courier-bold-o-normal--14-100-100-100-m-90-iso8859-15
> 
> I'm guessing that the font that your terminal emulator is using
> doesn't have those characters in the font that it's running which are
> being mis-displayed.
> 
> You can get a list of all of the fonts with xlsfonts. We really don't
> want to be using a proportional font, so one of the fixed fonts is
> probably more appropriate, e.g.,
> 

Strange though Anders sees this too, with (I guess) a Swedish locale
on the machine.

Very strange.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Values misaligned in config menus

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

On Thursday, Oct 9th 2008 at 02:33 -0000, quoth Nick Warne:

=>On Thu, 9 Oct 2008 07:05:09 +0100
=>Nick Warne <ni...@uk...> wrote:
=>
=>> On Wed, 8 Oct 2008 21:24:29 -0400 (EDT)
=>> "Steven W. Orr" <st...@sy...> wrote:
=>> 
=>> > On Wednesday, Oct 8th 2008 at 18:51 -0000, quoth Anders Lind?n:
=>> > 
=>> > =>I've noticed that when I use the Swedish translation, the current
=>> > settings =>in the config and advanced menu are not aligned evenly.
=>> > In English and =>German it all looks right but not in Swedish.
=>> > Anyone have a clue on why =>this is?
=>> > 
=>> > I'm not sure why, but I see it too. I only see that the last four
=>> > menu items are messaed up. The rest is ok.
=>> > 
=>> > If I try this:
=>> > 
=>> > #! /bin/bash
=>> > bb_conf_menu_default=$'\205terstll'
=>> > printf "%s\n" "$bb_conf_menu_default"
=>> > 
=>> > It prints out something on two lines.
=>> > 
=>> > So for starters, we should not be coding the line up with embedded
=>> > control characters. We should be using the notation I describe
=>> > above.
=>> > 
=>> > As for why it displays this way... I suspect it has something to do
=>> > wit hwhether the terminal emulator program we're using (each one of
=>> > different) knows how to handle the characters we try to display.
=>> > IOW, is the character that we want to see part of the character set
=>> > that the program knows how to display? This is just a stab because
=>> > the likelyhood is that Anders is correctly capable of displaying
=>> > whatver that $'\205' really is.
=>> 
=>> Now, I don't see this at all in X using mrxvt terminal.  All are lined
=>> up perfect.  But if I go to virtual terminal Ctrl+Alt+F2 and try it,
=>> they are mis-aligned by a space.
=>
=>OK, in xterm I see what you mean.
=>
=>In the Swedish lang configure.lang:
=>
=>bb_conf_menu_default='_____terst____ll'
=>bb_conf_menu_revert='_____ngra ____ndringar'
=>
=>(if you can't see the above try:
=>http://svn.inf.sgsp.edu.pl/filedetails.php?rep=0&path=/bashburn/trunk/lang/Swedish/configure.lang&rev=0&sc=0
=>)
=>
=>appear as:
=>
=>^[[1;31m|-^[[37;40m 20) __^__terst____ll^[[1;31m
=>^[[1;31m|-^[[37;40m 21) __^__ngra ____ndringar^[[1;31m
=>
=>i.e. having ctrl ^ chars in there instead of that funny inverse question
=>mark.
=>
=>Nick



I suspect that it's not the xterm or or mrxvt (not familiar with that 
one). When you start an xterm, you *can* specify the font.

e.g.,

xterm -font -adobe-courier-bold-o-normal--14-100-100-100-m-90-iso8859-15

I'm guessing that the font that your terminal emulator is using doesn't 
have those characters in the font that it's running which are being 
mis-displayed.

You can get a list of all of the fonts with xlsfonts. We really don't want 
to be using a proportional font, so one of the fixed fonts is probably 
more appropriate, e.g.,

xterm -font -screen-fixed-bold-r-normal--0-0-100-100-c-0-koi8-r



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

Re: [Bashburn-info] Values misaligned in config menus

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

On Thu, 9 Oct 2008 07:33:15 +0100
Nick Warne <ni...@uk...> wrote:

> On Thu, 9 Oct 2008 07:05:09 +0100
> Nick Warne <ni...@uk...> wrote:
> 
> > On Wed, 8 Oct 2008 21:24:29 -0400 (EDT)
> > "Steven W. Orr" <st...@sy...> wrote:
> > 
> > > On Wednesday, Oct 8th 2008 at 18:51 -0000, quoth Anders Lind?n:
> > > 
> > > =>I've noticed that when I use the Swedish translation, the
> > > current settings =>in the config and advanced menu are not
> > > aligned evenly. In English and =>German it all looks right but
> > > not in Swedish. Anyone have a clue on why =>this is?
> > > 
> > > I'm not sure why, but I see it too. I only see that the last four
> > > menu items are messaed up. The rest is ok.
> > > 
> > > If I try this:
> > > 
> > > #! /bin/bash
> > > bb_conf_menu_default=$'\205terstll'
> > > printf "%s\n" "$bb_conf_menu_default"
> > > 
> > > It prints out something on two lines.
> > > 
> > > So for starters, we should not be coding the line up with embedded
> > > control characters. We should be using the notation I describe
> > > above.
> > > 
> > > As for why it displays this way... I suspect it has something to
> > > do wit hwhether the terminal emulator program we're using (each
> > > one of different) knows how to handle the characters we try to
> > > display. IOW, is the character that we want to see part of the
> > > character set that the program knows how to display? This is just
> > > a stab because the likelyhood is that Anders is correctly capable
> > > of displaying whatver that $'\205' really is.
> > 
> > Now, I don't see this at all in X using mrxvt terminal.  All are
> > lined up perfect.  But if I go to virtual terminal Ctrl+Alt+F2 and
> > try it, they are mis-aligned by a space.
> 
> OK, in xterm I see what you mean.
> 
> In the Swedish lang configure.lang:
> 
> bb_conf_menu_default='_____terst____ll'
> bb_conf_menu_revert='_____ngra ____ndringar'
> 
> (if you can't see the above try:
> http://svn.inf.sgsp.edu.pl/filedetails.php?rep=0&path=/bashburn/trunk/lang/Swedish/configure.lang&rev=0&sc=0
> )
> 
> appear as:
> 
> ^[[1;31m|-^[[37;40m 20) __^__terst____ll^[[1;31m
> ^[[1;31m|-^[[37;40m 21) __^__ngra ____ndringar^[[1;31m
> 
> i.e. having ctrl ^ chars in there instead of that funny inverse
> question mark.
> 
> Nick

Also, if I use 'strings' on configure.lang I see it also:

bb_conf_menu_default='Ã
terställ'
bb_conf_menu_revert='Ã
ngra ändringar'

You get a line break at that funny ^ char.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] Values misaligned in config menus

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

On Thu, 9 Oct 2008 07:05:09 +0100
Nick Warne <ni...@uk...> wrote:

> On Wed, 8 Oct 2008 21:24:29 -0400 (EDT)
> "Steven W. Orr" <st...@sy...> wrote:
> 
> > On Wednesday, Oct 8th 2008 at 18:51 -0000, quoth Anders Lind?n:
> > 
> > =>I've noticed that when I use the Swedish translation, the current
> > settings =>in the config and advanced menu are not aligned evenly.
> > In English and =>German it all looks right but not in Swedish.
> > Anyone have a clue on why =>this is?
> > 
> > I'm not sure why, but I see it too. I only see that the last four
> > menu items are messaed up. The rest is ok.
> > 
> > If I try this:
> > 
> > #! /bin/bash
> > bb_conf_menu_default=$'\205terstll'
> > printf "%s\n" "$bb_conf_menu_default"
> > 
> > It prints out something on two lines.
> > 
> > So for starters, we should not be coding the line up with embedded
> > control characters. We should be using the notation I describe
> > above.
> > 
> > As for why it displays this way... I suspect it has something to do
> > wit hwhether the terminal emulator program we're using (each one of
> > different) knows how to handle the characters we try to display.
> > IOW, is the character that we want to see part of the character set
> > that the program knows how to display? This is just a stab because
> > the likelyhood is that Anders is correctly capable of displaying
> > whatver that $'\205' really is.
> 
> Now, I don't see this at all in X using mrxvt terminal.  All are lined
> up perfect.  But if I go to virtual terminal Ctrl+Alt+F2 and try it,
> they are mis-aligned by a space.

OK, in xterm I see what you mean.

In the Swedish lang configure.lang:

bb_conf_menu_default='_____terst____ll'
bb_conf_menu_revert='_____ngra ____ndringar'

(if you can't see the above try:
http://svn.inf.sgsp.edu.pl/filedetails.php?rep=0&path=/bashburn/trunk/lang/Swedish/configure.lang&rev=0&sc=0
)

appear as:

^[[1;31m|-^[[37;40m 20) __^__terst____ll^[[1;31m
^[[1;31m|-^[[37;40m 21) __^__ngra ____ndringar^[[1;31m

i.e. having ctrl ^ chars in there instead of that funny inverse question
mark.

Nick

-- 
Free Software Foundation Associate Member 5508