<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
In my system kedit(1) crashes with with signal 11 reciption...with the
following KDE Crash Handler popup<br>
<br>
KCrash: Application 'kedit' crashing....<br>
<br>
This backtrace appears to be useless.<br>
This is probably because your packages are built in a way which
prevents creating of proper backtraces, or the stack frame was
seriously corrupted in the crash.<br>
<br>
(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".<br>
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]<br>
[New Thread -150966144 (LWP 17064)]<br>
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...0x00c9c402 in ?? ()<br>
#0 0x00c9c402 in ?? ()<br>
#1 0x00493e83 in __waitpid_nocancel () from /lib/tls/libpthread.so.0<br>
#2 0x00b04b60 in KCrash::defaultCrashHandler () from
/usr/lib/libkdecore.so.4<br>
#3 <signal handler called><br>
#4 0x0143b23d in Coverage_Index () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#5 0x014498af in Free_LigatureSubst () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#6 0x0144f56e in TT_GSUB_Query_Features ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#7 0x0144f7a2 in TT_GSUB_Query_Features ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#8 0x0144fa58 in TT_GSUB_Apply_Feature ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#9 0x011334ed in QOpenType::applyGSUBFeature ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#10 0x012413dd in q_heuristicPosition () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#11 0x012419d1 in q_heuristicPosition () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#12 0x012490d1 in QTextEngine::shape () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#13 0x01249bf2 in QTextEngine::width () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#14 0x0110b7dd in QFontMetrics::charWidth ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#15 0x012171f7 in QTextFormat::width () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#16 0x01218d51 in QTextString::width () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#17 0x0122211f in QTextFormatterBreakWords::format ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#18 0x0121a42f in QTextParagraph::format ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#19 0x012012b9 in QTextCursor::insert () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#20 0x0131a977 in QTextEdit::insert () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#21 0x0131a827 in QTextEdit::insert () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#22 0x01313ba6 in QTextEdit::keyPressEvent ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#23 0x007bfce8 in KEdit::keyPressEvent () from /usr/lib/libkdeui.so.4<br>
#24 0x011f08e5 in QWidget::event () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#25 0x0131324d in QTextEdit::event () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#26 0x0115e87f in QApplication::internalNotify ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#27 0x0115e374 in QApplication::notify ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#28 0x00a70229 in KApplication::notify () from /usr/lib/libkdecore.so.4<br>
#29 0x010f7080 in QETWidget::translateKeyEvent ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#30 0x010f2df0 in QApplication::x11ProcessEvent ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#31 0x01109ab4 in QEventLoop::processEvents ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#32 0x01170a78 in QEventLoop::enterLoop ()<br>
from /usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#33 0x01170928 in QEventLoop::exec () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#34 0x0115ead1 in QApplication::exec () from
/usr/lib/qt-3.3/lib/libqt-mt.so.3<br>
#35 0x00f3d697 in kdemain () from /usr/lib/libkdeinit_kedit.so<br>
#36 0x080485eb in ?? ()<br>
#37 0x00000002 in ?? ()<br>
#38 0xfeed3f34 in ?? ()<br>
#39 0xfeed3f08 in ?? ()<br>
#40 0x08d92ad4 in __libc_start_main () from /lib/tls/libc.so.6<br>
ه<br>
<br>
Aryan Ameri wrote:
<blockquote cite="mid200409180013.08636.a.ameri@linuxiran.org"
type="cite">
<pre wrap="">On Friday 17 September 2004 20:15, Medi Montaseri wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I'm also noticing that kwrite(1) cursor positioning is not correct.
That is while I'm typing
in Farsi, the cursor is to the far right of the text, but for each
keystrock, the char is inserted
to the far left. Effectively what you get is a left justified
text....
Is this a configuration issue or bug with kwrite(1).
</pre>
</blockquote>
<pre wrap=""><!---->
Yes, Kwrite and Kate I think still have problems with BiDi text. There
was a bug on KDE relating to this, but the KDE guys wanted input from
Persian and Arabic users to fix it for KDE 3.3, and no one gave them
any feedback, so they dropped the issue, and didn't fix it.
Kedit should work flawlessly though. It is ofcourse nothing but a very
simple editor.
Cheers
</pre>
<blockquote type="cite">
<pre wrap="">Aryan Ameri wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Thursday 16 September 2004 19:43, Medi Montaseri wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Thanks Arash jan....
Looks like gedit(1) was the problem, I tried kedit(1) but when I
attempted to switch my keyboard
via "Alt-Shift", kedit(1) seg-faulted.
</pre>
</blockquote>
</blockquote>
<pre wrap="">>From KDE 3.2, Alt-Shift isn't working properly, not at-least for me.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I then moved to kwrite(1)
which works but I get the following
error constantly for every key stroke
ASSERT: "width" in katerenderer.cpp (675)
ASSERT: "width" in katerenderer.cpp (675)
ASSERT: "width" in katerenderer.cpp (675)
ASSERT: "width" in katerenderer.cpp (675)
ASSERT: "width" in katerenderer.cpp (675)
ASSERT: "width" in katerenderer.cpp (675)
I did manage to print using kwrite(1).
Any ideas on why I'm getting this assertion ?
Thanks guys....I've been waiting for this revelution (Farsi on
Linux) for years....
</pre>
</blockquote>
<pre wrap="">umm, it has been available now, for a couple of years, albeit with
its own problems.
</pre>
<blockquote type="cite">
<pre wrap="">PS: how do I write an HTML file, could I just use kwrite, provide
the HTML tags in English
and put my content by switching to Farsi and then end-tags in
English...
</pre>
</blockquote>
<pre wrap="">Yes, generally that's what you should do. Also in the <head> of your
html file, specify encoding as UTF-8, and also using whatever
editor, make sure that when you are saving your document, the
editor saves its contents using utf-8 encoding.
It is ofcourse easier said than done. In practice, mixing english
and farsi text will cause you so many peculiar and weird problems,
that you rarely get the formatting that you like. I have produced a
couple of persian html pages, and it takes me trice the amount of
time to produce a persian html page, relative to a comparable
english document.
</pre>
<blockquote type="cite">
<pre wrap="">Arash Zeini wrote:
</pre>
<blockquote type="cite">
<pre wrap="">We have been using (Farsi)KDE successfully to print documents in
Farsi as well as other languages on network printers using CUPS.
This is not a KDE related problem. It looks to me like the
GnomePrintCupsPlugin has a problem. Can you print your documents
using KDE applications like KEdit, KWrite, KOffice or applications
like OO.org?
Greetings,
Arash
In a message dated Thursday 16 September 2004 02:09, Medi
Montaseri
</pre>
</blockquote>
</blockquote>
<pre wrap="">wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">I am using gedit(1) and have a linux KDE and have couple of
network printers on my LAN.
I was wondering how to I print my document to these printers.
Currently when I print or do a
print preview from gedit, I see bunch of non-printables chars.
I do get the following messages from gedit(1)
(gedit:12099): GnomePrintCupsPlugin-WARNING **: iconv does not
support ppd character encoding: ISOLatin1, trying CSISOLatin1
Model not found, discarding config
Model not found, discarding config
Is there any HOW-TO for the printing part of Farsi KDE
environment. I have a feeling, some print spooler filter needs
to translate the content to Postscript or whatever
the printer understand.
Thanks
_______________________________________________
Kde-i18n-fa mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kde-i18n-fa@kde.org">Kde-i18n-fa@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/kde-i18n-fa">https://mail.kde.org/mailman/listinfo/kde-i18n-fa</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>