Printing Unicode characters is not possible with KDE 2 apps. BibleTime 1.2
prints unicode very well.
Joachim
> Hi guys
>
> I am a user of Sword and Bibletime, I am using 1.1beta2. I love the
> software and everyone's commitment to the project it helps me no end in
> my ministry. I even compi
> Can someone confirm whether installing Bibletime 1.2 is possible without
> having to download the latest source from CVS?
Yes. You need Sword 1.5.3 and the bibletime-1.2 and bibletime-doc-1.2 files
and follow the usual install process. Current BibleTime cvs is unstable.
Martin
> I had earlie
Solution:
-upgrade to KDE3.
-install BibleTime 1.2
-configure ghostscript (KControl does this automatically for you).
You can then even print right-to-left.
Martin
> I am not able to print the IGNT module with both greek and english, for
> that matter I can't seem to print anything apart from
Hi guys
I am a user of Sword and Bibletime, I am using 1.1beta2. I love the software and everyone's commitment to the project it helps me no end in my ministry. I even compiled my own ESV module the other day. But.
I am not able to print the IGNT module with both greek and engli
> Martin, do you think we should integrate ICU directly into Sword? (And
> does anyone else have a serious objection to this?) It would mean
> signifigant growth in the size of the source tree. But this would be a
> good time to make the jump since we are about to do a CVS reorganization
> and
> -Original Message-
> Hello all,
>
> we were given an article on newsforge:
> http://newsvac.newsforge.com/newsvac/02/05/14/1913250.shtml?tid=11
>
> Please check it out and see if you can contribute to the discussion.
It is
> related to Unicode, Sword, BibleTime, KDE, QT and Pango alr
Yes, we have a cool Unicode implementation. May our Lord remember those
who contributed. May the glory go to our God.
As to the 2nd paragraph, I'd say yes, we do have Unicode search, yet I am
not sure what 'Unicode input' means. But I do know in Windows, Sword
search dialog doesn't display Unicod
