Thread: [Bashburn-info] Blanking type help mismatch
Brought to you by:
bashburn
Menu
▾
▴
bashburn-info
|
From: Nick W. <ni...@uk...> - 2008-09-01 08:12:34
|
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 |
|
From: Nick W. <ni...@uk...> - 2008-09-01 09:58:08
|
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 |
|
From: Nick W. <ni...@uk...> - 2008-09-01 12:18:39
|
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 |
|
From: Nick W. <ni...@uk...> - 2008-09-01 13:12:03
|
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 |
|
From: Markus K. <mar...@on...> - 2008-09-01 20:40:53
|
Nick Warne wrote: > 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 > As I wrote already to Steven (who made changes to german translation), it would be VERY NICE - Nick - if you ask me too, before making changes to german translation (since I created and currently maintain german translation). No I have conflicts with my working copy, because I have checked it not in frequently - since I thought the german translation is currently maintained by me und thus no changes will be done. Because of this, I think we should place a info file, where all current "chief-maintainer" of bashburn-parts - or at least the tranlsations - are listed. So one knows where to talk to in the case there are questions and so the whole work is more structured. Or are there any other suggestions? |
|
From: Nick W. <ni...@uk...> - 2008-09-01 23:02:42
|
On Mon, 01 Sep 2008 22:45:40 +0200 Markus Kollmar <mar...@on...> wrote: > No I have conflicts with my working copy, because I have checked it > not in frequently - since I thought the german translation is > currently maintained by me und thus no changes will be done. > > Because of this, I think we should place a info file, where all > current "chief-maintainer" of bashburn-parts - or at least the > tranlsations - are listed. So one knows where to talk to in the case > there are questions and so the whole work is more structured. > > Or are there any other suggestions? > Bloody hell. I guessed something like would happen. Do you have svn commit access? As otherwise the file change[s] move so fast sometimes it is hard to keep up. If you do, then commit often and very often. If you do not, then just use the /land/English/<files> as templates (i.e. your work is not wasted). Please mail me if you need any help here. Nick -- Free Software Foundation Associate Member 5508 |
|
From: Steven W. O. <st...@sy...> - 2008-09-02 01:43:37
|
On Monday, Sep 1st 2008 at 16:45 -0000, quoth Markus Kollmar: =>As I wrote already to Steven (who made changes to german translation), =>it would be VERY NICE - Nick - if you ask me too, before making changes =>to german translation (since I created and currently maintain german =>translation). => =>No I have conflicts with my working copy, because I have checked it not =>in frequently - since I thought the german translation is currently =>maintained by me und thus no changes will be done. => =>Because of this, I think we should place a info file, where all current =>"chief-maintainer" of bashburn-parts - or at least the tranlsations - =>are listed. So one knows where to talk to in the case there are =>questions and so the whole work is more structured. => =>Or are there any other suggestions? I am very happy to leave the language components alone. Markus, you are now officially the owner of the German directory. I'm hoping that if everyone else takes two steps backwatds, you will end up as the owner of the whole lang directory. This doesn't mean you have to be penta-lingual, just that you should take ownership of making all of the files look consistent. Does this work for everyone? =>Steven, yes I personally like your system too - but with one exception =>that I prefer to write "case 1" like: => =>foo='Hello' => =>or: => =>foo="Hello" => =>This may not be better in technically terms. But it keeps a routine to =>quote strings and one can see with one quick look that it is a string. =>(Ok, maybe I have a little touch of lisp programming language, where =>normally strings are quoted, otherwise it is seen as a symbol). This is not a religious war I'm interested in championing. We all understand each other and that must be worth something. I have run into cases in the past where people have said something like foo=Hello but the hello had whitespace after it. The idea is that the convention causes you to say what you want to say, not what you mean. =>Short comment (for people not speaking german) which has nothing =>directly to do with bashburn: =>Vaterland? Steven bist Du urspruenglich aus Deutschland? Oder lebtest Du =>dort eine weile? My family escaped in dubblyoo dubblyoo too. My grandfather on my mother's side is from Gruenewald and my grandmother on my mother's side is from Hanover. I visited a couple of times and I spent a Summer in Stuttgart back in '67. =>Arrrg... Steven I had started particulary updating the german =>translation of the new parts and now I have conflicts with your added =>things. You only have changed the quotes? Oh yes, I don't like conflicts =>in vc-systems (nor in real live). ;-) => I agree about the possibility of stepping on people. I'm new to svn but so far, I'm not all that thrilled. I do need to read more, maybe buy the book etc. But what's really lacking is the ability for people to define their own branches. :-( -- 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 |
|
From: Markus K. <mar...@on...> - 2008-09-02 23:05:35
|
Steven W. Orr wrote: > On Monday, Sep 1st 2008 at 16:45 -0000, quoth Markus Kollmar: > > =>As I wrote already to Steven (who made changes to german translation), > =>it would be VERY NICE - Nick - if you ask me too, before making changes > =>to german translation (since I created and currently maintain german > =>translation). > => > =>No I have conflicts with my working copy, because I have checked it not > =>in frequently - since I thought the german translation is currently > =>maintained by me und thus no changes will be done. > => > =>Because of this, I think we should place a info file, where all current > =>"chief-maintainer" of bashburn-parts - or at least the tranlsations - > =>are listed. So one knows where to talk to in the case there are > =>questions and so the whole work is more structured. > => > =>Or are there any other suggestions? > > I am very happy to leave the language components alone. Markus, you are > now officially the owner of the German directory. I'm hoping that if > everyone else takes two steps backwatds, you will end up as the owner of > the whole lang directory. This doesn't mean you have to be penta-lingual, > just that you should take ownership of making all of the files look > consistent. > Hm - I would manage the language dir's if nobody else want to do this and if all agree. This would - like you said - be work to keep things consistent, and to have a person to talk first if there are any questions about the language side of bashburn. Of course this can only be done TOGETHER with the great native translators. By the way, maybe it is also a good idea if we create analogue to this, persons who coordinates a little bit the user-interface things or the burning technical part of bashburn? > Does this work for everyone? > > =>Steven, yes I personally like your system too - but with one exception > =>that I prefer to write "case 1" like: > => > =>foo='Hello' > => > =>or: > => > =>foo="Hello" > => > =>This may not be better in technically terms. But it keeps a routine to > =>quote strings and one can see with one quick look that it is a string. > =>(Ok, maybe I have a little touch of lisp programming language, where > =>normally strings are quoted, otherwise it is seen as a symbol). > > This is not a religious war I'm interested in championing. We all > understand each other and that must be worth something. > > I have run into cases in the past where people have said something like > foo=Hello > but the hello had whitespace after it. The idea is that the convention > causes you to say what you want to say, not what you mean. > > =>Short comment (for people not speaking german) which has nothing > =>directly to do with bashburn: > =>Vaterland? Steven bist Du urspruenglich aus Deutschland? Oder lebtest Du > =>dort eine weile? > > My family escaped in dubblyoo dubblyoo too. My grandfather on my mother's > side is from Gruenewald and my grandmother on my mother's side is from > Hanover. I visited a couple of times and I spent a Summer in Stuttgart > back in '67. > > Cool Steven. Stuttgart is in Baden Württemberg - where I also live. :-) > =>Arrrg... Steven I had started particulary updating the german > =>translation of the new parts and now I have conflicts with your added > =>things. You only have changed the quotes? Oh yes, I don't like conflicts > =>in vc-systems (nor in real live). ;-) > => > > I agree about the possibility of stepping on people. I'm new to svn but so > far, I'm not all that thrilled. I do need to read more, maybe buy the book > etc. But what's really lacking is the ability for people to define their > own branches. :-( > > Sorry if I can not answer/response every time immediately. (I hope this will partially be better if I have my holiday. :-) ) Markus |
Thanks for helping keep SourceForge clean.
X