bna-linuxiran
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [linuxiran] Xfree86 bug, and Behdad Esfahbod


From: Aryan Ameri
Subject: Re: [linuxiran] Xfree86 bug, and Behdad Esfahbod
Date: Tue, 13 Jan 2004 23:45:19 +0200
User-agent: KMail/1.5.3

On Monday 12 January 2004 08:35, Arash Bijanzadeh wrote:
> I am telling this is a KDE bug. It is not happening in gedit under
> X4.3 and it is happening in KDE under X4.2.1;

Umm, sorry I have a debian partition here, with KDE 3.1.4 and X 4.2, and 
this bug is not there.

> I have told this
> several times but you keep saying that it is a  X bug.

Because I keep beleiving that it's a X bug.

> I went through
> 6 chapter of unicode to find the last one out  I took me 48 hours and
> was a real torture!  I am working on a bug before reporting it or
> saying something!

> I dont' care about this kiddy, what is really anoying is that nobody
> moving his finger, All of linuxiran guys keep talking and talking and
> talking! no move no translation no progress!
> Example? You should have one a great deal of translation till now but
> you did nothing! Why? Instead of watching the lord of the ring or
> compiling kernel translating two string of KDE would be more useful
> but less fun I should agree!

Why should I lie? Last year as you know I was free for nearly 6 months, 
so I did a great deal of translation. Right now, I have a completely 
different situation. I don't have internet access in home, I don't have 
access to CVS (that little application of yours isn't able to check out 
the files) and I also can't properly type Farsi in Kbabel. These all 
have contributed to my lack of participation in FarsiKDE.

And most important of all, it's about time. You have a working day-job 
which has enabled you to pay the bills, as well as contribute to open 
source. I don't. I am a student, with a limited financial budget, 
taking 6 courses every semester and trying to get an A in all of them, 
just because I need to get that scholarship. While I love FarsiKDE, It 
should be noted that I feel under no obligation to contribute to 
FarsiKDE. 

Still, I actualy planned on participating more on the translation side 
specially when I am in Iran. I don't have CVS, so I couldn't see how 
many commits and translations were done. But untill this email of 
yours, I had no knowlegde that "There is NO TRANSLATION, NO PROGRESS".


> With the great knowledge of C++ that ArashP have he can fix this bug
> of KDE, but he preefr to write a memory allocation sample! I really
> could not understand it!

How rude of you to think people have an obligation to participate. As a 
friendly note Arash, I advice you to reconsider this behaviour. You 
won't be a good Open Source manager like this.

I think it has been an honour for us to have Arash P here with us. He 
has adviced us on many issues, and instead of insluting hime (although 
I have done that my self in the past) I look forward to learn from his 
experience. I have always found myself lucky to have had the 
opportunity to know this person.

I look at Arash P, like the members of the fellowship look at Gandalf. 
He doesn't get involve in every little subject, but he is a great 
observer, and he sees the big picture, and from time to time, he gives 
you a little hint to set you on the right direction.

Arash Bijanzadeh, my dear fellow friend, Open Source is about volountary 
cooperation. It doesn't work in a hostile environment that you are now 
trying to make.

> Nobody else is working but platoali and he got to give up soon "ye
> dast seda nadare" you know.


I am sorry to hear that he is alone. I thought a couple of enthusiastic 
individuals were involved.

> The bad news is that we missed kate bidi support in KDE3.2 too! There
> was no feedback and interest in it and it could not be merged in the
> head for 3.2   :-(

:-|

Cheer up Pal. 

> On Sunday 11 January 2004 15:09, Aryan Ameri wrote:
> > On Saturday 10 January 2004 11:54, Arash Bijanzadeh wrote:
> > > I am afraid he is right on this one.
> > > So please ignore it, and for gods sake vote http://bugs.kde.org/
> > > show_bug.cgi?id=70986 and make this bug active,
> >
> > Arash,
> >
> > I know that it might not be related to xkb, and frankly I don't
> > know what xfree86 component it is related to. But it is quite
> > common for a bug reporter, not to know what specific component of a
> > product the bug is related to. It is usually the task of Bugzilla
> > maintainer to reassign the bug to the related component, not for a
> > stranger to close it, saying that it is not related to 'foo'
> > component.
> >
> > And while I have voted (20 points) for your bug on KDE, I have to
> > agree with Arash Z in that I think it is a Xfree86 bug. The reason?
> > KDE 3.1 using XFree 4.2 doesn't show this vertical line. It is IMHO
> > a bug introduced in Xfree86 4.3
> >
> > > we are gonna loose
> > > the proper farsi support because of this bug. Don't let'em to
> > > laugh at us!
> >
> > Well, we have lost proper farsi support due to this bug, and I am
> > not exaggerating when I say that this bug is the sole reason that
> > has prohibited me from using KBabel, and translating KDE.
> >
> > And well, they are already laughing at us. Have you looked at
> > Roozbeh P's weblog recently? he makes great fun of us, whenever he
> > finds a spelling error in one of our bug reports.
> >
> > We two groups, haven't had a smooth relationship in the past, but
> > still I assume that we do have some common goals, and while I don't
> > expect them to help us in our problems, I at least expect them not
> > to trow stones in our way.
> >
> > Or maybe that's a wrong assumption.
> >
> > But seriously, Arash, I think we should investigate this bug more
> > thourouly, and determine really wether it is a KDE bug, or a
> > XFree86 one. This bug is really serious.
> >
> > Cheers

-- 
/*  Trademarks, Copyrights, Patents, etc are all loans from the public 
domain. They are not a property ('intellectual' or otherwise.) */
        

Aryan Ameri




reply via email to

[Prev in Thread] Current Thread [Next in Thread]