#kde - Mon 26 Feb 2007 between 12:06 and 12:17

NY Lost Funds



Mirrakoris there a special channel for KDE-PIM apps?
daskreech#kdepim ?
annmaMirrakor: #kontact
JucatoMirrakor: #kontact
DaSkreech: :P
Mirrakor:D
srednamkl1525: if you have the original document, try loading it using different encodings until you find one that is correct
JucatoDaSkreech: they're pushing for the OpenRaster format... but not sure where it stands now, specially in light of XCF2...
srednamkl1525: also confirm that the encoding is actually correct in Tools->Encoding after loading the document.
daskreechxcf had a son?
srednamkl1525: if there are errors, please let me know, or file bug reports or email kwrite-devel@kde.org
JucatoDaSkreech: apparently, yes
daskreechIt's a killer spec?
Jucatodunno
but it's supposed to solve lots of problem with XCF... not sure about the "open standard/format" part
thiagoXCF is Gimp's internal format
it is NOT meant to be loadable by other applications
Jucatoyep
daskreechI wouldn't mind killing psd :(
mkl1525sredna, extended version: the files are stored as iso8559-1 in a subversion repository - checked out to debian etch utf8 file system and then opened in kate. Maybe this mess it up cause if I write my own docs I don't have any encoding problems
RFC_1149I am running Fedora Core 6 with KDE 3.5.6, and kernel 2.6.19-1.2911.fc6. Whenever I run a 3D app, for example glxgears, the process pegs the cpu at 100% as shown by top. This occurs even if I login to a failsafe terminal. I am using a gefore fx 5700 with the latest nvidia drivers. This problem occurs with all recent nvidia drivers. I have tried both the livna drivers and the *sh files from nvidia.com. Bery
l and other 3D apps are pretty unusable because of this. For more information, please visit http://redqueen.serveftp.com/pub/problem/ where you will find relevant configuration files, lsmod, lspci etc. I have been trying unsucessfully to resolve this problem via google and IRC. The beryl devs narrowed it down to being all 3D apps, including glxgears. Does anyone else have this issue, or any ideas of what c
ould cause it? Thanks.
srednamkl1525: if the files doesn't show the correct characters if you open them as iso8859-1, the encoding is changed somewhere in the chain. in that case, you could try opening them as utf8 and see if that works. then you must explicitly save them as iso8859-1 to convert them back
RFC_1149: that is hardly a KDE issue ;)
RFC_1149sredna, I suppose not, since the failsafe term has this problem - but I have found help in the most unusal places before
Jucatosredna: I shed a tear tonight for kate... even though I know that it will live on in some better place (kdesdk)... and part of it will continue to exist (kwrite)...
:(
apokryphoshm, is kedit out now too? Haven't checked.
daskreechkate is dead?
apokryphosif so I presume the from-right-to-left text is available in kwrite now?
DaSkreech: no, it's just moved to kdesdk in kde4
JucatoDaSkreech: not dead
daskreechso not shipped by default?
Jucatoapokryphos: kedit has been out for some time now, afaik
DaSkreech: katepart is still in kdelibs
apokryphosDaSkreech: the part is (in libs), but the app isn't in base anymore, yeah.
Jucatobut kwrite will be the default text editor
apokryphosJucato: I see. I wonder if that has been implemented yet then, since it was the one reason for keeping kedit around
Jucatomaybe I just got so used to Kate being the default, even when I first used KDE, that I didn't really see it as a sort of power user app...

Page: 4 11 18 25 32 39 46 53 60 67 74 

IrcArchive

NY Lost Funds