Bug 2139 - KDing for mageia1
Summary: KDing for mageia1
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Oliver Burger
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-13 16:18 CEST by Walter Müller
Modified: 2011-07-15 21:23 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Walter Müller 2011-07-13 16:18:41 CEST
Description of problem:


My wish: KDing for mageia1

Thank you
Comment 1 Oliver Burger 2011-07-15 10:23:56 CEST
Although google finds it quite fast, it would be most helpful to post more information. Especially since kding was not in the official Mandriva repos...

I will look into importing it...

Oliver

CC: (none) => oliver.bgr

Comment 2 Walter Müller 2011-07-15 14:20:46 CEST
hello Oliver,

I'm really sorry, I did not know that, becaus I used it in mandriva. 

KDing "a dictionary lookup program" it is for "translation between German and English" but, it "can be used for every language for which a word list is available for Ding"

KDing is a "a KDE port of Ding".

Thank you.
Comment 3 Oliver Burger 2011-07-15 15:19:47 CEST
No prob here. I was a package by mandrivauser.de (and possibly other third party repos).
After I found out, I built it for mud, it was quite easy for me to import it. It should already be in Cauldron and I can try and backport it to Mga 1.

Oliver

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Assignee: bugsquad => oliver.bgr

Comment 4 Walter Müller 2011-07-15 21:23:36 CEST
(In reply to comment #3)
> No prob here. I was a package by mandrivauser.de (and possibly other third
> party repos).
> After I found out, I built it for mud, it was quite easy for me to import it.
> It should already be in Cauldron and I can try and backport it to Mga 1.
> 
> Oliver

I hope, it will be possible.

Thank you
Walter

Note You need to log in before you can comment on or make changes to this bug.