Re: [Bashburn-info] Blanking type help mismatch
Brought to you by:
bashburn
|
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 |