[Gtranslator-devel] Re: [Fwd: [Bug 68725] Changed - Crash while editing string in gtranslator]

On Sat, 2002-01-19 at 21:41, Roy-Magne Mo wrote:
On lau , 2002-01-19 at 21:32, Fatih Demir wrote:
> On Sat, 2002-01-19 at 21:25, Roy-Magne Mo wrote:
>     On lau , 2002-01-19 at 21:20, Fatih Demir wrote:
>     > Sometimes the editing component crashes quite silently gtranslator, but
>     > this did only occur once or twice for me and as I couldn't reproduce it,
>     > I didn't look much after it.
>     I've gotten gtranslator to crash by unfuzzying the text and marking it fuzzy
>     right after, might be an gal issue.
> Oh, yes, that could be; I guess this is
> http://bugzilla.gnome.org/show_bug.cgi?id=61884 you're just getting in
> touch with.

Might very well be.
Hehe :-)
> There's also http://bugzilla.gnome.org/show_bug.cgi?id=59418 about a
> relatively close issue -- a common fix could fix all that alltogether --
> but this needs time I'm lacking... (OMG, I didn't take really care about
> b.g.o for about some months and I do see how many trash landed in the
> bug basket.. ohoh ;-)).

hmm... I've never realised the meaning of sticky before now, and I've translated it too!
Yes, and I think, we should slowly move this insane idea of mine into the edit menu and name it "Copy msgid -> msgstr" and forget about the sticky status in the GUI at all. What do you say? I guess, this will also make some people quite happy :-)
>     > Besides this, it's quite interesting to view the author's lines in
>     > gtranslator -- the syntax highlighting has got some special ideas about
>     > some parts of it, but these problems are really minimalistic.
>     > 
>     > What are the exact problems we're trying to care about now?!
>     I guess the crashes with the table is the one that matters right now.
> Yes, I would be absolutely happy about a fix for this and if it would
> really work.... well, it's time for a contribution award in
> gtranslator's source history.. Peeter, you could be also a candidate due
> to your patch.. hehe, no, no beer, there's no gtranslator beer out there
> (yet) ;-) And Gediminas.. .ohoh, we need a brevery :-)

beer for bugs!
Erhm, maybe for patches but not for bugs at themselves, I'm not Ximian nor related to them nor paid by them nor adopted by them or something like that :-)
>     It could be an memory allocation issue. I've tried looking into it -
> .. brave Roy-Magne!

battle scarred, but alive :)
Heha ;-)
> I couldn't find a really good reason why it shouldn't occur at once --
> there's a violent point in gtranslator's (messages table) sources crying
> for resolution...

I'm leaning towards that too
If you could find a solution for that... Eeehh, would be wonderful :-)
>     but the documentation for GAL is rather slim.
> Oh, is there any? News, news :-)

Yes, in the docs directory - but the the parts used in gtranslator isn't documented.
But things are quite similar, so it's semi-documented.
Oh, that's a word. Then it won't be a that big problem for you to solve our problem? Yes? Fine :-)
PS: I added gtranslator-devel too... 
Oh, why not; I don't like this CC'ing orgies, but if you don't mind alltogether, I won't stop the chain :-)
<([ Fatih Demir / kabalak / kabalak gtranslator org ])>
<([ ICQ 64241161 / fdemir2 ix urz uni-heidelberg de ])>
<([ Studying Biology @ the University of Heidelberg ])>

Attachment: signature.asc
Description: This is a digitally signed message part

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