[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 98316] New: kpdf should use setText/startText instead of
From:       Gary Cramblitt <garycramblitt () comcast ! net>
Date:       2005-02-01 1:46:56
Message-ID: 20050201024653.98316.garycramblitt () comcast ! net
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=98316         
           Summary: kpdf should use setText/startText instead of sayMessage
                    to speak text
           Product: kpdf
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: tsdgeos terra es
        ReportedBy: garycramblitt comcast net


Version:            (using KDE Devel)
Installed from:    Compiled sources
OS:                Linux

Attached is a patch for kpdf/ui/pageview.cpp.  It changes from using sayMessage to \
using setText and startText.

Messages, and Warnings should only be used for short messages and will interrupt \
other speech in progress.   setText/startText should be used for longer texts that \
are not urgent.  In addition, by using sayMessage, the user loses the following \
capabilities:

1.  Cannot stop or pause the speech in KTTSMgr.
2.  Cannot advance/rewind by sentence in KTTSMgr.
3.  Cannot change the text job to use an alternate Talker (synth).
4.  Filters are not applied to messages and warnings, only to text jobs and \
KNotifies. 5.  Sentence Boundary Detection is not applied to messages or warnings, \
which means that the entire text must be synthesized before KTTSD will begin speaking \
it.  With text jobs, the text is broken up into sentences and each sentence is \
synthesized individually, resulting in faster time to begin  speaking.

I was thrilled to learn that this capability is now in kpdf.

Thank you!

BTW, not trying to spam you Enrico, but not sure I had your correct email address and \
time is short before freeze.


[prev in list] [next in list] [prev in thread] [next in thread]